Unable to connect using Pritunl Client Electron

Pritunl Pritunl VPN
1

System information:

  • OS: Arch Linux (fully updated at 2026-02-20)
  • Laptop: Honor Magicbook X16 Pro (Ryzen 7 7840HS, 16GB RAM)
  • Pritunl Client version: 1.3.4466.51-1 (pritunl/pritunl-client-electron from pritunl)

Issue:

I am unable to connect using Pritunl Client Electron. The client launches, but the VPN connection never establishes.

When I connect directly using OpenVPN, it works perfectly:

sudo openvpn --config ~/Downloads/your-profile.ovpn --verb 4

Relevant log snippets from the working OpenVPN connection:

do_ifconfig, ipv4=1, ipv6=0
net_iface_mtu_set: mtu 1500 for tun0
Initialization Sequence Completed
Data Channel: cipher 'AES-128-GCM', peer-id: 0, compression: 'stub'

Network interface is up:

6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
    link/none

DNS is updated via resolvectl.

Client Logs from Pritunl Client:

[2026-2-20 20:46:7][ERROR] Profiles: Failed to sync profile, user not found
RequestError: Profiles: Failed to sync profile, user not found
    at file:///usr/lib/pritunl_client_electron/resources/app/dist/static/app.711482.js:25461:35
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
[2026-2-20 20:46:12][INFO] Profiles: Updating profile '0a6795fa04aadac5'

It seems the client tries to sync the profile but fails immediately with a “user not found” error, while direct OpenVPN connections work fine.

2

We detected the same issue in pritunl-client-electron. It gets stuck on “connecting” and then drops the connection, regardless of whether the authentication method is SSO, device-based, or PIN.

The problem appears to be related to the upgrade to OpenVPN version 2.7.0 (on Arch Linux, this package was updated on February 11). If you downgrade to version 2.6.19, it works again without any issues.

We hope the issue is resolved soon.

1 Like
3

if you are running OpenVPN v2.7.0-1 it could be this issue:

solved with the current client code or by downgrading OpenVPN

1 Like
4

Thanks you, current client code not works, but downgrading OpenVPN to 2.6.19 works fine.

1 Like