thepawn713

Yep! It's been working fine for months and has just recently stopped.

Upgraded to 6.6.7 and now I'm getting a connection refused error... Tried reinstalling the container, a new appdata folder, bridge mode, eth0 instead of bond0, but nothing has worked... Any ideas? tower-diagnostics-20190228-0840.zip

Hello, I changed my home network from 192.168.1.1 to 10.0.0.0 subnet to fix a conflicting issue with OpenVPN from where I usually connect from (both client and network were 192.168.1.X so I couldn't connect to local devices). I also updated Unraid to 10.0.0.123 static IP, 10.0.0.1 default gateway. Router is 10.0.0.1 and 255.255.0.0. Once doing this, I could access the Unraid GUI through the VPN fine, but not individual docker container GUIs. Also, none of my containers will communicate with each other and I cannot get Sonnar to reconnect to NZBGet, Deluge, or Jackett. I've tried 10.0.0.123, localhost, Tower, 127.0.0.1, the actual container IPs to connect with..nothing works. I get a 404 connection timeout error. I was able to connect to the container GUIs through the VPN by deleting and recreating my docker bridge network, but this has not fixed the Sonarr issue. I'm really at a loss... if anyone has any suggestions that'd be amazing. Thanks!

That's a good idea! I'll have to see if I can get DD-WRT installed on my router to get it working, but I'll do that as well. Thanks!

So I'm out of town and last night I connected to my server through my OpenVPN docker to check on things. I started fooling around with another container and absentmindedly clicked 'shut down all containers'... which naturally shutdown OpenVPN along with everything else... My server is plugged into a Wemo outlet (and UPS) to let me force shutdown if absolutely necessary, but upon restarting my containers didn't come up back up as I hoped they would have (the auto-restart button is on). I did get an email notification saying it came back on, so it's definitely running though. Anyways, now I have to wait until someone gets home in a few days so I can teamviewer into her computer, turn my containers back on, etc... Tldr: Idiotically booted myself out of OpenVPN and the container didn't start on server restart. Is there anything I can add in place once I'm back up to ensure this doesn't happen again? I was thinking perhaps a user script set to run on startup to ensure OpenVPN always starts? But maybe there's a better way?