-
Notifications
You must be signed in to change notification settings - Fork 112
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
Unable to access WebUI #337
Comments
I had this issue recently too, and redeploying the container didn't immediately resolve the issue. After like 10 minutes the reverse proxy began working for be my DNS resolution fails. Editing I read your log and it claims it was able to resolve google.com at some point. |
From within the container I can access WAN hosts and resolve DNS
as well as hosts on my LAN (notably this only works if LAN_NETWORK is set to
and from within the container I can access Deluge on any interface except
But from outside the container, Deluge WebUI is not accessible. If I set iptables to allow all connections iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT then it lets me access WebUI from outside the container, so the issue is not with the Docker ports, it's definitely with the generated I tried feeding the |
I currently experiencing identical behavior right now on the qbittorrent container. did you ever resolve the issue? |
Has this been looked at? I've got identical behavior. i.e. Can't access the webui with VPN enabled, but can access without. |
check out binhex/arch-qbittorrentvpn#203 and binhex/arch-int-vpn#32. I've been working with binhex and we're now waiting on the fix. |
There are a 1001 reasons for this, its a bit like saying my car wont start, could be no fuel, could be no spark plugs, it could be no engine, etc, please do the following to give me a clue as to what is going on:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md if @lcdt22890158 is still watching this, your issue is incorrect lan_network, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md |
The container launches successfully, the logs indicate that it has connected to the VPN successfully and launched Deluge successfully. But I'm not able to access the Web UI, I just get "The connection has timed out".
I'm using TrueNAS with bhyve running a Ubuntu Server 21.10 VM with Docker Swarm. My docker-compose.yml file looks like this:
Log files:
supervisord.log
deluge-web.log
But when I access
http://192.168.10.240:8112
the connection times out.ProtonVPN doesn't currently support port forwarding on non-Windows platforms, so I've got STRICT_PORT_FORWARDING disabled. I also tried having
LAN_NETWORK
set to 192.168.10.0/24 with the same result. I tried configuring the Docker port as9094:8112
and accessinghttp://192.168.10.240:9094
as well, also no luck.I'm able to access other containers running on the same node (such as pyMedusa and Jackett) without any issues.
I'm not really sure what other steps I should take to troubleshoot the issue.
The text was updated successfully, but these errors were encountered: