VPN Setup

Set up Cloud1VPN on Unix with OpenVPN

Install OpenVPN, import your Cloud1VPN .ovpn profile, connect, and verify your public IP.

OpenVPN setup for Unix

Choose a VPN protocol

Before you begin

You need an active Cloud1VPN server configured for OpenVPN. Open My Servers and retrieve a personal .ovpn profile before importing it into your client.

Get your OpenVPN configuration

Unix setup

Connect with OpenVPN

Use an official OpenVPN client with the personal .ovpn profile generated for your Cloud1VPN server.

  1. Install OpenVPN

    Install the OpenVPN community client through your package or ports collection. Use the official community download page if a package is not available.

    Open the official OpenVPN download page

  2. Download your OpenVPN profile

    Open My Servers, choose the OpenVPN server, and download its personal .ovpn configuration file. Do not share or edit the embedded credentials.

  3. Import the profile

    Keep the .ovpn file in a private location, then start OpenVPN with that profile using your service manager or the openvpn --config command.

  4. Connect

    Start the imported profile and approve any Unix request to create the VPN connection or install its network component.

  5. Verify your connection

    Wait for the client log to report a successful connection, then confirm that your public IP matches the Cloud1VPN server.

    Open What's My IP?

Frequently Asked Questions

Unix OpenVPN setup & troubleshooting

Why will the .ovpn profile not import?

Keep the profile in a private readable location and start it with the OpenVPN package or service installed on your system. Check that the command is loading the intended file rather than an older profile with the same name. Profiles copied through a rich-text editor or messaging app can be damaged, so download a fresh file directly from My Servers when import fails.

What does a TLS handshake timeout mean?

The client reached the connection stage but did not complete the secure exchange. Common causes are a stale server address, a blocked network path, an offline server, or a profile from before a rebuild. Retry on a different trusted network and download a fresh profile before editing transport or certificate fields.

Why does OpenVPN report a certificate verification error?

Confirm the Unix date, time, and timezone are correct, then replace the profile with a current download. Do not remove certificate-verification directives to make the warning disappear; they protect you from connecting to the wrong server.

Why am I being asked for credentials unexpectedly?

Use only the credentials or certificate behavior described by the Cloud1VPN profile. An unexpected prompt can mean the wrong profile was imported or an embedded credential is no longer valid. Do not guess with your Cloud1VPN account password unless the member area explicitly instructs you to use it.

OpenVPN says connected, but websites do not load. What should I check?

First open What's My IP?. If it loads with the Cloud1VPN address, the tunnel works and DNS is the likely problem. If it does not load, check routes, local firewall rules, and competing VPN or proxy software before changing the profile.

Why is my normal public IP still visible?

The client may have connected without installing the default route, or another network service may have higher priority. Remove duplicate profiles, disconnect other VPN clients, reconnect the Cloud1VPN profile, and verify the client log does not show a route-add failure.

Why does OpenVPN repeatedly reconnect or drop?

Use the OpenVPN service log to find the first reconnect, TLS, or route error. Interface changes and competing route managers can leave the process running without a usable route. Repeated TLS errors point back to the server path or profile; route errors after a successful connection point to the local network configuration.

What should I send support for an OpenVPN problem?

Include the Unix version, OpenVPN client version, Cloud1VPN server name, failure time and timezone, and the first relevant log error. Never send the .ovpn file, private key, certificate password, or account password.