-
Notifications
You must be signed in to change notification settings - Fork 93
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
Can not access the UI #163
Comments
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. |
Hi, I had the same issue. Putting VPN_ENABLED=true instead of "yes" solved it for me. |
Strange as the log says the following;
|
Hi, Same issue on my side. Everything was working well and since 2 weeks I cannot access the UI anymore. On my side, here are the logs when I let VPN_ENBALED=yes. And it goes on and on without stopping. Did you find a solution @dobage ? |
I've a feeling this is not going to get resolved! Repo has been updated in years... |
I found a solution. Just ignore the variable entirely. If you look at start.sh, you'll see it default to yes. |
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. |
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.
markusmcnugen-qbittorrentvpn-1.csv
The text was updated successfully, but these errors were encountered: