-
Notifications
You must be signed in to change notification settings - Fork 14
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
WebUI not connecting/possible circular crash #30
Comments
It seems like there is an issue with the container or the config. The restarts are probably caused because the container exists but is set to always (or unless-stopped) restart. |
Hahah wow I can't believe the restart policy didn't occur to me. Thanks for the patience lmfao So turned the restart policy to never, this is the entire console log. There is also a docker container log in a different area (this is all via portainer) but its gibberish in the same way that an image file would be if you opened it in notepad so I didn't think that was what you meant.
` |
So adding vpn_enabled yes to the env has stopped QBVPN from crashing, meaning I can modify settings and whatnot without a 10 second timer to worry about. But torrents added error and fail instantly. edit: vpn_enabled no doesn't prevent QBVPN from erroring out immediately so I don't think its a vpn config issue |
Your docker log is not complete but from what you posted it seems like the VPN goes down shortly after the container finishes startup as there is no tun0 in the interface list (ip a). Can you post the complete log and your portainer config? If the container behaves differently, it would also be helpful if you could post the logs with VPN_ENABLED set to yes or no and without VPN_ENABLED set. |
I think the log is only saving the most recent 100 lines as the console display in portainer is set to display the most recent 100 lines by default? this here is the config part of my ovpn file
QBVPN VPN enabled.txt |
Hi!
I'm getting that same circular crash issue that a few others have reported on here the last few years. Not going to lie there is a solid chance this is a configuration issue as I am fresh at this whole linux/debian thing. I haven't tested with a torrent yet but right now I can log into webUI just fine for about 10 seconds at a time. Container seems to crash within about 10 seconds of me logging in, and is fine with a reboot.
Any guidance would be appreciated.. small words please!
The text was updated successfully, but these errors were encountered: