The response is
Whoops! Cannot reach System Daemon.
The suggested solution is
sudo systemctl start nordvpnd
but it doesn’t change anything. Has anyone experienced the same problem?
Should be in Applications.
Move done.
BUT…
:~> /sbin/service --status-all
shows
nordvpnd.service loaded active running NordVPN Daemon
I’m not a NordVPN user, but just in case the following is helpful to you…
Thanks for the link. I tried all of the suggestions. Nothing changed. I have re-installed NordVPN at least twice and followed the web instructions that worked before. I chatted with a useless support person who gave me the same instructions to no avail. Then told me I could not get a refund for the three years I paid for. Support?
But here’s some not so bad news. Ubuntu connects. I truly hate Ubuntu, but it works. I’m afraid our favorite distro is at the bottom of the list for support as it’s not as universally popular.
Examine the journal logging…
sudo journalctl -fu nordvpnd.service
Try to start the connection, and observe/capture the output.
I note that NordVPN help pages include the following information…
https://support.nordvpn.com/Connectivity/Linux/1214725942/How-to-get-connection-logs-on-Linux.htm
Thanks, that was great advice.
Well that confirms what I suspected. That the site that adds the certificate is not working. Because when I originally installed it I got to a site that asked me to log in and it activated. But not the last few times. And this report confirms it. The daemon starts and stops repeatedly.
Apr 16 18:34:36 ion-a960d nordvpnd[3551]: 2022/04/16 18:34:36 error on making client request: Head "https://downloads.x9fnzrtl4x8pynsf.com/configs/dns/cybersec.json": dial tcp: i/o timeoutApr 16 18:34:36 ion-a960d nordvpnd[3551]: 2022/04/16 18:34:36 error on making client request: Head "https://downloads.mxo4bkqvdityebzvp.xyz/configs/dns/cybersec.json": dial tcp: i/o timeout
Apr 16 18:34:36 ion-a960d nordvpnd[3551]: 2022/04/16 18:34:36 error on making client request: Head "https://downloads.icpsuawn1zy5amys.com/configs/dns/cybersec.json": dial tcp: i/o timeout
Apr 16 18:34:36 ion-a960d nordvpnd[3551]: 2022/04/16 18:34:36 rotating: transport rotator: can't find gateway
Apr 16 18:34:36 ion-a960d systemd[1]: nordvpnd.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 18:34:36 ion-a960d systemd[1]: nordvpnd.service: Failed with result 'exit-code'.
Apr 16 18:34:41 ion-a960d systemd[1]: nordvpnd.service: Scheduled restart job, restart counter is at 10.
Apr 16 18:34:41 ion-a960d systemd[1]: Stopped NordVPN Daemon.
Apr 16 18:34:41 ion-a960d systemd[1]: Started NordVPN Daemon.
Apr 16 18:34:41 ion-a960d nordvpnd[3566]: 2022/04/16 18:34:41 [Info] Daemon has started
As for seeing the connection log. There isn’t one/
:~> sudo cat /var/log/nordvpn/daemon.log >> ~/Desktop/daemonlog.txt[sudo]
password for root:
cat: /var/log/nordvpn/daemon.log: No such file or directory
And “top” shows a nordvpn process starting and stopping repeatedly. So that solves the investigation. I just have to wait until someone fixes the i/o timeouts on the certificate sight.
It might be worth a shot to try connecting via NM (using OpenVPN protocol). Part of the process allows/requires you to select the server you want to connect to. (That might be a trial and error process.)
Can you access those URLs directly using browser or command line?
curl -I https://downloads.x9fnzrtl4x8pynsf.com/configs/dns/cybersec.json
Everything returned to normal this morning when I reverted to using wicked instead of network manager and changed my DNS servers. Perhaps the old DNS I was using was blocking my access. Or perhaps the certifying site was modified and the daemon ran normally. But I did learn something about checking logs. Thanks to all again.
Thanks for the update. (Not an openSUSE issue as such.)