Open FunctionDJ opened 2 years ago
I have added a new environment variable called RESTART_CONTAINER
if you set this to no
it will do nothing when the "network is down".
Please update the container, set RESTART_CONTAINER
to no
and check if the container can access the internet.
You can do that by running the following commands from the console:
apt update && apt install -y curl dnsutils
curl ifconfig.io
> If this shows your vpn ip you are connected to your vpn provider
After that you can perhaps troubleshoot a bit why it can't connect to the internet.
Try running some of the following commands;
nslookup one.one.one.one
nslookup github.com
ping one.one.one.one
ping github.com
cat /etc/resolv.conf
> To check which DNS servers the Docker uses (should also show while running nslookup actually)
@DyonR curl ifconfig.io
gives me the correct VPN IP address. all of the other commands also work, i can reach cloudflare's DNS and github all fine. the resolv.conf looks like this:
# Some comment stuff
nameserver 192.168.0.1
search myrouter.name
nameserver 1.1.1.1
nameserver 1.0.0.1
does this info help? logs still say [ERROR] Network is possibly down
Have you been able to sort anything out with this? I get the similar [ERROR] Network is possibly down
. However, if I have RESTART_CONTAINER
on or off it still just stops and doesn't restart.
I currently have RESTART_CONTAINER
set to yes
, and the log shows that it tries to restart container, but it doesn't succeed as far as I can tell.
@pmd5700 I haven't been able to solve this issue yet
hello, I am using windscribe VPN. Windscribe-Wireguard didn't work for me for some reason, but Windscribe-OpenVPN is working fine.
This is happening multiple times per day now. Is there any way to force a container to restart automatically in the Synolgy Software?
@FunctionDJ i just had this issue but i ended up just restarting the docker service guessing / hoping it was a one time thing. ether way did you test the openvpn on another device to make sure it works?
@pmd5700 do you have the latest
image set? in order to stop the restarting looks to need that version.
@WhiteNight121 Yes, I have latest set. I thought it was getting better - didn't have an issue for a week or so. Now it's back to every day or 2.
@WhiteNight121 Yes, I have latest set. I thought it was getting better - didn't have an issue for a week or so. Now it's back to every day or 2.
Hmm I do see the VM go down and restart or I assume it does as if I have the tab open sometimes I got log back in again but it comes back up and goes back to doing it's thing. I will say I'm not on the latest, I'm also not using OpenVPN but I don't think that should matter
Hi, i'm running this container using portainer and tried to follow the README as closely as possible, but i'm getting a "Network is down" error, which exits the container and makes it 'boot-loop' because of the restart policy.
Here's an edited screenshot of my config in portainer:
I'm also running the container in privileged mode because i ran into this issue.
Finally, here's my edited log file that includes one full "run" of the container before it loops:
_qbittorrent-with-vpn_logs.txt
I'm very thankful for any help :pray: