Nord vpn unable to connect, activated and immediately deactivated

English Applications
1

I have a ticket opened with Nord on this but thought I’d ask here as well. First I’ll start off by saying that my android and windows machine connect to nord just fine over my wifi (ISP) so I know it’s not my ISP or router. Also, on my Tumbleweed host I do not have firewalld running so there’s no active local firewall. TW is up to date with the following moderatly recent kernel.

Linux localhost.localdomain 6.7.6-1-default

I didn’t want to install nord without a package manager via their wget way so I used their snapcraft app in the snap store. I snap installed the app and added the group and user. I also ran the commands it said to post install.

Systemctl shows the snap.nordvpn service running. I’m able to login to nord and the tray icon with the snap app and cli show I’m logged in. So, the next thing is to connect with the tray icon or command line via… “nordvpn connect”.

The issue is it creates the “nordlynx” interface as can be seen while monitoring the ip stack then then it gets torn down. The kde network daemon says “nordlynx activated” and then followed with a “nordlynx deactivated” message. I don’t think this is related to the network daemon as I created a config file that told it to not manage the nordlynx interface. I don’t get the kde network messages anymore but you can still see the interface appear briefly on the ip stack only to get removed. The nordvpnd logs are not where the docs say they are so I’m just using the journalctl to try and figure this out. Is anybody else using nord and might know what’s going on?

nordvpn settings
Technology: NORDLYNX
Firewall: enabled
Firewall Mark: 0xe1f1
Routing: enabled
Analytics: enabled
Kill Switch: disabled
Threat Protection Lite: disabled
Notify: disabled
Tray: enabled
Auto-connect: disabled
IPv6: disabled
Meshnet: disabled
DNS: disabled
LAN Discovery: disabled
Virtual Location: enabled

Here’s me monitoring via nmcli:

  • I can also see this in “ip a” via the watch command.

Blockquote

nmcli monitor
NetworkManager is running
nordlynx: device created
nordlynx: unavailable
nordlynx: disconnected
nordlynx: connecting (prepare)
nordlynx: connecting (configuring)
nordlynx: connecting (getting IP configuration)
nordlynx: using connection ‘nordlynx’
nordlynx: connection profile created
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connected (externally)
nordlynx: device removed
nordlynx: connection profile changed
nordlynx: connection profile removed
nordlynx: device created
nordlynx: unavailable
nordlynx: disconnected
nordlynx: connecting (prepare)
nordlynx: connecting (configuring)
nordlynx: connecting (getting IP configuration)
nordlynx: using connection ‘nordlynx’
nordlynx: connection profile created
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connected (externally)
nordlynx: device removed
nordlynx: connection profile changed
nordlynx: connection profile removed
nordlynx: device created
nordlynx: unavailable
nordlynx: disconnected
nordlynx: connection profile created
nordlynx: using connection ‘nordlynx’
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connecting (externally)
nordlynx: connected (externally)
nordlynx: device removed
nordlynx: connection profile changed
nordlynx: connection profile removed
vnet0: connection profile changed

Blockquote

The interfaced shows up and then it’s gone.

Systemctl shows it’s running.

systemctl status snap.nordvpn.nordvpnd.service
● snap.nordvpn.nordvpnd.service - Service for snap application nordvpn.nordvpnd
Loaded: loaded (/etc/systemd/system/snap.nordvpn.nordvpnd.service; enabled; preset: disabled)
Active: active (running) since Sat 2024-08-31 21:42:59 CDT; 22h ago
Invocation: 7131b4676e364e7cb8072e2490dc1b05
Main PID: 1778 (nordvpnd)
Tasks: 38 (limit: 19052)
CPU: 5min 5.635s
CGroup: /system.slice/snap.nordvpn.nordvpnd.service
└─1778 /snap/nordvpn/9/bin/nordvpnd

Here’s the journalctl ouput.

Blockquote

sudo journalctl -fu snap.nordvpn.nordvpnd.service
[sudo] password for root:
Sep 01 21:12:12 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Wg
Sep 01 21:12:13 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse
Sep 01 21:12:13 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse Heartbeat Analytics
Sep 01 21:12:13 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse QoS Analytics
Sep 01 21:12:13 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:12:13 [Info] unset allow list
Sep 01 21:12:13 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:12:13 [Error] networker setting dns: dns not set, no dns setting method is available
Sep 01 21:13:02 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:13:02 [Info] HTTP CALL Duration: 199.707643ms

Sep 01 21:13:37 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:13:37 [Warning] TELIO(v4.3.3): “telio_utils::tokio”:86 All tokio threads are parked for 84.826926027s
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 PRE_CONNECT system info:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: App Version: 3.18.4
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: OS Info:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: NAME=“Ubuntu Core”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: VERSION=“22”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: ID=ubuntu-core
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: PRETTY_NAME=“Ubuntu Core 22”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: VERSION_ID=“22”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: HOME_URL=“https://snapcraft.io/”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: BUG_REPORT_URL=“Bugs : Snappy”
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: System Info:Linux localhost.localdomain 6.7.6-1-default #1 SMP PREEMPT_DYNAMIC Fri Feb 23 09:15:04 UTC 2024 (b9dc7c6) x86_64 x86_64 x86_64 GNU/Linux
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: Routes for ipv4:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: default via 192.168.1.1 dev wlp3s0 proto dhcp src 192.168.1.118 metric 600
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.118 metric 600
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 192.168.100.0/24 dev virbr0 proto kernel scope link src 192.168.100.1 linkdown
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local 192.168.1.118 dev wlp3s0 table local proto kernel scope host src 192.168.1.118
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: broadcast 192.168.1.255 dev wlp3s0 table local proto kernel scope link src 192.168.1.118
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local 192.168.100.1 dev virbr0 table local proto kernel scope host src 192.168.100.1
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: broadcast 192.168.100.255 dev virbr0 table local proto kernel scope link src 192.168.100.1 linkdown
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: IP rules for ipv4:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 0: from all lookup local
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 32766: from all lookup main
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 32767: from all lookup default
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: Routes for ipv6:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: fe80::/64 dev wlp3s0 proto kernel metric 1024 pref medium
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local ::1 dev lo table local proto kernel metric 0 pref medium
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: local fe80::6cd6:4a01:f3c1:b47e dev wlp3s0 table local proto kernel metric 0 pref medium
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: multicast ***/8 dev wlp3s0 table local proto kernel metric 256 pref medium
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: IP rules for ipv6:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 0: from all lookup local
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 32766: from all lookup main
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: IP tables for ipv4:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: filter:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: # Warning: iptables-legacy tables present, use iptables-legacy to see them
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: nat:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: # Warning: iptables-legacy tables present, use iptables-legacy to see them
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P POSTROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: mangle:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: # Warning: iptables-legacy tables present, use iptables-legacy to see them
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P POSTROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: raw:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: # Warning: iptables-legacy tables present, use iptables-legacy to see them
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: security:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: # Warning: iptables-legacy tables present, use iptables-legacy to see them
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: IP tables for ipv6:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: filter:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: nat:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P POSTROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: mangle:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P POSTROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: raw:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P PREROUTING ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: security:
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P INPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P FORWARD ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: -P OUTPUT ACCEPT
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Debug] picking servers for NORDLYNX technology input
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] HTTP CALL Duration: 174.749521ms
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: Request: HTTP/3 GET https://api.nordvpn.com/v1/servers/recommendations?limit=20&filters[servers.status]=online&filters[servers_technologies]=35&filters[servers_technologies][pivot][status]=online&fields[servers.id]&fields[servers.name]&fields[servers.hostname]&fields[servers.station]&fields[servers.status]&fields[servers.load]&fields[servers.created_at]&fields[servers.groups.id]&fields[servers.groups.title]&fields[servers.technologies.id]&fields[servers.technologies.metadata]&fields[servers.technologies.pivot.status]&fields[servers.specifications.identifier]&fields[servers.specifications.values.value]&fields[servers.locations.country.name]&fields[servers.locations.country.code]&fields[servers.locations.country.city.name]&fields[servers.locations.country.city.latitude]&fields[servers.locations.country.city.longitude]&coordinates[longitude]=-96.383200&coordinates[latitude]=34.002600&fields[servers.ips] map[Accept-Encoding:[gzip, deflate] Content-Length: Content-Type:[application/json] User-Agent:[NordApp Linux 3.18.4 Linux 6.7.6-1-default]]

Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] server us8134.nordvpn.com remote true
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] starting vpn
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] libtelio version: v4.3.3
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: task started - Wg
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024-09-02T02:19:47.512485Z ERROR libmoose::tracker::tracker: ContextNotFound Error while fetching shared context: ContextNotFound
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: task started - Nurse QoS Analytics
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: task started - Nurse Heartbeat Analytics
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: task started - Nurse
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: task started - Telio
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] TELIO(v4.3.3): “telio::ffi”:528 telio_set_fwmark entry with instance id: 2084850250635892696. fwmark: 57841
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] TELIO(v4.3.3): “telio::ffi”:570 telio_connect_to_exit_node entry with instance id :2084850250635892696. Public Key: Ok(“8pRF…dgI=”). Allowed IP: Ok(“0.0.0.0/0”). Endpoint: Ok(194.110.112.187:51820)
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info] TELIO(v4.3.3): “telio::device::wg_controller”:181 Inserting peer: Some(RequestedPeer { peer: Peer { public_key: “8pRF…dgI=”, endpoint: Some(194.110.112.187:51820), ip_addresses: [100.64.0.1, 10.5.0.1], persistent_keepalive_interval: Some(25), allowed_ips: [V
4(Ipv4Network { addr: 0.0.0.0, prefix: 0 })], rx_bytes: None, tx_bytes: None, time_since_last_handshake: None, preshared_key: None }, local_direct_endpoint: None })
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Info]{“type”:“node”,“body”:{“identifier”:“75e00f8f-84c3-4d42-a34d-d767c0781f70”,“public_key”:““,“nickname”:null,“state”:“connecting”,“link_state”:“down”,“is_exit”:true,“is_vpn”:true,“ip_addresses”:[“10.5.0.1”,“100.64.0.1”],“allowed_ips”:[“0.0.0.0/0”],“endpoint”:”
194.110.112.187:51820",“hostname”:null,“allow_incoming_connections”:false,“allow_peer_send_files”:false,“path”:“direct”}}
Sep 01 21:19:47 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:47 [Debug] notifying about connect event: {IsMeshnetPeer:false APIHostname: Auto:false ThreatProtectionLite:false Protocol:UNKNOWN_PROTOCOL ResponseServersCount:0 ResponseTime:0 DurationMs:0 ServerFromAPI:false Type:0 TargetServerSelection: Technology:UNKNOWN_TECHNOLOGY
TargetServerCity:Dallas TargetServerCountry:United States TargetServerDomain:us8134.nordvpn.com TargetServerGroup: TargetServerIP:194.110.112.187 TargetServerPick: TargetServerPickerResponse: TargetServerName:United States #8134}
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info]{“type”:“node”,“body”:{“identifier”:“75e00f8f-84c3-4d42-a34d-d767c0781f70”,“public_key”:"”,“nickname”:null,“state”:“connected”,“link_state”:“up”,“is_exit”:true,“is_vpn”:true,“ip_addresses”:[“10.5.0.1”,“100.64.0.1”],“allowed_ips”:[“0.0.0.0/0”],“endpoint”:“194
.110.112.187:51820”,“hostname”:null,“allow_incoming_connections”:false,“allow_peer_send_files”:false,“path”:“direct”}}
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Debug] notifying about connect event: {IsMeshnetPeer:false APIHostname: Auto:false ThreatProtectionLite:false Protocol:UNKNOWN_PROTOCOL ResponseServersCount:0 ResponseTime:0 DurationMs:0 ServerFromAPI:false Type:1 TargetServerSelection: Technology:UNKNOWN_TECHNOLOGY
TargetServerCity:Dallas TargetServerCountry:United States TargetServerDomain:us8134.nordvpn.com TargetServerGroup: TargetServerIP:194.110.112.187 TargetServerPick: TargetServerPickerResponse: TargetServerName:United States #8134}
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] Setting the routing rules up
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] starting network configuration
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] reset allow list
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] unset allow list
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] setting dns to 103.86.96.100 103.86.99.100
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] set dns for interface [nordlynx] using: resolved
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Error] setting dns with resolved: setting link dns for nordlynx via dbus: Call failed: The name is not activatable: exit status 1
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] set dns for interface [nordlynx] using: resolvectl
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Error] setting dns with resolvectl: setting dns with resolvectl: Failed to set DNS configuration: The name is not activatable: exit status 1
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] set dns for interface [nordlynx] using: resolvconf
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Error] setting dns with resolvconf: setting dns with resolvconf: : exec: “resolvconf”: executable file not found in $PATH
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] set dns for interface [nordlynx] using: resolv.conf, default
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Error] setting dns with resolv.conf, default: open /etc/resolv.conf: permission denied
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Warning] removing suppress prefix rule: no such file or directory
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Warning] removing fwmark rule: no such file or directory
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] TELIO(v4.3.3): “telio::ffi”:862 telio_disconnect_from_exit_nodes entry with instance id: 2084850250635892696.
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Debug] notifying about disconnect event
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] TELIO(v4.3.3): “telio::device::wg_controller”:176 Removing peer: Some(Peer { public_key: “8pRF…dgI=”, endpoint: Some(194.110.112.187:51820), ip_addresses: [100.64.0.1, 10.5.0.1], persistent_keepalive_interval: Some(25), allowed_ips: [V4(Ipv4Network { addr: 0
.0.0.0, prefix: 0 })], rx_bytes: Some(92), tx_bytes: Some(1684), time_since_last_handshake: Some(889.806267ms), preshared_key: None })
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info] TELIO(v4.3.3): “telio::ffi”:444 telio_stop entry with instance id: 2084850250635892696.
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Telio
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Wg
Sep 01 21:19:48 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:48 [Info]{“type”:“node”,“body”:{“identifier”:“75e00f8f-84c3-4d42-a34d-d767c0781f70”,“public_key”:“***”,“nickname”:null,“state”:“disconnected”,“link_state”:“down”,“is_exit”:true,“is_vpn”:true,“ip_addresses”:[“10.5.0.1”,“100.64.0.1”],“allowed_ips”:[“0.0.0.0/0”],“endpoint”
:“194.110.112.187:51820”,“hostname”:null,“allow_incoming_connections”:false,“allow_peer_send_files”:false,“path”:“direct”}}
Sep 01 21:19:49 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse
Sep 01 21:19:49 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse Heartbeat Analytics
Sep 01 21:19:49 localhost.localdomain nordvpn.nordvpnd[1778]: task stopped - Nurse QoS Analytics
Sep 01 21:19:50 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:50 [Info] unset allow list
Sep 01 21:19:50 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:50 [Error] networker setting dns: dns not set, no dns setting method is available
Sep 01 21:19:50 localhost.localdomain nordvpn.nordvpnd[1778]: 2024/09/01 21:19:50 [Info] HTTP CALL Duration: 120.099826ms

Blockquote

2

Is there a reason why you use such an old kernel? Which snapshot are you on?
It would make more sense to upgrade to the latest snapshot before starting troubleshooting.

3

Your post is near to unreadable. Always use preformatted text when posting computer output. But all these logs appear to be from the program nordvpn.nordvpnd. Which is not part of the openSUSE. Have you tried to ask on the support channels for this program? They likely have more expertise than these forums. We can guess that your program stops because it fails to adjust DNS configuration.

but it requires someone familiar with this program to suggest how to fix it.

4

I don’t consider that to be a old kernel, I mean it’s the 6.7 vs the 6.10. Why do you consider this to be “such a old kernel”?

5

I apologize about the readability. I tried to put the format in there and space it out. Do you just hit the </> at in the composer menu before or after you past something?

Anyways, yes I know it’s not suse I asked because I thought maybe somebody here was using nord. And, yes I did ask the vendor which is the very first sentence in my post.

That output was from the journal, maybe I should put that on pastbin next time and just link it.

I think the dns error stands out…I put that in the ticket to the vendor but it’s suppose to fall back I believe to my dhcp servers. We shall see.

Thanks for your feedback.

6

My man…this might not be considered an old kernel if you were on Ubuntu or Debian, but you are on a rolling release. Which means you either are holding back the kernel from upgrading for some specific reason, or you simply haven’t upgraded your system since you installed and thus are running a snapshot that is months old.

7

I personally pin my kernel due to nvidia drivers, got tired of running a dup just to find out the nvidia drivers didn’t work. Next laptop or whatever I get I’m going to try and get a amd or intel video chip. I think Intel video is a good option? I don’t want to ever have to go through this nvidia bs again. I don’t game but do stream a lot so I think a intel or amd should work fine…don’t both of these have good support in the kernel? About time for a new laptop anyways.

I unpin and upgrade the kernel from time to time but generally don’t fret over the latest kernel. My install is about six years old.

8

Which drivers are you using? The open source or the proprietary?

Tbh, I have the proprietary Nvidia drivers and have never had much of an issue at all, and when I do, they are usually transient and due to Mesa overlay or other related packages being out of sync and not due to the drivers themselves. So I’m not exactly sure what you have on your system that could be causing that frequent of problems.

As far as your original issue, are you sure that the Nord application is even compatible with Opensuse, or Linux for that matter? It’s generally more advisable to set up either Openvpn or Wireguard in most distros.

9

I’m using the proprietary Nvidia drivers (GFXG04) I believe. It’s a old laptop but it’s still a intel I7 and works fairly well but it’s about time to upgrade. The issue I normally have is I run a dup and reboot to a black screen because the new kernel doesn’t have a driver yet or the driver that’s compiled for it has issues. A simple rollback works but it’s a pain. I usually run a full dup with the kernel pinned and if everything is ok then I’ll take a snapshot and then unlock the kernel and run dup again …so if it’s broke it’s just a little rollback and not everything. Regarding the nordvpn. I’m using their snap app which should work on anything that can run the snap daemon such as basically any Linux. I’ve had great success with snap and flatpack. And, yes it’s compatible with Linux as it’s basically wireguard / openvpn. I’ve got a ticket open with them so maybe I can get somewhere.

01:00.0 VGA compatible controller: NVIDIA Corporation GF114M [GeForce GTX 670M] (rev a1)

But, I do think I’m leaning toward a Intel or Amd chipset next as hopefully it has better native support in the mainline kernel.

10

Not sure if I need to ask this in the network section or not. But the vendor got back to me and ask me to try and restart “systemd-resolved”. I don’t see that on my TW install, I assume the kde network manager handles setting the dns. Is this something that can be installed without causing conflicts or issues? I guess the vpn application is trying to use this to set to a dns on their side so dns traffic goes over the tunnel. A little research seems to suggest this was removed from suse a few years back. It appears to be in package “systemd-network”. Again, is this something that could be installed or would it conflict and cause issues with network manager when I’m not wanting to use the vpn?

Here’s their response.

Please try running the following command via the terminal:

sudo systemctl start systemd-resolved && sudo systemctl enable systemd-resolved

11

Yes.

NetworkManager supports systemd-resolved for DNS management. I am not sure whether it will use it automatically though. Reading man NetworkManager.conf - probably not, you will need to set main.dns to systemd-resoved.

As was mentioned already, you can simply configure connection to your VPN directly in NetworkManager and it is even documented on their site (of course as usual, only using one of many available NetworkManager GUIs). The only reason to use vendor application is more convenient VPN server selection. Whether you actually need it, you need to decide yourself.

12

The network manager style of connecting does not allow me to use the wireguard protocol, it appears that it’s only a valid way of connecting via openvpn. I want to use their wireguard protocol aka “nordlynx”. And, their client also picks the best server, auto reconnects etc.

If I have to I will use the NM method but I was wanting to use the wireguard protocol since it’s suppose to be less resource intensive, more reliable and reported a better streaming experience by a lot of users.

The other thing I’m looking at after this experience is getting a raspberry or cheap intel n100 box and turning it into a vpn gateway so I can just route traffic that I want to go out the vpn to it and not have to worry about a client on every device I wish to use the vpn. It might be a better solution since then I can just point phones and tvs etc to it as they default gw.

I greatly appreciate your time sir. Thanks to you and the others!

13

Networkmanger has built in Wiregaurd support since over 5 years. It can easily chosen when setting up a VPN connection.

14

Ok, I was not aware of this. I will try this method then, thank you so much.

It also looks like my TP-Link router running OpenWRT supports wireguard as well. I was thinking of digging it out, updating it and seeing if it will work. It’s a old AC1750 so who knows what kind of speed I can get.

15

Of course it does. You tagged your post with “tumbleweed” and you mentioned KDE, so

image

Is it compatible with “normal” WireGuard?

16

Thanks, I see that now. The last time I looked at NM VPN support it didn’t have all this. I had to use a Cisco client, they really have added a lot.

But, I’ve looked into this more and it seems like setting up a manual “WireGuard” tunnel with Nord is maybe impossible without already having a working NordVpn client on linux working…which was my original issue.

The issue is you seem to need to have a established session with them then use some tools from github to pull the priv/pub keys. Also, getting the WG endpoints info is cumbersome. Their competitor surfshark seems to have all this in their portal with instructions on how to setup manual tunnels on linux or openwrt etc. I might just try surfshark out since they seem to officially support this.

I greatly appreciate the input here guys.

17

Well, then enable systemd-resolved if that is what their tools need.

18

I set them (dns servers) manually like support instructed me to and it didn’t fix anything. Besides, support keeps asking me to run journalctl commands that produce nothing. I keep telling them it’s not finding any logs for their nord daemon but each email another tech ask me to do the same thing.

The last tech at least said that suse wasn’t supported even though a snap app should work just fine on suse. It’s the only snap app I have a issue with so far.

It’s been a good experience because I figure I’d just like to get a gateway and configure that so all my devices can use it without much fuss. OpenWRT seems to support what I’m after so I’ll probably just go that route.

Thanks!

19

the logs goes to desktop and access them via dolphin hoe desktop.

how did you run the installer? script or downloading RPM file and then install

20

i just installed nordVPN using there rpm package that installs repo and gpg key. It creates yum.repos.d folder where you need to copy nordvpn.repo to zypp/repos.d folder to enable repo
sudo cp /etc/yum.repos.d/nordvpn.repo /etc/zypp/repos.d/

then just run install process as normal typing sudo zypp in nordvpn

i use aeon so it is similar only using transactional-update method

also as you using snap it cant get access to needed system files and have so any issues so i recommend using the method i use