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

Setup guides

Pick your platform. Where we have an app, that is the short way — otherwise any OpenVPN client works, and every profile has the certificates inlined, so there is only ever one file to move.

Windows

Easiest: the Privasee VPN app v2.4.4

Sign in with your account, pick a location, press Connect. OpenVPN is bundled - there is no profile to download or import.

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 Community Edition (the 64-bit MSI) from openvpn.net, or OpenVPN Connect.
  2. Download a profile from the config generator.
  3. Copy the .ovpn file into C:\Program Files\OpenVPN\config\
  4. Right-click the OpenVPN tray icon, choose the profile, and click Connect.
  5. Approve the Windows UAC prompt. The tray icon turns green when the tunnel is up.

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

Keep block-outside-dns enabled (it is in every profile we generate) so Windows cannot leak DNS queries around the tunnel.

macOS

Easiest: the Privasee VPN app v2.4.9

Same app as Windows. Unzip, drag to Applications, sign in. Needs OpenVPN present (brew install openvpn); the app says so if it is missing.

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 Tunnelblick (tunnelblick.net) or OpenVPN Connect from the App Store.
  2. Download a profile from the config generator.
  3. Double-click the .ovpn file - Tunnelblick offers to install it.
  4. Pick "Only Me" when asked who may use the configuration.
  5. Click the Tunnelblick icon in the menu bar and choose Connect.

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

On Apple silicon both clients run natively; no Rosetta needed.

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.

Android

Easiest: the Privasee VPN app v2.4.7

A direct download, not from a store - your phone asks once to allow installs from the browser. Sign in and connect; no profile to import.

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 for Android" (Arne Schwabe) from Play Store or F-Droid.
  2. Download a profile on the phone, or transfer it from a computer.
  3. In the app tap the + icon and choose Import.
  4. Select the .ovpn file, give it a name, and save.
  5. Tap the profile to connect and allow the VPN permission prompt.

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

Enable "Always-on VPN" and "Block connections without VPN" in Android network settings for a kill switch.

iPhone / iPad

There is no Privasee VPN app for this platform, so use any OpenVPN client with a .ovpn profile. The profile carries the location, your certificate and every setting already filled in.

  1. Install "OpenVPN Connect" from the App Store.
  2. AirDrop, e-mail or save the .ovpn file to Files on the device.
  3. Open the file and choose "Copy to OpenVPN".
  4. Press ADD in OpenVPN Connect.
  5. Toggle the connection on and allow the VPN configuration prompt.

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

iOS only allows one active VPN profile at a time.

Router

There is no Privasee VPN app for this platform, so use any OpenVPN client with a .ovpn profile. The profile carries the location, your certificate and every setting already filled in.

  1. Confirm your firmware includes an OpenVPN client (OpenWrt, pfSense, DD-WRT, Asuswrt-Merlin).
  2. Use the "all locations" profile if the firmware supports multiple remotes.
  3. OpenWrt: install openvpn-openssl, copy the profile to /etc/openvpn/, then enable the service.
  4. pfSense: VPN -> OpenVPN -> Clients -> Add, pasting each inline block into its field.
  5. Test from one device before pushing all traffic through the tunnel.

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

A router counts as a single device against your plan, no matter how many machines sit behind it.

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.