search

MarkusMcNugen / docker-qBittorrentvpn

Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN
https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/
GNU General Public License v3.0
166 stars 92 forks source link

Can not access the UI #163

Open dobage opened 8 months ago

dobage commented 8 months ago

System is Synology 1019+ running Container manager (The docker equivalent) . I am on the latest DSM version and latest Container Manager. Uploaded environment settings TCP is set to 32349 internal and 32349 on the docker. I have tied 8080 and 8080 just like the docs say and still can not get the UI up. I am on the local network. Everything looks right.

image markusmcnugen-qbittorrentvpn-1.csv

dobage commented 8 months ago

Set everything back to 8080 and the turned off VPN VPN_ENABLED=no and then I can reach the UI. Changed VPN_ENABLED=yes then I can not reach the UI on port 8080.

CrisDoesCG commented 6 months ago

Hi, I had the same issue. Putting VPN_ENABLED=true instead of "yes" solved it for me.

longieirl commented 6 months ago

Hi, I had the same issue. Putting VPN_ENABLED=true instead of "yes" solved it for me.

Strange as the log says the following;

torrent  | 2023-12-15 11:45:45.127684 [WARNIG] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
qbittorrent  | 2023-12-15 11:45:45.155079 [WARNIG] THE CONTAINER IS RUNNING WITH VPN DISABLED
qbittorrent  | 2023-12-15 11:45:45.178025 [WARNIG] PLEASE MAKE SURE VPN_ENABLED IS SET TO 'yes'
qbittorrent  | 2023-12-15 11:45:45.199289 [WARNIG] IF THIS IS INTENTIONAL, YOU CAN IGNORE THIS
qbittorrent  | 2023-12-15 11:45:45.219897 [WARNIG] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
D4rkAn6e1 commented 6 months ago

Hi,

Same issue on my side. Everything was working well and since 2 weeks I cannot access the UI anymore. Putting VPN_ENABLED=true is working but the docker is not running through the VPN, which is not my goal.

On my side, here are the logs when I let VPN_ENBALED=yes. And it goes on and on without stopping.

Capture d'écran 2023-12-23 190514

Did you find a solution @dobage ?

longieirl commented 5 months ago

I've a feeling this is not going to get resolved! Repo has been updated in years...

aeperea commented 3 months ago

I found a solution. Just ignore the variable entirely. If you look at start.sh, you'll see it default to yes. After doing this the UI shows up and when I track with https://ipleak.net/ I see the VPN ip being used.

AaronBenDaniel commented 2 months ago

I had this exact issue, where "VPN_ENABLED=yes" and I could not access the WebUI, but with "VPN_ENABLED=no" I could. @aeperea's solution (to just ignore the "VPN_ENABLED" environment variable) did not work for me. I then realized that "LAN_NETWORK" had been set incorrectly (it was "10.0.0.0/24" but it needed to be "192.168.4.0/24"). Fixing that solved the issue for me.