Configuring and connecting to a Self-managed VPS

Overview

This article describes how to purchase and configure a Self-managed VPS in the DreamHost panel, and how to connect to your server over SSH once it finishes provisioning. Self-managed VPS gives you full root access to a Linux environment that you configure, maintain, and secure yourself. For a description of the product, base OS choices, and the app library, see the Self-managed VPS overview.

Your base OS and app image selections cannot be changed after the server launches without reprovisioning. The authentication credentials you choose are set during provisioning and are not stored by DreamHost. If you lose your SSH key or root password, you will need to provision a new server.

Configuring a Self-managed VPS

To purchase and configure a Self-managed VPS:

  1. Navigate to the Servers & Usage page.
  2. Click the +Add Service button. A pop-up displays.
  3. Select Self-Managed VPS from the list. The Self-Managed VPS page opens.
  4. On this page, select a billing term (Monthly, Yearly, or 2 Years) and a plan size (Stack 4, 8, 16, or 32).
  5. Click Select Plan. A cart page opens with your order.

Next, configure your server image, access, and domain on the cart page:

  1. Under the Select Your Configuration section, choose a base OS or app image.

    • Base OS — Debian is the default OS. You can also choose Ubuntu or AlmaLinux.
    • Apps — Choose app images to add to your server.

    This selection cannot be changed after the server launches without reprovisioning.

  2. Under the Secure VPS Access section, choose an authentication method (see the options below). The credentials you choose are set during provisioning and are not stored by DreamHost. Make sure to save your credentials during this step.
  3. Under the Connect a Domain section, select an option to enter a domain name. This step is optional and can be configured after provisioning.
  4. Click Submit Order.

Your server begins provisioning automatically. Once complete, it appears on the Servers & Usage page, where you can select the App Info tab to monitor your new server.

Authentication method — SSH key (recommended)

An SSH key lets you securely access your VPS without a password. First create a key pair on your Windows or Mac/Linux computer, then add the public key during configuration.

  1. Click the Add New Key button.
  2. In the Name field, enter a label to identify this key (for example, my-laptop).
  3. Copy and paste the entire contents of your .pub key file into the SSH Key field. This was created when you originally created the key pair.
  4. Click Save SSH Key.

Authentication method — root password

A root password gives you full server control. It is not possible to set a custom password.

  1. Click Generate Password.
  2. Check the confirmation box, then click the Confirm button. A password is automatically generated and displayed once.
  3. Click the eye icon to view the password.
  4. Save this password somewhere safe, as it is not possible to view it after this order is complete.

Connecting to your server

Once your server finishes provisioning, connect to it over SSH:

  1. Navigate to the Servers & Usage page.
  2. Click Manage next to your new server.
  3. Select the App tab. Here you will find the server's IP address, login user, and a ready-to-use SSH login command.
  4. Run the command that matches your key (see below) to connect.

The login user varies depending on the base OS you selected at provisioning. For example, Ubuntu uses ubuntu and Debian uses debian. Always confirm the correct user in the App tab before connecting — using the wrong user is one of the most common causes of a failed connection.

Default key name — If your key is in the default location (~/.ssh/id_ed25519), SSH detects it automatically. Use the command shown in the App tab:

[local]$ ssh user@your-server-ip

Custom key name — If you saved your key with a custom name or path, use the -i flag to specify it:

[local]$ ssh -i ~/.ssh/your-key-name user@your-server-ip

Replace ~/.ssh/your-key-name with the actual path to your private key file, and user with the login user shown in the App tab.

See also

Did this article answer your questions?

Still not finding what you're looking for?