Licence validation step fails after reboot

[bazzybtec]

Describe the bug
Upon reboot of the workstation the Licence that i have purchased shows as not valid in the connection GUI however in settings it shows as active and valid. connection fails due to licence issue so I have to deactivate and reactivate the licence for it to work

Expected behavior
A paid licence should not interrupt the running of the product

Logs

[2024-05-06T21:37:04Z INFO gpservice::cli] gpservice started: 2.2.0 (2024-04-30)
[2024-05-06T21:37:04Z INFO gpservice::ws_server] WS server listening on port: 34921
[2024-05-06T21:37:05Z INFO gpapi::process::gui_launcher] Version check passed: 2.2.0
[2024-05-06T21:37:05Z INFO gpapi::process::gui_launcher] Launching gpgui
[2024-05-06T21:37:05Z INFO gpgui::cli] gpgui started: 2.2.0 (2024-04-30)
[2024-05-06T21:37:05Z INFO gpgui::app] Setting the custom openssl conf path
[2024-05-06T21:37:05Z INFO gpgui::config::private_data] Loaded config key from keyring
[2024-05-06T21:37:05Z INFO gpgui::app::app_initializer] App initialized
[2024-05-06T21:37:05Z INFO gpgui::ws_connector] Connecting to WS server
[2024-05-06T21:37:05Z INFO gpgui::ws_connector] Received ping
[2024-05-06T21:37:05Z INFO gpgui::ws_connector] Connected to WS server
[2024-05-06T21:37:05Z INFO gpservice::handlers] New client connected
[2024-05-06T21:37:05Z INFO gpservice::ws_server] Sending current VPN state to new client
[2024-05-06T21:37:05Z WARN gpgui::license::api] Failed to call API: error sending request for url (https://api.lemonsqueezy.com/v1/licenses/validate): error trying to connect: dns error: failed to lookup address information: Name or service not known
[2024-05-06T21:37:07Z WARN gpapi::utils::window] Failed to raise window: Failed to raise window: GlobalProtect
[2024-05-06T21:37:08Z INFO gpgui::handlers::subscription] Sending the init event to client: main
[2024-05-06T21:37:08Z INFO gpgui::handlers::subscription] Sent the init event to client: main

attempting to ping that domain resolves in console

OS: [e.g. Ubuntu 22.04]
Desktop KDE

[yuezk]

Hi @bazzybtec,

Sorry for the inconvenience.

This could be a temporary network issue. Could you please try to restart the client or restart the OS and try again?

Thanks.

[bazzybtec]

this is an ongoing issue that happens every system restart. I suspect this is caused by the client performing this check too soon in the startup process and not reattempting upon failure.

[yuezk]

It will check it when the client is started. BTW, will the client start automatically after the system startup? And if restarting the client works for you?