Not connected to Privasee VPN sites see your real address 216.73.216.204 · create an account

Setup guides Linux

Set up a VPN on Linux

Linux is where the manual route shines, and we support it fully. Our packages for Debian, Ubuntu and Mint (.deb) and Fedora, RHEL and openSUSE (.rpm) install the desktop app and pull in OpenVPN as a dependency. If you prefer plain OpenVPN, a single .ovpn file from the config generator runs from the command line, as a systemd unit that comes up at boot, or imported into NetworkManager so the tunnel sits in your desktop's network menu.

Linux

Easiest: the Privasee VPN app v2.4.9

Same app as Windows. Installing the package pulls in OpenVPN automatically; your desktop asks for your password once per session to start the tunnel.

Or use any OpenVPN client

You do not have to install our app. The network is standard OpenVPN, so any client connects with a .ovpn profile — useful on a machine you would rather not install software on, or if you already run OpenVPN.

  1. Install OpenVPN: sudo apt install openvpn (Debian/Ubuntu) or sudo dnf install openvpn (Fedora/RHEL).
  2. Download a profile from the config generator.
  3. Test it: sudo openvpn --config ./profile.ovpn
  4. To run it as a service: sudo cp profile.ovpn /etc/openvpn/client/vpn.conf && sudo systemctl enable --now openvpn-client@vpn
  5. For NetworkManager: Settings -> Network -> VPN -> + -> Import from file.

Profiles come from the config generator (sign in first). Generate one per device — that way losing a device means revoking just that profile.

For DNS to follow the tunnel, install openvpn-systemd-resolved and uncomment the script-security lines in the profile.

Troubleshooting

AUTH_FAILED right after connecting

The certificate is fine but the account was rejected: an expired subscription, a revoked device, or too many simultaneous connections. Check your dashboard.

TLS handshake keeps timing out

UDP is probably blocked on that network. Use the TCP profile - it runs on port 443 and looks like ordinary HTTPS traffic to most filters.

Connected but no internet

Usually a DNS problem. Confirm the client applied the pushed DNS server, and on Windows keep block-outside-dns on.

Speeds are poor

Try a closer location and prefer UDP. TCP-over-TCP is slow by design and should only be a fallback.

Other platforms

Plans and prices are on the Pricing page; every location is listed on the Server network page with live load.