Due to a power outage my server did a hard reboot and now I have issues with my reverse proxy. It seems it cannot access any containers listening on the IP of the host. Host network access is enabled.

 

Any ideas? 192.168.100.200 is my Unraid IP

 

root@Tower:~# docker exec -it NginxProxyManager bash
bash-5.0# ping 192.168.100.200
PING 192.168.100.200 (192.168.100.200): 56 data bytes
^C
--- 192.168.100.200 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
bash-5.0# ping 192.168.100.220
PING 192.168.100.220 (192.168.100.220): 56 data bytes
64 bytes from 192.168.100.220: seq=0 ttl=128 time=0.412 ms
^C
--- 192.168.100.220 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.412/0.412/0.412 ms
bash-5.0#

 

 

Any the reverse-proxy container has this configured:

 

edit: for completeness the network settings:

Edited June 21, 20215 yr by mattie112

I just experienced this earlier today on 6.9.2; had to reboot and a previously working container with a fixed IP on br0 wasn’t loading via reverse proxy.

Disabling and re-enabling docker made the already enabled “host access to custom network” setting actually come into effect.

Been meaning to test more and look into existing bug reports.

Hope that helps.


Sent from my iPhone using Tapatalk

Yeah that seems to fix it! I've noticed some routes where added:

 

 

The 'shim-br0' ones didn't exist earlier

Follow, I too has this issue for a long time already. 

today unraid crashed again and also needed to stop and start docker separately before the containers were able to access each other again on the host. 

Same here, anybody solved this by now ?

Yup just had this happen again, any fixes yet?

Restart the server or restart the Array, both should fix the issue after a cold boot.

Had this issue again (Unraid 6.10.3), my system kinda "crashed"  (I think cache got filled 100% and docker did not like that). Rebooted -> had this issue, stopped docker & started it -> it works again.

 

So even in the latest release this is still present.

Do you use DHCP or a static IP assignment for your server, use static.

 

This is DHCP. I prefer to use that (with a reservation ofc). Just in case I need to change anything than I have no trouble accessing my server.

 

(and this would be a workaround and not a fix :p)

So:

 

This is still an issue for me. Had a very long uptime, recently restarted due to an upgrade -> no problem. Now I had a "crash" (again due to filling-up the cache dir). Could not recover, removed the docker image and had it recreate. Then re-added all my containers and behold the same problem again

 

It is exactly the same as in the first screenshot, however disabeling and then re-enableing docker does not fix the issue right now.

 

docker run
  -d
  --name='NginxProxyManager'
  --net='br0'
  --ip='192.168.100.201'
  --ip6='xx:xx:xx:xx::xx'
  --privileged=true
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="NginxProxyManager"
  -e 'TCP_PORT_8181'='8181'
  -e 'TCP_PORT_8080'='80'
  -e 'TCP_PORT_4443'='443'
  -e 'USER_ID'='99'
  -e 'GROUP_ID'='100'
  -e 'UMASK'='000'
  -e 'APP_NICENESS'=''
  -e 'DISABLE_IPV6'='0'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://192.168.100.201:8181'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/nginx-proxy-manager-icon.png'
  -v '/mnt/user/appdata/NginxProxyManager/matthijs-custom-ssl-ciphers.conf':'/etc/nginx/conf.d/include/ssl-ciphers.conf':'rw'
  -v '/mnt/user/appdata/NginxProxyManager':'/config':'rw' 'mattie112/docker-nginx-proxy-manager'

 

And then the reply is:

```

Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets
Error: failed to start containers: NginxProxyManager

```

 

I tried removing br0 and manually creating it:

 

`docker network create --driver=macvlan --subnet=192.168.100.0/24 --subnet=xx:xx:xx:xx::0/64 br0`

 

That allows me to start the container but no network traffic possible.

 

So yes: any help is appreciated again  I could also open a new topic but this is exactly the same problem so yeah.... (or at least to me it looks like the same problem)

 

edit:

Tried changing to eth0 as listed in changelog (https://docs.unraid.net/unraid-os/release-notes/6.12.4/) no luck!

Edited September 4, 20232 yr by mattie112

For me the easy "fix" after a power failure and the server is booted back up and running ... the container aren't able to communicate with each other.

 

Fix:

do a restart after the system is booted and docker is running and that seems to fix it ... Containers can now communicate with each other