Connection Error with Daemon in NymVPN when Trying to Launch the Application

[Gelois0]

When attempting to run the NymVPN application using Flatpak (flatpak run net.nymtech.NymVPN), several warnings and errors occur related to the inability to connect to the daemon via IPC. The system shows multiple failed connection attempts, indicating a "transport error" and mentioning that the necessary file or directory for the connection cannot be found. This prevents the application from functioning correctly and blocks actions dependent on the connection with the daemon, such as retrieving VPN status, connections, or system messages.

Steps to Reproduce the Error:

1. Run the command flatpak run net.nymtech.NymVPN.
2. Observe that the application attempts to start but fails to connect to the daemon.
3. Check the error messages in the logs, where connection failures with the daemon are repeated.

Logs:

gelois@fedora:~$ flatpak run io.nymtech.NymVPN
error: app/io.nymtech.NymVPN/x86_64/master not installed
gelois@fedora:~$ flatpak run net.nymtech.NymVPN
2025-01-10T21:06:13.102285Z  INFO nym_vpn_app: app version: 1.1.0
2025-01-10T21:06:13.102384Z  INFO nym_vpn_app: Starting tauri app
2025-01-10T21:06:13.399965Z  INFO nym_vpn_app: app setup
2025-01-10T21:06:13.400018Z  INFO nym_vpn_app: Creating k/v embedded db
2025-01-10T21:06:13.400273Z  INFO new: nym_vpn_app::fs::path: app data dir: /home/gelois/.var/app/net.nymtech.NymVPN/data/nym-vpn-app
2025-01-10T21:06:13.400312Z  INFO new: nym_vpn_app::db: opening db at /home/gelois/.var/app/net.nymtech.NymVPN/data/nym-vpn-app/db
2025-01-10T21:06:13.446668Z  INFO new: nym_vpn_app::db: new db created at /home/gelois/.var/app/net.nymtech.NymVPN/data/nym-vpn-app/db
2025-01-10T21:06:13.634852Z  WARN set_max_size: nym_vpn_app::window: failed to get current monitor details
2025-01-10T21:06:13.635254Z  INFO nym_vpn_app::fs::path: app config dir: /home/gelois/.var/app/net.nymtech.NymVPN/config/nym-vpn-app
2025-01-10T21:06:13.646371Z  INFO new: nym_vpn_app::grpc::client: using grpc IPC transport: /run/nym-vpn.sock
2025-01-10T21:06:13.647327Z  WARN update_vpnd_info:vpnd_info:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:13.671544Z  INFO nym_vpn_app: starting vpnd health spy
2025-01-10T21:06:13.671776Z  INFO nym_vpn_app: starting vpn status spy
2025-01-10T21:06:13.671876Z  INFO nym_vpn_app: starting vpn connection updates spy
2025-01-10T21:06:13.671960Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:13.672233Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:13.672272Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error

(nym-vpn:2): Gtk-CRITICAL **: 16:06:13.828: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
2025-01-10T21:06:14.544723Z  INFO js: nym_vpn_app::commands::log: starting UI
2025-01-10T21:06:14.619647Z  WARN get_connection_state:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:14.619988Z  WARN daemon_status:check:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:14.620018Z  WARN daemon_status: nym_vpn_app::commands::daemon: failed to check daemon status: failed to connect to daemon using IPC transport

Caused by:
    0: transport error
    1: error trying to connect: No such file or directory (os error 2)
    2: No such file or directory (os error 2)
2025-01-10T21:06:14.621509Z  WARN is_account_stored:is_account_stored:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:14.621548Z ERROR is_account_stored: nym_vpn_app::commands::account: failed to check stored account: failed to connect to daemon using IPC transport
2025-01-10T21:06:14.624310Z  WARN account_links:account_links:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error locale="en"
2025-01-10T21:06:14.624343Z ERROR account_links: nym_vpn_app::commands::account: failed to get account link: failed to connect to daemon using IPC transport locale="en"
2025-01-10T21:06:14.624405Z  WARN system_messages:system_messages:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:14.624430Z  WARN system_messages: nym_vpn_app::commands::daemon: failed to get system messages: FailedToConnectIpc(transport error

Caused by:
    0: error trying to connect: No such file or directory (os error 2)
    1: No such file or directory (os error 2))
2025-01-10T21:06:14.629194Z  INFO js: nym_vpn_app::commands::log: show main window
2025-01-10T21:06:14.800052Z  WARN get_countries:countries:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error vpn_mode=TwoHop node_type=Some(Entry) gw_type=Wg
2025-01-10T21:06:14.800132Z  WARN get_countries:countries:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error vpn_mode=TwoHop node_type=Some(Exit) gw_type=Wg
2025-01-10T21:06:14.800169Z  WARN js: nym_vpn_app::commands::log: failed to query system messages: {"data":null,"key":"NotConnectedToDaemon","message":"not connected to the daemon"}
2025-01-10T21:06:14.820171Z  WARN js: nym_vpn_app::commands::log: command [get_connection_state] failed with error: {"data":null,"key":"NotConnectedToDaemon","message":"not connected to the daemon"}
2025-01-10T21:06:14.820350Z  INFO js: nym_vpn_app::commands::log: no entry country saved, using default {"name":"Switzerland","code":"CH"}
2025-01-10T21:06:14.820778Z  INFO js: nym_vpn_app::commands::log: no exit country saved, using default {"name":"Switzerland","code":"CH"}
2025-01-10T21:06:14.820864Z  WARN js: nym_vpn_app::commands::log: command [getStoredAccountRq] failed with error: {"data":null,"key":"NotConnectedToDaemon","message":"not connected to the daemon"}
2025-01-10T21:06:14.821218Z  WARN js: nym_vpn_app::commands::log: command [get_countries] failed with error: {"data":{"details":"failed to connect to daemon using IPC transport"},"key":"GetWgCountriesQuery","message":"failed to get countries for Wg"}
2025-01-10T21:06:14.821226Z  WARN js: nym_vpn_app::commands::log: command [get_countries] failed with error: {"data":{"details":"failed to connect to daemon using IPC transport"},"key":"GetWgCountriesQuery","message":"failed to get countries for Wg"}
2025-01-10T21:06:14.821291Z  WARN js: nym_vpn_app::commands::log: command [getAccountLinksRq] failed with error: {"data":null,"key":"NotConnectedToDaemon","message":"not connected to the daemon"}
2025-01-10T21:06:15.674207Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:15.674203Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:15.674258Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:17.675380Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:17.675435Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:17.675752Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:19.679170Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:19.679287Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:19.679303Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:21.680759Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:21.680787Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:21.681064Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:23.683271Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:23.683314Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:23.683448Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:25.684633Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:25.684684Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:25.684818Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:27.686461Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:27.686587Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:27.686893Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:29.687583Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:29.687729Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:29.688948Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:31.688702Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:31.688968Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:31.690276Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:33.691484Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:33.691484Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:33.691864Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:35.692936Z  WARN watch:health: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:35.693185Z  WARN refresh_vpn_status:vpn_status:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error
2025-01-10T21:06:35.693290Z  WARN watch_vpn_connection_updates:vpnd: nym_vpn_app::grpc::client: failed to connect to the daemon: transport error

[pronebird]

Hi,

Seems like the daemon is not running for some reason. Would be curious to see daemon logs. I don't remember the exact location for logs on Linux and we really need to document that. @octol can you please assist with extracting daemon logs on Linux?

[octol]

If you are on a Linux distribution supporting deb packages, like Ubuntu or PopOS, I would suggest using that as the primary way of installing, which should make sure the daemon is running

Which Linux distribution are you using?

[Gelois0]

I am using Fedora.