Open sokol-usa opened 1 month ago
hi, thanks for the feedback. Does it happen only on Arch Linux, for the other computers, or also other distros? And could you please check the system logs for the error that causes the failure?
I am having the same issue in Redhat on 8.10 if I upgrade nordvpn to 3.18.1 I can no longer connect. I had to revert my VM back to 3.17.2 in order to get nordvpn to work. I might build out a new vm and try it on a fresh install to see if it still fails.
There is a new release 3.18.2 available. Could you check if this fixes your issues?
3.18.2. Did not resolve my issues. I am still failing to connect to nordvpn. I am running without issues on 3.17.2.
Would it be possible to check in the system logs if there is an error reported by our app related to DNS configuration?
Search in logs after Failed to set DNS configuration
and if you find it pass the full error message.
Here are some of the journalctl errors that I am seeing when attempting to connect.
I also removed /var/lib/sss/db folder and restarted sssd since it mentioned there were issues with sssd when I did the dnf upgrade on NordVPN.
Jun 13 21:08:45 hostname nordvpnd[819]: 2024-06-14T01:08:45.126186Z ERROR libmoose::tracker::tracker: ContextNotFound Error while fetching shared context: ContextNotFound
Jun 13 21:08:46 hostname nordvpnd[819]: 2024/06/13 21:08:46 [Error] invoking dbus object method: Unit systemd-resolved.service not loaded.
Jun 13 21:08:46 hostname nordvpnd[819]: 2024/06/13 21:08:46 [Error] networker setting dns: setting dns with resolvconf: setting dns with resolvconf: Failed to set DNS configuration: Unit dbus-org.freedesktop.re
solve1.service not found.: exit status 1
Jun 13 21:08:46 hostname nordvpnd[819]: 2024/06/13 21:08:46 [Error] err1: autoconnect failure | err2:
Thanks for checking the logs. Yes, this is the issue that we are working on to fix for the next release. Until them please use an older version, 3.17.2.
Thank you. Please let me know if there is a new version to test. I have a separate vm for testing this out so I can confirm it works before putting it into my production.
This update on Arch Linux (Endevour OS) returns an error message of "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."
The temporary solution until reboot is systemctl restart systemd-resolved.service
This is not an isolated issue as it spans across multiple computers.