How to Install OpenVPN on a LightNode VPS

LightNode
By LightNode ·

LightNode provides the Linux VPS for OpenVPN. OpenVPN itself is not pre-installed on the standard VPS created from the OpenVPN landing page, so you choose the edition, install it, and maintain the server.

This guide uses OpenVPN Access Server because its official installer and web interface provide a short, reviewable setup path. OpenVPN Community Edition is also available, but its certificate authority, server configuration, client profiles, and routing rules require a longer manual setup.

Create a Linux VPS for OpenVPN

Choose a server location and plan

Start with 1 vCPU and 2 GB of RAM for initial testing and a small number of users. Choose a LightNode location near the people or private services that will connect. Hourly billing makes it practical to test more than one route before settling on a location.

Create an Ubuntu 24.04 or another operating system currently supported by OpenVPN Access Server. Save the public IP and SSH credentials.

Connect to the VPS

ssh root@YOUR_SERVER_IP

Update the package index and installed security updates:

sudo apt update
sudo apt upgrade -y

Confirm the operating system before choosing an OpenVPN installer:

cat /etc/os-release
uname -m

Open the required ports

OpenVPN's current Access Server documentation lists these ports for a standard deployment:

  • TCP 443 for the web interface and OpenVPN TCP connections
  • TCP 943 for the web interface and API communication
  • UDP 1194 for OpenVPN UDP connections

Add only the ports you use to the LightNode firewall or the firewall running inside the VPS. Restrict the administrative interface to trusted source addresses when your network design allows it.

The official Access Server installation guide remains the source of truth for supported operating systems and ports.

Run the official Access Server installer

  1. Create or sign in to an OpenVPN account.
  2. Open the Access Server portal.
  3. Select the Linux distribution running on the VPS.
  4. Copy the installation command generated by the portal.
  5. Run that command in the SSH session.

The generated command changes with the operating system and repository, so copying it from the OpenVPN portal is safer than keeping an old installer command in a tutorial.

When installation finishes, save the Admin Web UI address, Client Web UI address, temporary username, and temporary password shown in the terminal.

Sign in and change the administrator password

The Admin Web UI normally uses a URL similar to:

https://YOUR_SERVER_IP:943/admin

Your browser may warn about the initial self-signed certificate. Confirm that the IP is your new VPS before continuing. Sign in with the temporary credentials and replace the temporary password immediately.

Add a hostname and a valid TLS certificate before inviting production users. A hostname also prevents client profiles from depending on a raw IP if the server address changes later.

Add a user and download a profile

Create a separate OpenVPN user for each person who needs access. Avoid sharing one account across a team because separate accounts and profiles are easier to revoke and audit.

The Client Web UI normally uses:

https://YOUR_SERVER_IP:943/

Sign in as the new user and download the profile or the OpenVPN Connect package offered for the device. Import the profile into OpenVPN Connect and start the connection.

Test the connection

Check the client log and confirm that the connection completes. Then test the specific private resources the user should reach. A successful connection does not prove that DNS, route permissions, and every private service are correct.

On the server, check the Access Server services and recent logs using the commands documented for the installed version. Keep the original SSH session open while changing network or authentication settings so you have a recovery path.

Community Edition alternative

OpenVPN Community Edition is open source and can run on the same LightNode Linux VPS. Its official setup covers PKI creation, server and client configuration, routed or bridged networking, startup services, and certificate revocation.

Use the OpenVPN Community How-To for that path. Do not copy an old sample configuration without checking its cryptographic and routing settings against the current documentation.

Ongoing maintenance

  • Install operating system and OpenVPN security updates.
  • Revoke profiles when a user or device no longer needs access.
  • Back up configuration and certificate material securely.
  • Review exposed ports and administrator source addresses.
  • Watch CPU, memory, and network use before increasing the plan.

LightNode manages the VPS infrastructure. You remain responsible for OpenVPN licensing, users, certificates, routes, firewall rules, logs, and software updates.