-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to bind VPN config + Unable to access WEB UI #280
Comments
I’m no expert, so I could be wrong on anything. But it looks like you have strict port forwarding enabled but are using a Proton VPN server that doesn’t support port forwarding. It also looks like there’s a problem with iptables. You may want to try enable the legacy option for that. |
Yep, you are right on. The scrip won't start the qbittorrent script if there is no port forwarding when STRICT_PORT_FORWARD=yes I have been banging my head at this problem for so long and I finally figured it out recently. |
Any solution to this? I'm having the exact same problem since the update... And weird, I can't even rollback to an earlier version, the images have been deleted.... Using PIA as my VPN Provider. Strict Port Forwarding enabled.. If the VPN is enabled, no WEB UI available. |
Hello,
I'm experiencing issues with my qBittorrent container setup. Seem to fails to start properly due to issues binding the VPN configuration file. I also can't access WEB UI (also, it seem that deployment freezed for a while after WEBUI_PORT defined 8100...)
(first time using docker ask me if you need more details)
logs :
YAML :
Environnement :
UPDATE: Setting VPN_ENABLED to "no" allows me to access the UI. Do you have any idea why I encounter issues when the VPN is enabled? The container still freezes after defining WEBUI_PORT to 8100... but I see that there is already an issue opened about it on TrueNAS Scale.
The text was updated successfully, but these errors were encountered: