This is more of a docker question than a selfhosted question, but i think that most of people here should be familiar with docker.
HA runs with network-mode : host (in order for autodiscovery to work) when my Nginx Proxy Manager is running on a bridge network (and in a different docker-compose.yml file), which makes them not see each other as far as I know. Could I maybe add an additional network to the HA like this:
networks:
default:
driver: host
nginxnetwork:
external: true
I don’t have it setup this way myself. I just have nginx point to http://1.2.3.4:8123 where 1.2.3.4 is the LAN IP of your docker host.
I know there are ways to connect containers with the backend docker network and I think that is what you are trying to do. I’ve seen examples for Caddy and Traefik doing it this way to make setup “easier”.
Ill jump in while you are waiting on answer from more experienced user. My HA runs on host network and most of other containers are on their default network including NPM. NPM can manage them all, but I think you have to enable access from additional reverse proxy address in HA config
I have this in my configuration.yaml
http: use_x_forwarded_for: true trusted_proxies: - 10.0.0.20010.0.0.200 should be your npm docker IP
I dont know how to use code block in jerboa lol.
I do have this setup, but i don’t think that npm can reach the HA, i have tried through direct IP and 127.0.0.1 and none of them seemed to work.
Pretty sure that if you’re using host networking you can’t add an additional bridge network. I use macvlan to provide host-like access to the network (the container gets it’s own ip on your actual network) and then use bridges to connect to my reverse proxy (and also the zwave controller)
