-
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
Recent update broke everything, WEBUI not accessible #296
Comments
Don't think this explains the above problem but noticed this while turning DEBUG to true 2024-12-25 13:54:50 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) HERE ARE the entire logs in case this could help..
|
Hello, I experienced a similar issue where there was no network activity initially, and after restarting the container, I couldn’t access the WebUI. As a ProtonVPN user, I resolved this by downloading a new configuration file from ProtonVPN. After updating the config, everything started working smoothly again. I’m not entirely sure what caused the issue, but I wanted to share this fix in case it helps someone else identify the root cause. |
Hi there, thanks for the suggestion.. I tried but that wasn't the issue. I would have had an error message saying I'm missing the ovpn profile or something which I didn't get. Something changed in relation to PIA I'm guessing which is now breaking things. Not sure. The log files is not giving much information. But yeah, just to confirm downloading a new ovpn file didn't work. |
I did see this DECRECATED OPTION in the logs... Not sure if that would cause the issue or how to change that.
|
Also noticed this error coming up 024-12-26 15:08:27 ERROR: Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted (errno=1) I did try this in an attempt to fix this error but that didn't work
|
This is due to a change in runc, see here. |
Thanks for letting me know. I saw that for some people this worked but for me it doesn't do anything..
Are you aware of a solution? Anything you can do on your side? |
There are no solutions, needing to specify the tun device as part of the configuration is intended and runc was updated to reflect that. |
Of note, the change to runc to remove tun/tap from the default device rules has been reverted:- opencontainers/runc#4555 So things will be back to as they were once the revert has percolated through. |
Just to be clear.. Once the revert has gone through, adding the following
should get things working again? And I'm assuming we are talking of a revert of the runc and container changes? Sorry just making sure I understand right. I'm not sure I understand where those changes will take effect and in what version of what. |
No, once the runc revert has gone through you will NOT need to do that, as has been the case up until the recent runc change. |
Alright then it is sit and wait.. |
@binhex a new version of containerd was released, containerd.io/bookworm,now 1.7.25-1, with a new runc.. I'm not sure if this is supposed to address the vpn issue. I tried but nothing changed, the issue persists. |
Just ran into this issue, @tessierp can confirm updating containterd resolved the issue for me $ containerd --version
containerd containerd.io 1.7.25 bcc810d6b9066471b0b6fa75f557a15a1cbf31bb |
Recently updated this app and now I can't access the WEBUI. Any ideas? Here is my config :
The text was updated successfully, but these errors were encountered: