-
Notifications
You must be signed in to change notification settings - Fork 19
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
Container doenst connect to my vpn since 2.7.0. #361
Comments
Nordvpn disabled basic authent with user/pass, you have to know use service credentials, it could be the cause of the issue |
Well i was updating those when i found the issue. Since they did notify me by email about that change. So im using the service credentials. They work till 2.7 after they dont |
Thank you @crryp and @yongbi85, I've just had this issue and solved it following your suggestion! I'll leave the procedure here for it might be useful for someone: Basically you now need to use a
|
I allready did this. Those work but not after container 2.6. I did update to the latest container version then followed your steps allready at that time. But it doesnt connect. I went back to version 2.6 and then it does connect with the service credentials. Im using the container on a synology nas with dsm 7. |
Same here. Using 2.6.0 with the new service credentials works, but not any version past that. |
@crryp and @rikonor you seem to be having a different experience from me then. I use Watchtower to keep my containers up-to-date, and so I'm using the latest available version from In my case it's the So I'd say your issue is a totally different thing. For reference, these are my specs:
|
Since version 2.7.0 the container doenst connect to my vpn anymore. Im using nordvpn.
The log file shows this error:
Version 2.6.0 does work fine.
The text was updated successfully, but these errors were encountered: