docker-qbittorrentvpn
docker-qbittorrentvpn copied to clipboard
DyonR
"Network is down" on subsequent runs
Running macOS Big Sure (11.4) on mid 2015 Macbook Pro retina 15" Docker version 20.10.5, build 55c4c88
Using the example to run the container, first run works well. Connection is established and works all fine. In case of restart of the container or sometimes automatically because network is down, it constantly attempts but produces the error "Network is down, exiting this Docker" each time.
Not having restart unless-stopped will just result in it closing. Wonder how it works if I remove, create and run it but not when start the container which is already made and stopped.
I do not fully understand what you mean. You want to run a new container when the other one goes down?
Running it for the first time works well. But if I stop the container and start it again, it goes into a loop where it display the error message "Network is down" and keeps restarting.
To fix this, I have to remove the image and then re-run it from scratch and then the first works all good. If I stop it and start it again, it goes into this loop again.
@Anoopnk I would check your all your VPN settings. Usually you get that message if the container cannot contact the "HEALTH_CHECK_HOST" (if undefined it is one.one.one.one). Still very, very odd that you are able to fix it via a purge and redo. Maybe there is a setting file somewhere that is causing your client to get kicked off after the container is created? I thought I had the same issue except I couldn't fix it with a purge. Turns out I had to delete my client from my provider and regenerate a new config.
@deranjer Thanks. I attempted to try by allowing "HEALTH_CHECK_HOST" through while monitoring it's accessablity by a simulator, but unfortunately I cannot get the container to run anymore.
2021-06-26 13:06:06.623378 [INFO] Starting WireGuard... Warning: `/config/wireguard/wg0.conf' is world accessible
[#] ip link add wg0 type wireguard
Error: Unknown device type.
Unable to access interface: Protocol not supported [#] ip link delete dev wg0
Cannot find device "wg0"
Do you have an idea to fix this? It was running fine last time I ran.
Can confirm that this was my issue, the DNS service I use blocks a lot of other DNS' to prevent people circumventing the DNS restraints so it was blocking one.one.one.one, so I added my own health check host and this error disappeared.
