I couldn't figure out how to resolve the issue, so I changed programs, moved to binhex-delugevpn. I think figured out my issue NordVPN everything was working normally, but Transmission only had the tunnel and not an IP address, so when I tried to access it from web-browser the errors were from cached info from previous changes in settings. Per the Docker documentation I added an environmental-variable 'PORTS'='9091,54321' - this change allowed me to access the Transmission-webgui.Īnyone have ideas on how to resolve or further troubleshoot? The Webui is unable to reach Transmission backend (server not found). However, when I open my Transmission docker container (modified per spaceinvader video - 97%-certain it's correctly modified). If I open the console for the Nordvpn container, and type the CLI: 'curl ifconfig.io' the reported IP address is NOT my WAN IP, but appears to be a NORD server/node: 207.38.90.204. Firewall is up, everything has to go through the vpn Just edited the container, adding environment variable DEBUG=on no new information. Port 54321 (UDP|TCP) is whitelisted successfully. Port 9091 (UDP|TCP) is whitelisted successfully. Subnet 172.17.0.0/16 is whitelisted successfully. Enabling connection to secure interfaces T10:01:46-05:00] Firewall is up, everything has to go through the vpn If I leave the 'Location' variable empty (let the docker/app auto-detect the server) the log stops at 'Connecting.' Question of my own, what's the syntax format for the 'Location' variable? I tried to use: '' which resulted in, ' could not determine server tag' and ' picking servers: no servers found' in the log window. It appears that you aren't the only one: Was only ever able to get it working in openvpn mode, could never get nordlynx to work.

I had been using an install I setup using the bubuntux container for the past year.

Nord torrent