OpenVPN Access Server has a dedicated support ticket system with professionals standing by 24/7 across the world to answer any questions you may have. To reach our support ticket system, first create a free account. Once you have created an account — or if you already have an account — you can log-in and submit a ticket. We will be in touch right away.

To access the admin web interface, point to the public Elastic IP address you assigned and log in with the admin user you set up. The admin web interface URL has the following format: https://xxx.xxx.xxx.xxx/admin.

You can download connection clients that include profiles directly from the public IP address of your Access Server. You can also download clients directly from our site and import profiles from your computer or from your server.

If you don’t find your questions here, you can also click on our general Frequently Asked Questions page for questions regarding licensing, renewals, purchases, and administration.

During the setup of your Azure virtual machine, you should have selected to use an SSH public key under authentication type. If you chose Password instead, you cannot use SSH to access your Azure VM. Using an SSH connection tool such as PuTTY, point to the IP address or hostname of your instance, and load the private key file for authentication. This key must be the same key you used with the Azure VM setup. For more detailed information, please refer to Microsoft’s SSH documentation.

When configuring OpenVPN Access Server on your Azure virtual machine, there is a step where you set up security groups. We have already preconfigured the rules for this so there is no need to create additional rules under NIC network security group. Under Configure network security group, when you click on Create new, you’ll see the preconfigured settings we’ve defined. You can review them and click OK.

Your OpenVPN Access Server resource on Azure needs a Static IP address, rather than a dynamic one. You should assign this when you are creating your resource. To do this, you’ll find it under the Networking setup step.

Under Public IP, click on Create new and choose from the options that pop up on the right. Enter a Name for the IP, the SKU, and select Static under Assignment.

This step is especially important if you will be getting a commercial SSL certificate that would be valid for your VPN administration portal. Selecting a static IP makes it easier for you to point your DNS records to the correct IP address for a custom domain or FQDN for your VPN server.

Providing a customized hostname for users to connect to the Client UI provides a better experience than remembering an IP address. It’s easier to update a DNS record than requiring users to reinstall client profiles if the IP address changes for any reason. Lastly, SSL certificates require a proper FQDN hostname in order to function properly, which makes this step required to set that up.

Follow these helpful tips in our Azure Quick Start Guide to set up your custom domain or FQDN.

If you need to set up routing, rather than the default NAT, for users connecting to your VPN, you will need to enable IP forwarding and create and assign route tables within your Azure network. To do this, followed the step-by-step instructions on our Azure Quick Start Guide.

For more information about OpenVPN Access Server, refer to our resource page: How to configure the OpenVPN Access Server: The Admin UI.