Same Nym account, same machine, same cable to the same router, Windows 10 has no issue at all; connects and works perfectly; same account works in Android too.
But in Ubuntu 22, despite of NymVPN app seems connected there won’t be response from WAN, requests stays in lookup state.
I guess it must be about the DNS settings.
I removed all network profiles and created new, fully DHCP; Ipv4 and Ipv6 activated to be automatically configured by VPN app if it requires. I removed Proton but kept PIA and disconnected it with settings as no killswitch or anything at all.
Found out some issues get escalated because of the TZ settings of Ubuntu distros, I have set Location Settings allowed as default and Timezone is set to Auto. Eleminated that option as well.
Here are some output for a start
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
ID=ubuntu
ID_LIKE=debian
...
❯ sudo nym-vpnd --version
nym-vpnd
Binary Name: nym-vpnd
Build Timestamp: 2026-10-21T21:29:02.801774178Z
Build Version: 2026.14.0
Commit SHA: b537d58cdfbb898b4449e73fdeed3a1e940a8285
Commit Date: 2026-10-21T22:05:49.000000000+02:00
Commit Branch: release/2026.14-xaubub
rustc Version: 1.99.1
rustc Channel: stable
cargo Profile: release
2026-10-23T13:31:44.638249Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638280Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638311Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638343Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638375Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638406Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638438Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.638471Z DEBUG mnl::callback: Processing 36 byte netlink message without a callback
2026-10-23T13:31:44.647425Z DEBUG mnl::socket: Sending 69631 byte netlink message
2026-10-23T13:31:44.647710Z DEBUG mnl::callback: Processing 60 byte netlink message with callback
2026-10-23T13:31:44.647765Z DEBUG mnl::callback: Processing 60 byte netlink message with callback
2026-10-23T13:31:44.647799Z DEBUG mnl::callback: Processing 56 byte netlink message with callback
2026-10-23T13:31:44.647833Z DEBUG mnl::callback: Processing 56 byte netlink message with callback
2026-10-23T13:31:44.647877Z DEBUG mnl::callback: Processing 60 byte netlink message with callback
2026-10-23T13:31:44.647907Z DEBUG mnl::callback: Processing 60 byte netlink message with callback
2026-10-23T13:31:44.647936Z DEBUG mnl::callback: Processing 56 byte netlink message with callback
2026-10-23T13:31:44.647965Z DEBUG mnl::callback: Processing 56 byte netlink message with callback
2026-10-23T13:31:44.647996Z DEBUG mnl::callback: Processing 56 byte netlink message with callback
2026-10-23T13:31:44.648070Z DEBUG nym_vpn_lib::tunnel_state_machine::states::connected_state: Enabling local DNS forwarder to: 9.9.9.9 (853/tls), 149.112.112.112 (853/tls), 9.9.9.9 (443/https), 149.112.112.112 (443/https), 1.1.1.1 (853/tls), 1.0.0.1 (853/tls), 1.1.1.1 (443/https), 1.0.0.1 (443/https)
2026-10-23T13:31:44.648170Z INFO nym_vpn_lib::resolver: Updating config: Forwarding { dns_servers: [NameServerConfig { ip: 9.9.9.9, trust_negative_responses: true, connections: [ConnectionConfig { port: 853, protocol: Tls { server_name: "dns.quad9.net" }, bind_addr: None }] }, NameServerConfig { ip: 149.112.
112.112, trust_negative_responses: true, connections: [ConnectionConfig { port: 853, protocol: Tls { server_name: "dns.quad9.net" }, bind_addr: None }] }, NameServerConfig { ip: 9.9.9.9, trust_negative_responses: true, connections: [ConnectionConfig { port: 443, protocol: Https { server_name: "dns.quad9.net",
path: "/dns-query" }, bind_addr: None }] }, NameServerConfig { ip: 149.112.112.112, trust_negative_responses: true, connections: [ConnectionConfig { port: 443, protocol: Https { server_name: "dns.quad9.net", path: "/dns-query" }, bind_addr: None }] }, NameServerConfig { ip: 1.1.1.1, trust_negative_responses:
true, connections: [ConnectionConfig { port: 853, protocol: Tls { server_name: "cloudflare-dns.com" }, bind_addr: None }] }, NameServerConfig { ip: 1.0.0.1, trust_negative_responses: true, connections: [ConnectionConfig { port: 853, protocol: Tls { server_name: "cloudflare-dns.com" }, bind_addr: None }] }, N
ameServerConfig { ip: 1.1.1.1, trust_negative_responses: true, connections: [ConnectionConfig { port: 443, protocol: Https { server_name: "cloudflare-dns.com", path: "/dns-query" }, bind_addr: None }] }, NameServerConfig { ip: 1.0.0.1, trust_negative_responses: true, connections: [ConnectionConfig { port: 443
, protocol: Https { server_name: "cloudflare-dns.com", path: "/dns-query" }, bind_addr: None }] }] }
2026-10-23T13:31:44.657950Z INFO nym_dns: Setting DNS servers on interface 'tun1': DnsConfig { addresses: [127.27.74.41], port: 53 }
2026-10-23T13:31:44.658510Z DEBUG nym_dns::imp: Managing DNS via systemd-resolved
2026-10-23T13:31:44.661363Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}:parse_response: nym_http_api_client: attempting to parse response as application/json
2026-10-23T13:31:44.661415Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}:parse_response: nym_http_api_client: close time.busy=154µs time.idle=57.1µs
2026-10-23T13:31:44.661445Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}: nym_wireguard_private_metadata_client: close time.busy=663µs time.idle=37.5ms
2026-10-23T13:31:44.661464Z DEBUG nym_wg_metadata_client: Remaining wireguard bandwidth with gateway CigQNee3iCs3zoXjf5c9WbEScaEwWGwoNPt2rdnKvZmP for today: 1427.56 MB
2026-10-23T13:31:44.661493Z DEBUG nym_vpn_lib::bandwidth_monitor: current depletion rate of 0 bytes per current check period of 5 seconds
2026-10-23T13:31:44.661520Z DEBUG nym_vpn_lib::bandwidth_monitor: Adjusting check interval to 5 seconds
2026-10-23T13:31:44.661540Z DEBUG nym_vpn_lib::bandwidth_monitor: Attempt #1 to query bandwidth of gateway EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw...
2026-10-23T13:31:44.661599Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}:create_request{path=["v1", "bandwidth", "available"]}: nym_http_api_client: close time.busy=28.0µs time.idle=2.58µs
2026-10-23T13:31:44.665917Z DEBUG nym_favorites::io: Data written to "/var/lib/nym-vpnd/mainnet/recents.json"
2026-10-23T13:31:44.666025Z INFO nym_vpn_lib::tunnel_state_machine: New tunnel state: Connected wg to 77.111.101.179:51822 [CigQNee3iCs3zoXjf5c9WbEScaEwWGwoNPt2rdnKvZmP] → 157.254.54.45:51822 [EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw]
2026-10-23T13:31:44.666130Z DEBUG nym_statistics::handler::report_sending: Stats report conditions are met, trying to send in 3 secs
2026-10-23T13:31:44.703019Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}:parse_response: nym_http_api_client: attempting to parse response as application/json
2026-10-23T13:31:44.703170Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}:parse_response: nym_http_api_client: close time.busy=237µs time.idle=58.5µs
2026-10-23T13:31:44.703251Z DEBUG available_bandwidth{request_body=Request { version: V2, inner: [0, 0] }}: nym_wireguard_private_metadata_client: close time.busy=636µs time.idle=41.1ms
2026-10-23T13:31:44.703309Z DEBUG nym_wg_metadata_client: Remaining wireguard bandwidth with gateway EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw for today: 1401.65 MB
2026-10-23T13:31:44.703393Z DEBUG nym_vpn_lib::bandwidth_monitor: current depletion rate of 0 bytes per current check period of 5 seconds
2026-10-23T13:31:44.703436Z DEBUG nym_vpn_lib::bandwidth_monitor: Adjusting check interval to 5 seconds
2026-10-23T13:31:47.670082Z DEBUG nym_statistics::handler::report_sending: ReportHandler: Trying to send 1 reports
❯ sudo nym-vpnc connect && sudo nym-vpnc status -l
State: Connecting wg, resolving api addresses, fallback entry: false, fallback exit: false, try #0
State: Connecting wg, awaiting account readiness, fallback entry: false, fallback exit: false, try #0
State: Connecting wg, awaiting credentials availability, fallback entry: false, fallback exit: false, try #0
State: Connecting wg, refreshing gateways, fallback entry: false, fallback exit: false, try #0
State: Connecting wg, selecting gateways, fallback entry: false, fallback exit: false, try #0
State: Connecting wg, registering with gateways, fallback entry: false, fallback exit: false, try #0
State: Connecting wg to 77.111.101.179:51822 [CigQNee3iCs3zoXjf5c9WbEScaEwWGwoNPt2rdnKvZmP] → 157.254.54.45:51822 [EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw], connecting tunnel, try #0
State: Connecting wg to 77.111.101.179:51822 [CigQNee3iCs3zoXjf5c9WbEScaEwWGwoNPt2rdnKvZmP] → 157.254.54.45:51822 [EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw], connecting tunnel, try #0
State: Connected wg to 77.111.101.179:51822 [CigQNee3iCs3zoXjf5c9WbEScaEwWGwoNPt2rdnKvZmP] → 157.254.54.45:51822 [EGjiDxYgnApuMSi8eHi5qHCm2RWGb3Xub7yPo2QqPYgw]
❯ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether e8:***:79 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether b8:***:e3 brd ff:ff:ff:ff:ff:ff
4: br-171ae0f7b5de: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:***:d0 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether fe:***:28 brd ff:ff:ff:ff:ff:ff
9: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1420 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
10: tun1: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1340 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
❯ resolvectl status
Global
Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Fallback DNS Servers: 1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4
Link 2 (enp3s0)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 10.0.1.1
DNS Servers: 10.0.1.1
DNS Domain: local
Link 3 (wlp2s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 4 (br-171ae0f7b5de)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 5 (docker0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 9 (tun0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Link 10 (tun1)
Current Scopes: DNS
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 127.27.74.41
DNS Servers: 127.27.74.41
DNS Domain: ~.
Edit: fixed the nym-vpnd version.