Nestoraj

Hi everybody! I'm having some troubles using this container and I wonder if you could help me. Using the docker container in bridge mode seems to work just fine and I'm even able to use it to add vpn to other containers adding their ports in the config, and I'm able to access the webui using the host IP with the 8112 port. My problem is that I would like to change it to a new network (br0) because I have my pihole and nginx proxy manager there. The thing is that when I change the deluge container to the new network, nothing fails and I can curl the webpage from the docker container itself, but I can't access it from my computer. This is the run command that it prompts the docker webpage in my nas: docker run -d --name='binhex-delugevpn' --net='br0' --ip='10.168.2.135' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="NAS" -e HOST_CONTAINERNAME="binhex-delugevpn" -e 'TCP_PORT_8112'='8112' -e 'TCP_PORT_58846'='58846' -e 'TCP_PORT_58946'='58946' -e 'UDP_PORT_58946'='58946' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'=<myvpnusername> -e 'VPN_PASS'=<myvpnpassword> -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='10.168.2.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DELUGE_ENABLE_WEBUI_PASSWORD'='yes' -e 'VPN_INPUT_PORTS'='8080,8090,7878,8989,9897,5055,6789,5454' -e 'VPN_OUTPUT_PORTS'='8080,8090,7878,8989,9897,5055,6789,5454' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'UDP_PORT_9696'='9696' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8090'='8090' -e 'TCP_PORT_7878'='7878' -e 'TCP_PORT_8989'='8989' -e 'TCP_PORT_9897'='9897' -e 'TCP_PORT_5055'='5055' -e 'TCP_PORT_6789'='6789' -e 'TCP_PORT_5454'='5454' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8112]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/deluge-icon.png' -v '/mnt/user/Downloads/Torrents/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-delugevpn' I have noticed that using `docker inspect binhex-delugevpn` the PortBindings section is empty when I use the br0 network, but filled up with all the ports when it's in bridge. Thanks for any help in advance! Cheers, Nestor

Hi! I has worked!, I tried removing all the unused custom networks and it was still failing, but once I removed the one in use (in my case proxynet) it has started working again. It's a bit weird since I have not touch this custom network in a while. I'll try to reconfigure it again and if it fails at least I know where to look at. I've also set the ipvlan, I've seen that it's the default since 6.11.5 Thanks a lot!

Yes I have several custom networks Should I remove all of them and reset them?

Hi Thanks for your reply, I tried disabling the bridge and renaming the network.cfg file and it keeps failing. I had to reconfigure my eth0 using the instructions here for setting an static IP: https://wiki.unraid.net/Configuration_Tutorial After that I was able to connect using the UI from my main PC but once the docker service starts it stops responding, even if there is no container running. If I stop the docker service once it hangs, I'm not able to reconnect either, the only solution is to reboot, or change the static IP of my eth0 to something else (I was able to do this using the IP from my other NIC)

Hi everyone, I'm having some troubles to use the webUI whenever I enable Docker. I have two NICs, one ethernet with an static IP set to 10.168.2.100 and the other one is a Mellanox 10G with an static IP set to 192.168.2.100. I have used both cards without any problem for a few months and the webUI was loading on the first one, so if tried to access using 10.168.2.100, everything worked. But I don't know what I've done that the 10.168.2.100 does not work anymore once I start the docker service. I can still get access to the webUI using the 192.168.2.100 ip but I can not get access to any docker container because all of them use the 10.168.2.100 ip. The only thing that I changed was the naming of the interfaces on settings (I've already set them to empty again and it keeps failing). This is how I have configured my network: And this is the docker settings: I've updated to the lastest version (6.11.5) and everything keeps failing, I don't know where else to look at. I hope someone can figure out what's going on, Thanks! Nestor nas-diagnostics-20221202-2200.zip

+1 for not been able to access it. I'm able to access the webui using the ip of my 10GbE NIC, but the default one isn't working. This only happens to me once I start the docker service (even if all my containers are off), and if I try to run any container, I'm not able to access any of them either since they are using the default IP.

Hi everyone, I'm having some troubles to use the webUI whenever I enable Docker. I have two NICs, one ethernet with an static IP set to 10.168.2.100 and the other one is a Mellanox 10G with an static IP set to 192.168.2.100. I have used both cards without any problem for a few months and the webUI was loading on the first one, so if tried to access using 10.168.2.100, everything worked. But I don't know what I've done that the 10.168.2.100 does not work anymore once I start the docker service. I can still get access to the webUI using the 192.168.2.100 ip but I can not get access to any docker container because all of them use the 10.168.2.100 ip. The only thing that I changed was the naming of the interfaces on settings (I've already set them to empty again and it keeps failing). This is how I have configured my network: And this is the docker settings: I've updated to the lastest version (6.11.5) and everything keeps failing, I don't know where else to look at. I hope someone can figure out what's going on, Thanks! Nestor