---
title: 'Tutorial: Get Started with Access Server'
canonical: https://openvpn.net/as-docs/v3/tutorials/tutorial--access-server-install-and-set-up/
product: Access Server Docs
description: New to Access Server? This tutorial walks you through choosing a deployment method (Linux, cloud, VM, or container), completing initial setup, connecting your first VPN client, and securing your deployment.
---

# Tutorial: Get Started with Access Server

## Overview

This tutorial helps you get Access Server running from start to finish. It doesn't repeat installation instructions. Instead, it guides you to the right deployment guide for your environment, walks you through initial configuration after installation, and points you to the next steps that matter most for your setup.

Access Server is a self-hosted business VPN solution. You install it on your own infrastructure — Linux, cloud, virtual machine, or container — and manage it through the Admin Web UI.

## Step 1: Choose your deployment method

Use the table below to go directly to the right guide for your environment:

| **I want to deploy on...** | **Use this guide** |
| --- | --- |
| Ubuntu (recommended for most users) | [Ubuntu Quick Start Guide](https://openvpn.net/as-docs/v3/ubuntu.md) |
| Debian | [Debian Quick Start Guide](https://openvpn.net/as-docs/v3/debian.md) |
| Red Hat Enterprise Linux, Rocky Linux, or AlmaLinux | [Red Hat Quick Start Guide](https://openvpn.net/as-docs/v3/rhel.md) |
| AWS (bring your own license) | [AWS BYOL](https://openvpn.net/as-docs/v3/aws-byol.md) |
| AWS (pay as you go) | [AWS PAYG](https://openvpn.net/as-docs/v3/aws-payg.md) |
| Azure (bring your own license) | [Azure BYOL](https://openvpn.net/as-docs/v3/azure.md) |
| Azure (pay as you go) | [Azure PAYG](https://openvpn.net/as-docs/v3/azure-payg.md) |
| Google Cloud | [Google Cloud](https://openvpn.net/as-docs/v3/google-cloud.md) |
| IBM Cloud | [IBM Cloud](https://openvpn.net/as-docs/v3/ibm.md) |
| Oracle Cloud | [Oracle Cloud](https://openvpn.net/as-docs/v3/oracle.md) |
| DigitalOcean | [DigitalOcean](https://openvpn.net/as-docs/v3/digitalocean.md) |
| Vultr | [Vultr](https://openvpn.net/as-docs/v3/vultr.md) |
| VMware ESXi | [ESXi deployment](https://openvpn.net/as-docs/v3/esxi.md) |
| Microsoft Hyper-V | [Hyper-V deployment](https://openvpn.net/as-docs/v3/hyper-v.md) |
| Docker | [Docker deployment](https://openvpn.net/as-docs/v3/docker.md) |
| Raspberry Pi | [Rapberry Pi deployment](https://openvpn.net/as-docs/v3/raspberry-pi.md) |
| Access Server Link | [Access Server Link](https://openvpn.net/as-docs/v3/access-server-link.md) |

> **Note**
>
> Not sure which to choose? For most new deployments, installing on Ubuntu is the fastest path to a working server. See [System Requirements](https://openvpn.net/as-docs/v3/system-requirements.md) for the supported operating systems and hardware requirements.

**Complete the installation for your chosen platform, then return here for Step 2.**

## Step 2: Complete the initial setup

After installation, use the Admin Web UI to complete the initial Access Server setup.

The exact first-run sequence depends on your deployment method. Some cloud deployments can preconfigure administrative credentials, licensing, or a browser-trusted certificate during deployment.

### 1. Sign in to the Admin Web UI

Your installation or deployment output provides the Admin Web UI URL and initial administrative credentials. For a command-line installation, the output may look similar to:

```
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/
```

1. Open a browser.
2. Navigate to the Admin Web UI URL provided during installation. For example: `https://198.51.100.130:943/admin`.
3. If a certificate warning displays, continue to the site.

   > **Tip**
   >
   > Depending on your deployment, Access Server may already have a browser-trusted certificate configured. Otherwise, it uses a self-signed certificate. The self-signed certificate still encrypts the connection, but browsers display a warning because they can't automatically verify the server's identity.
4. Enter the administrative username and password provided during installaion.
5. Review and accept the End User License Agreement to proceed to the Admin Web UI.

### Activate Access Server, if required

Some new BYOL deployments require activation before you can access the rest of the Admin Web UI.

If **Activate your Access Server** displays:

1. Open the Access Server Hub in another browser tab or window.
2. Create a free subscription for your deployment.
3. Copy the new activation key.
4. Return to the Admin Web UI and enter the activation key.
5. Select **Activate**.

Your available VPN connections update based on the activated subscription, and you can continue with setup.

This mandatory activation step appears only on deployments that require activation.

### 3. Complete the Onboarding Wizard

On a fresh Access Server 3.2.2 or newer installation, the Onboarding Wizard can display during the first-run experience.

1. Select whether VPN clients should have:
   - Internet access through Access Server.
   - Access to private resources behind Access Server.
   - Both, if appropriate for your deployment.
2. If access to private resources is enabled, review the network CIDRs that Access Server detected.
3. Verify that the detected networks match the resources VPN users should access.
4. Keep only the networks that VPN users should be allowed to access.
5. Select **Continue**.
6. Review the OpenVPN Connect download offered by the wizard.

   The wizard displays the download appropriate for the operating system of the device you're currently using.
7. Select **Download**.
8. Install OpenVPN Connect.
9. Return to the onboarding wizard.
10. Select **Continue**.
11. The wizard displays a prompt while it waits for a VPN connection.
12. Launch OpenVPN Connect on your device.
13. Connect using the profile included.
14. Confirm that the VPN connection succeeds.
15. Return to the Admin Web UI.
16. Select **Finish Wizard**.

    > **Tip**
    >
    > You can also close the onboarding wizard by selecting the **X** if you prefer to skip these steps.
17. After completing the wizard, the Admin Web UI opens and presents a short product tour covering:
    - The Client Web UI
    - Users
    - Access Controls
    - Authentication
    - Activation

### 4. Change the default password

Change the default `openvpn` admin password immediately after signing in for the first time:

- [Tutorial: How to Change the Password for Your New Administrative Account](https://openvpn.net/as-docs/v3/tutorials/tutorial--change-admin-user-password.md)

### 5. Configure the hostname

For VPN clients to connect from outside the network, Access Server needs to know its public hostname or IP address. We recommend setting up a public domain name:

- [Tutorial: Setting Up Your Access Server Hostname for the Admin/Client Web UIs](https://openvpn.net/as-docs/v3/tutorials/tutorial--custom-hostname.md)

### 6. Verify Access Server is running

1. Confirm the service is running from the console:

   ```
   systemctl status openvpnas --no-pager
   ```

   - Look for `Active: active (running)` in the output.
2. Confirm the service is running via the `sacli` tool:

   ```
   sacli status
   ```

   - Confirm the output includes `"api": "on"` in the `service_status` block. That indicates Access Server is fully initialized and ready to accept connections.

## Step 3: Connect your first VPN client

With Access Server configured, connect a device to verify everything is working before adding more users or configuring advanced settings.

### 1. Create a user

Create a user to test connection status:

- [Tutorial: Adding Users to Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--adding-users.md)

### 2. Install OpenVPN Connect

OpenVPN Connect is the official VPN client for Access Server. Install it on the developer or end-user device:

- [Installing OpenVPN Connect](https://openvpn.net/as-docs/v3/installing-openvpn-connect.md)

  > **Tip**
  >
  > We recommend you install OpenVPN Connect with a bundled connection profile. That way, you can open the app and already have the profile to connect.

### 3. (If needed) Download a connection profile

A connection profile (`.ovpn` file) contains everything the client needs to connect to your server. Users can download their profile directly from the Client Web UI at `https://YOUR-IP:943`.

For other distribution methods, see [Connection Profiles](https://openvpn.net/as-docs/v3/connection-profiles.md).

### 4. Connect

Once the profile is imported into OpenVPN Connect, select it and authenticate to establish the VPN connection. See more:

- [Tutorial: Connect to Access Server on Windows with OpenVPN Connect](https://openvpn.net/as-docs/v3/tutorials/tutorial--connect-with-windows.md)
- [Tutorial: Connect to Access Server on macOS with OpenVPN Connect](https://openvpn.net/as-docs/v3/tutorials/tutorial--connect-with-macos.md)
- [Tutorial: Connect to Access Server with Linux](https://openvpn.net/as-docs/v3/tutorials/tutorial--connect-with-linux.md)

## Step 4: Configure your VPN

With a working connection confirmed, configure Access Server for your organization's requirements. Use the section links below to navigate to the relevant tutorials:

| **What you want to configure** | **Where to go** |
| --- | --- |
| Authentication (local, LDAP, SAML, PAM) | [Authentication tutorials](https://openvpn.net/as-docs/v3/tutorials/authentication---access-control.md) |
| DNS settings | [Tutorial: Configure DNS Settings in Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--configure-dns-settings.md) |
| Routing (split tunnel, full tunnel, domain routing) | [Networking & Topology tutorials](https://openvpn.net/as-docs/v3/tutorials/networking---topology.md) |
| Users and user management | [User and Group Setup](https://openvpn.net/as-docs/v3/tutorials/user-and-group-setup.md) |
| Access Controls | [Tutorial: How to Configure Group Access Control](https://openvpn.net/as-docs/v3/tutorials/tutorial--group-access-control.md) |
| VPN certificates and PKI | [VPN Certificates and PKI Management](https://openvpn.net/as-docs/v3/tutorials/vpn-certificates-and-pki-management.md) |
| Multi-factor authentication (MFA) | [MFA tutorials](https://openvpn.net/as-docs/v3/tutorials/multi-factor-authentication--mfa.md) |

## Step 5: Secure your deployment

Before going to production, complete these recommended security steps:

### 1. Install an SSL certificate

Replace the self-signed certificate with a trusted SSL certificate so clients and admins don't see browser warnings:

- [Tutorial: How to Install a Valid Web SSL Certificate in Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--install-ssl-certificate.md)
- [Tutorial: How to Use ACME Client to Issue Web SSL Certificates for the Access Server UI](https://openvpn.net/as-docs/v3/tutorials/tutorial--acme-web-ssl-certificates.md)

### 2. Configure MFA

Add multi-factor authentication to protect admin and user accounts:

- [MFA tutorials](https://openvpn.net/as-docs/v3/tutorials/multi-factor-authentication--mfa.md)

### 3. Create dedicated administrator accounts

Avoid using the default `openvpn` account for day-to-day administration. Create named admin accounts and secure the root user:

- [Tutorial: Adding Users to Access Server](https://openvpn.net/as-docs/v3/tutorials/tutorial--adding-users.md)
- [Tutorial: How to Secure the Root User Account on a Virtual Appliance](https://openvpn.net/as-docs/tutorials/tutorial--secure-root-user.md)

### 4. Back up your configuration

Take a configuration backup before making further changes or before any upgrade:

- [Tutorial: How to Back Up Access Server Configuration](https://openvpn.net/as-docs/v3/tutorials/tutorial--configuration-backup.md)

### 5. Activate your license

Access Server includes two free connections. To support more connections, activate a subscription license:

- [Tutorial: Purchase and Activate an Access Server Subscription License (Admin Web UI)](https://openvpn.net/as-docs/v3/tutorials/tutorial--activate-subscription-license.md)
- [Tutorial: Activate a Subscription License Key Using the Command-line Interface](https://openvpn.net/as-docs/tutorials/tutorial--activate-subscription-license-cli.md)

---

Prev: [Initial Server Configuration](https://openvpn.net/as-docs/v3/tutorials/initial-server-configuration.md)
Next: [Tutorial: Using the Access Server Onboarding Wizard and Admin Web UI Tour](https://openvpn.net/as-docs/v3/tutorials/tutorial--onboarding-wizard.md)
Index: https://openvpn.net/as-docs/llms.txt