Skip to main content
StartMyVPN can provision and configure a VPN server end-to-end on any of three paths: All three methods use the same background installation job — the only difference is who creates the underlying VPS.

​
Deploy on DigitalOcean

Requires a configured DigitalOcean API token. See DigitalOcean setup.
  1. Go to Admin → Deployments → DigitalOcean
  2. Fill in the form:
    • Region — geographic location for the droplet
    • Size — instance size
    • Protocol — OpenVPN or WireGuard
    • Server Name — display label shown to users
    • Country / City — shown in the user-facing server list
  3. Click Deploy
StartMyVPN creates the droplet, waits for it to boot, then connects via SSH and runs the VPN installation script automatically.

​
Deploy on Vultr

Requires a configured Vultr API key. See Vultr setup.
  1. Go to Admin → Deployments → Vultr
  2. Fill in the form with region, plan, protocol, and display info
  3. Click Deploy

​
Deploy on a custom server

Use this when you already have a VPS — from any provider (AWS, Hetzner, OVH, etc.) or a dedicated server. StartMyVPN connects via SSH and installs the VPN software automatically, exactly the same as for DigitalOcean and Vultr deployments.

​
Requirements for the custom server

  • OS: Ubuntu 20.04+ or Debian 10+
  • Access: Root or sudo-capable SSH user
  • SSH port: Port 22 open (or specify a custom port)
  • Clean install: Ideally a fresh VPS with no conflicting VPN software

​
Steps

  1. Go to Admin → Servers → Add Server
  2. Complete the 3-step wizard:
Step 1 — Location Step 2 — SSH Access Step 3 — Review & Deploy Review the summary and click Deploy Server. StartMyVPN will:
  1. Connect to the server via SSH using the credentials provided
  2. Automatically install and configure the selected VPN protocol
  3. Register the server and mark it active
Installation typically takes 3–5 minutes and runs in the background via the queue worker.
The queue worker must be running for deployment to proceed. See Queue Workers.

​
SSH credential security

SSH passwords are encrypted at rest using Laravel’s Crypt facade (AES-256-CBC). They are only decrypted in memory during installation and are never logged or displayed after the server is saved.

​
Post-deployment steps

After any server is deployed (regardless of method):
  1. Go to Admin → Server Groups and add the new server to a group
  2. Assign the server group to one or more Plans (Admin → Plans → Edit Plan)
  3. Users subscribed to those plans will see the server in their dashboard immediately

​
Monitoring deployment progress

Deployment jobs log progress to storage/logs/laravel.log. Check queue status:
If a deployment fails, the job retries up to 3 times before landing in the failed jobs table:

​
Google Places API (optional)

The city autocomplete field in the custom server wizard uses Google Places. To enable it:
  1. Obtain a Google Maps API key with the Places API enabled
  2. Enter it in Admin → Settings → API → Google Maps API Key
Without this key the city field is a plain text input — you can still type city and country names manually.