--- title: Ubuntu VPN Software Package for Access Server | OpenVPN canonical: https://openvpn.net/as-docs/ubuntu/ product: Access Server Docs description: The best Ubuntu VPN solution — OpenVPN's Access Server works with your Linux distro of Ubuntu, also built on open-source software fundamentals. Get started! --- # Ubuntu VPN Software Package for Access Server | OpenVPN Access Server fits seamlessly with Ubuntu. Access Server gives you the following benefits: - A self-hosted VPN solution. - A simplified, rapid deployment of secure remote access and site-to-site solutions. - A web-based administration interface. - Built-in OpenVPN Connect app distribution with bundled connection profiles. > **Tip** > > Refer to our [system requirements](https://openvpn.net/as-docs/system-requirements.md) to ensure your system works with Access Server. ## ⏰ Install updates and set the correct time We recommend you start by updating your operating system to the latest version and ensure it's set to the correct time: 1. Sign in to your Linux system on the console or via SSH and obtain root privileges. 2. Run the commands below to install updates and set time and date correctly. ``` apt update apt upgrade apt install tzdata dpkg-reconfigure tzdata ``` > **Note** > > We assume your OS comes with a time synchronization tool to ensure the correct date and time. If it doesn't, you must ensure they're correct and consider installing a Network Time Protocol (NTP) client program to keep accurate time on your server. Access Server relies on accurate time for time-based one-time passwords for multi-factor authentication and certificate management. ## 🖥️ Install Access Server with the install script 1. Sign into the [Access Server portal](https://myaccount.openvpn.com/signin/as). 2. Click **Get Access Server**. 3. Under **Install on Linux OS**, copy the `bash` command. 4. From your console or SSH session, copy and paste the command. > **Tip** > > The `curl` command fetches the `install.sh` script from the specified **openvpn.net** URL. The `-f` flag makes `curl` fail silently on servers, `-s` makes it silent (it won't show download progress), and `-S` shows errors if they occur. The `--yes` flag automatically answers **yes** to any interactive prompts during the installation, ensuring it runs without your manual input. > **Important** > > If your operating system version isn't listed as [one we support](https://openvpn.net/as-docs/system-requirements.md), don't proceed, as the commands will likely fail. ## 🔑 Take note of the web interface access and login credentials After installing the **openvpn-as** package, take note of the Admin UI and Client UI addresses as well as the randomly generated password for your administrative user **openvpn**. These display on screen similar to this example: ``` Initial Configuration Complete! You can now continue configuring OpenVPN Access Server by directing your Web browser to this URL: OpenVPN Access Server URL: During normal operation, OpenVPN AS can be accessed via these URLs: Admin UI: https://192.0.2.10:943/admin/ Client UI: https://192.0.2.10:943/ To login please use the "openvpn" account with "FKadk2254" password. See the Release Notes for this release at: https://openvpn.net/vpn-server-resources/release-notes/ ``` ## 🛠️ Activate your subscription and finish configuration Using the information from the previous step, connect to the Access Server and sign in with the **openvpn** user and password. > **Tip** > > The URL for the Admin Web UI is **https://\[address\]/admin/** — replace **\[address\]** with your server's public IP address or DNS hostname. The Access Server Admin Web UI provides an intuitive tool for managing settings for Access Server. The first time you access it, a warning will display. This is expected, as Access Server has a self-signed SSL certificate, so the web service can function. Override this warning message and proceed. > **Tip** > > We recommend you [set up a valid DNS hostname](https://openvpn.net/as-docs/hostname.md) for your Access Server and install [a valid signed SSL certificate](https://openvpn.net/as-docs/tutorials/tutorial--install-ssl-certificate.md). After you sign in and accept the EULA, the **Activation** page displays. Paste your [activation](https://openvpn.net/as-docs/activate-a-subscription.md) here and click **Activate**. ### 🛠️ Finish Access Server configuration Now that you've installed Access Server, follow these next steps. #### Find the URLs for your web server When you complete the installation process on the command line, the output displays the URLs for your admin UI and client UI as well as the username and randomly generated password for the admin account. ``` Initial Configuration Complete! You can now continue configuring OpenVPN Access Server by directing your Web browser to this URL: OpenVPN Access Server URL: During normal operation, OpenVPN AS can be accessed via these URLs: Admin UI: https://192.0.2.10:943/admin/ Client UI: https://192.0.2.10:943/ To login please use the "openvpn" account with "FKadk2254" password. See the Release Notes for this release at: https://openvpn.net/vpn-server-resources/release-notes/ ``` | | | | --- | --- | | **Admin UI** | The Admin UI is the web-based GUI for managing your Access Server. We refer to it as the Admin Web UI. Typically, it is the address of your server with /admin/ appended, for example https://192.0.2.222/admin/. When you sign in to the Admin Web UI, you can manage the configuration, certificate, users, and so on as an administrative user. The web-based GUI provides simplified management of complex VPN features rather than having to run Linux-based commands and scripts. | | **Client UI** | The Client Web UI is the web-based GUI where users sign in to download clients or configuration files. Typically, it is the address of your server, https://192.0.2.222 as an example. > **Tip** > > The web services run on port TCP 943, by default, so you can visit them at https://192.168.70.222:943/ and https://192.168.70.222:943/admin/ as well. The OpenVPN TCP daemon that runs on TCP port 443 redirects incoming browser requests so that it is slightly easier for users to open the web interface by leaving the :943 part out. | #### First time signing into the Admin Web UI ##### Administrative User For the first use of the Admin Web UI, sign in with the **openvpn** user created during setup. The user’s password is randomly generated and displays in the output at the completion of setup. On Access Server versions older than 2.9, you must manually set the password for the **openvpn** user with this command: ``` passwd openvpn ``` You can now open a browser and enter your Admin Web UI address. ##### Invalid Certificate Access Server’s web interface comes with a self-signed certificate. This allows you to sign in to the Admin Web UI right away. Since it’s self-signed, it triggers an expected warning. We recommend adding your own SSL certificate in the Admin Web UI to resolve this. By clicking through to the site, you can continue to the web interface. At the login screen, enter the username and password for your **openvpn** user. #### Activating a subscription The first time you sign into the Admin Web UI, Access Server displays the **Activation** page so you can easily get an activation key: 1. Click **Get Activation Key**. - This takes you to the Access Server portal. 2. Sign in with your openvpn.com account if needed. 3. Click **Activation Keys**. 4. Click **Purchase A New Key**. 5. Select the number of concurrent connections for your subscription. - For a free subscription with two connections, select the free option. - For five or more connections, select the standard option. 6. Once you've finished obtaining a subscription, click **Copy Key** to copy the subscription key. 7. Return to your Admin Web UI. 8. Paste the subscription key in the text field. 9. Click **Activate**. Once your subscription loads, you can see the available connections. When users start connecting, you'll see how many are connected. You can also see the connection details on the Access Server portal by clicking **Access Server Information**. #### Setting up a hostname We recommend configuring a hostname to provide a stable, user-friendly address for the Admin Web UI, Client Web UI, and VPN connections. For example: `vpn.example.com`. This provides an easier user experience than remembering the server's IP address. Refer to [Hostname](https://openvpn.net/as-docs/hostname.md) and follow the steps. #### Setting up authentication Once signed in to the Admin Web UI, you can configure user authentication. Access Server supports local authentication, where you configure users in the Admin Web UI. You can also use an external authentication system with PAM, RADIUS, LDAP, or SAML. Access Server 2.10 and newer supports using multiple authentication systems simultaneously. Refer to [Authentication System](https://openvpn.net/as-docs/user-authentication-system.md) for more information. #### First time connecting to the VPN server With your VPN server configured, your [users can get connected](https://openvpn.net/as-docs/connecting-76719.md). Choose one of the options below to connect to the server. | Connection method | Procedure | | --- | --- | | Download OpenVPN Connect from the Client Web UI | A user follows these steps to download a pre-configured OpenVPN Connect app: Navigate to the Client Web UI in a browser. Sign in with user credentials. Choose the OpenVPN Connect app for their operating system. After it downloads, install the software. Open the app and select the connection profile. The user connects to Access Server. | | Download a connection profile | Follow these steps to download a connection profile. They can then load this file into an installed VPN client like OpenVPN Connect: Navigate to the Client Web UI in a browser. Sign in with their user credentials. Select the link under **Available Connection Profiles**. After the connection profile downloads, upload the file to a VPN client. | | Admin distributes connection profiles or installers | Alternatively, as an admin, you can use these ways to connect your users: Have your users install [OpenVPN Connect](https://openvpn.net/vpn-client/) from our website, then [download a connection profile](https://openvpn.net/as-docs/user-management/#user-profiles-78636) from the Admin Web UI and distribute it to users. [Create an OpenVPN Connect installer from the Access Server command-line](https://openvpn.net/as-docs/tutorials/tutorial--create-connection-profiles/#option-1--create-connection-profiles-using-the-cli) interface and distribute it to users. | > **Tip** > > Once connected, a simple test the user can perform is checking their IP address. If internet traffic travels over your encrypted VPN tunnel, the user's IP address changes when they connect to Access Server. If you configure [split-tunnel traffic](https://blog.openvpn.net/split-tunneling-with-access-server), their IP address remains the same for internet traffic. ## 📋 Recommended next steps 1. [Tutorial: Setting up your Access Server Hostname](https://openvpn.net/as-docs/v3/tutorials/tutorial--custom-hostname.md). 2. [Tutorial: How to Install a Valid Web SSL Certificate in Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--install-ssl-certificate.md). 3. [VPN Network Config](https://openvpn.net/as-docs/v3/vpn-settings-overview.md). 4. [Tutorial: Adding Users to Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--adding-users.md). 5. [Strengthen Security](https://openvpn.net/as-docs/strengthen-security.md). ## 💡 Installation tips - To reach Access Server via the internet, set the hostname or IP address to one facing the public internet. If you set up your server in a private network, it may assume a private IP that can't be reached from the internet. Change this setting by setting up a DNS [hostname](https://openvpn.net/as-docs/hostname.md) that resolves to the public IP address where your Access Server can be reached. - Ensure the right ports are open so your VPN clients can reach Access Server from outside your private network. - Access Server's default, internal VPN subnet is 172.27.224.0/20. You can change the subnet to one that might work better for your current network. ## 📱 OpenVPN Connect Your users and devices need a VPN client program, like OpenVPN Connect, to establish a connection to Access Server. You can obtain the necessary software and connection details from the Client Web UI. This is the same address as the Admin Web UI, minus the /admin part. > **Tip** > > The URL for the Client Web UI is **https://\[address\]/** — replace **\[address\]** with your server's public IP address or DNS hostname. Users can sign in with their credentials and obtain all the necessary client software and configuration to connect to your Access Server. ## 🐧 Helpful Linux tips - Successfully running the Linux commands here requires executing them with root privileges logged in as a root user or sudo up. - By default, an unlicensed server allows only two connections. You can [purchase a subscription](https://openvpn.net/access-server/pricing/) to increase this. - Licensing an Access Server without internet access requires [contacting OpenVPN support](https://openvpn.net/support) for an offline activation procedure. - If you experience slowness with the web interface or license key activation, check that DNS resolution is working as expected. --- Prev: [Linux](https://openvpn.net/as-docs/linux-distributions.md) Next: [Debian](https://openvpn.net/as-docs/debian.md) Index: https://openvpn.net/as-docs/llms.txt