Setting up VyprVPN Self-Hosted Server via CLI

At this point, you have already followed one of our tutorials for deploying VyprVPN Self-Hosted Server on one of our 3 supported platforms. If not, head back to one of the setup articles listed here.

This tutorial will guide you through configuring server settings via the command-line interface (CLI). If you would prefer to use the web admin panel (recommended), see this article.

Note: VyprVPN Self-Hosted Server CLI functions are controlled using the admin command. At any point, you can run this command and option to see a list of arguments: admin -h. You can also see admin argument options like this, ex: admin server -h

1. Using a standard SSH client (PuTTY, terminal, etc), connect to the public IP address of your VyprVPN Self-Hosted Server on port 222 using the following syntax and credentials:

Username: admin
Password: Grod42decK
Terminal example: ssh -p 222 admin@x.x.x.x (Server IP)

Note: The username and password are case-sensitive.

See "How to access your server via SSH" if you are having trouble connecting using PuTTY or Terminal.

2. Once logged in, you will need to change the default password for admin from the one above. Run this command to set a new, secure password: admin password

3. Now that you have secured the admin password, proceed to secure access to the admin portion of the server. This step is optional but highly recommended as you should not leave admin access open to the world.

(Note: If you deployed on AWS and set up a restrictive security group outlined in the AWS tutorial, you can skip this step.)

This involves setting allowed IP blocks in the firewall. You can add specific netblocks for admin access (CLI and web admin) using this command: admin adminips add x.x.x.x/x (Insert netblock for x)

• For example, if you just wanted to allow your home connection access to the admin interface, you would add your home public IP address: admin adminips add 1.2.3.4/32 (CIDR notation required, /32 is a single IP)
• See all adminips subcommands using this command: admin adminips -h
• Any attempt to access the admin panel via CLI or web interface will be denied unless it's from one of your allowed netblocks.

4. Once you have secured your server, issue this command: admin server register

Upon entering the command, you will be prompted for the following information:

• Username: Your VyprVPN account email address.
• Password: Your VyprVPN account password.
• Server name: The custom name of your VyprVPN Self-Hosted Server. This is the name that will show in the list of server locations in the VyprVPN app.
• Server IP Type: Static or Dynamic. Static will be the most common choice and is used when the server is running on a public IP address that will not change. Use this if you are on Digital Ocean.

Dynamic is used for an IP address that may change at any time. This is useful for Virtual Box setups, where your ISP might change your IP address periodically. When you choose the Dynamic option, you won't need to enter an IP for the step below, as it will be detected automatically and monitored for changes.

If you are using AWS to host your VyprVPN Self-Hosted Server, be aware that by default your public IP will change if you power the instance off.  Therefore you should choose a Dynamic for the IP Type unless you have assigned a static Elastic IP to the instance.  If you assign an Elastic IP to your instance, then you are safe to use the Static IP Type.

• Server IP: The public IP of your server. It will be shown for you, type it in as shown.

5. Congratulations, your VyprVPN Self-Hosted Server server is now live! Head over to this article for information on how to connect to your server.

(Note: After registration, it may take a minute or two for the server's certificate to update. During this time, Wireguard connections to the server will not be possible. You can check the certificate status and refresh using the command admin webcert status and you can refresh the certificate using the command admin webcert refresh)

6. Type exit to close the SSH connection.