Skip to content
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

Closed
bjlockie opened this issue Mar 29, 2024 · 7 comments
Closed

can't connect on Raspberry Pi 4 with v3.17.3 #342

bjlockie opened this issue Mar 29, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@bjlockie
Copy link

bjlockie commented Mar 29, 2024

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 :-)).


$ sudo nordvpn c US
Connecting to United States #6270 (us6270.nordvpn.com)
The VPN connection has failed. Please check your internet connection and try connecting to the VPN again. If the issue persists, contact our customer support.

These are the only warnings or error from the log:


$ sudo journalctl -u nordvpnd

[Warning] executing 'ip -6 rule del from all lookup main suppress_prefixlength 0' command: exit status 2: RTNETLINK answers: No such file or directory

[Warning] executing 'ip -6 rule del not from all fwmark 57841' command: exit status 2: RTNETLINK answers: No such file or directory

[Error] networker setting dns: setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: Unit dbus-org.freedesktop.resolve1.service not found.: exit status 1

@bjlockie
Copy link
Author

I googled the error:

$ sudo systemctl start systemd-resolved.service
$ sudo systemctl enable systemd-resolved.service

fixed it.

@saus23
Copy link

saus23 commented Mar 30, 2024

same issue, my dns resolver is dnscrypt-proxy and was working fine with it before this update

@mariusSincovici mariusSincovici added the bug Something isn't working label Apr 3, 2024
@mariusSincovici
Copy link
Contributor

Thank your for reporting the issue! We are investigating and we'll release a fix for systemd.
@saus23 could you please let us know what error message are you receiving?

@saus23
Copy link

saus23 commented Apr 4, 2024

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

@mariusSincovici
Copy link
Contributor

Sorry for the late response.
Version 3.17.4 is available, could you please try to update and see if it fixes your issues?

@saus23
Copy link

saus23 commented Apr 5, 2024

sorry im not having much luck building it with mage and docker. I was using the nordvpn-bin package on the arch aur.

@bjlockie
Copy link
Author

bjlockie commented Apr 5, 2024

Seems fixed.

@bjlockie bjlockie closed this as completed Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants