-
Notifications
You must be signed in to change notification settings - Fork 43
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't connect on Raspberry Pi 4 with v3.17.3 #342
Comments
I googled the error:
fixed it. |
same issue, my dns resolver is dnscrypt-proxy and was working fine with it before this update |
Thank your for reporting the issue! We are investigating and we'll release a fix for systemd. |
Hello, here is the error that shows in journal. [Error] networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Could not activate remote peer: activation request failed: unknown unit.: exit status 1 It seems the update is now trying to use systemd-resolved, though I keep it disabled and "resolvectl" normally doesn't do anything on my system. If I allow resolved to set my dns, dig shows my own loopback address instead of a nordvpn assigned one |
Sorry for the late response. |
sorry im not having much luck building it with mage and docker. I was using the nordvpn-bin package on the arch aur. |
Seems fixed. |
I upgraded my raspberry pi to nordvpn v 3.17.3 and I can't connect anymore.
I logged out and logged back in but that doesn't help.
I don't have a gui on this machine.
I tried both wireguard and openvpn (I prefer wireguard :-)).
These are the only warnings or error from the log:
The text was updated successfully, but these errors were encountered: