Installing Plesk on DigitalOcean

Provided Product Configurations

The following Plesk configuration is available on DigitalOcean.

Plesk Components set

Plesk Web Admin Edition SE (Ubuntu 18.04)

Recommended set* (Fail2Ban, ModSecurity, Plesk Firewall, and **WordPress Toolkit are installed by default). Additionally, the DigitalOcean DNS extension is installed by default.

Note: *The Recommended components set includes all components necessary for web hosting (including the web server, a mail server, a database server, and so on), plus the most popular and widely used features. For more information about Plesk Web Admin Edition SE (Ubuntu 18.04), see the topic Plesk Web Admin SE.

Note: ** WordPress Toolkit in Plesk Web Admin Edition SE (Ubuntu 18.04) provides only basic functionality. To use premium WordPress features, upgrade your Plesk license to Web Pro or Web Host Edition.

Installing Plesk on DigitalOcean
  1. Log in to an existing DigitalOcean account or create a new one.
  2. Click Create > Droplets in the right upper corner of the screen.

    1 - Copy

  3. Go to the “One-click apps” tab and select Plesk on 18.04.

    2 - Copy

  4. Choose the droplet size.

    You can choose one of the standard droplets paying attention to the amount of memory it comes with.

    The more websites you intend to host and the more traffic the hosted websites generate, the more memory you will need. Estimate the amount of memory your setup will require.

    If you want to try out Plesk on DigitalOcean, you can choose the smallest possible droplet (1 GB/1 vCPU), which is sufficient for testing. If later you find yourself running out of resources, you can upgrade your droplet.

    3 - Copy

  5. Adding block storage is not necessary for Plesk to operate. You can skip this option and go to the next step.
  6. Choose the datacenter region. If you plan to host small business websites, we recommend choosing the zone closest to their geographic location to reduce page load times for local visitors.
  7. Additional options such as Private networking, Backups, User data, and Monitoring are not necessary for most Plesk users. You can skip them and go to the next step.
  8. Click New SSH key to add a new SSH key or select a previously added key (if you have any).

    Note: You must add an SSH key because Plesk droplets do not currently support password authentication.

  9. Choose how many Plesk instances you want to deploy and give each one a recognizable name.

    3 - Copy

  10. (Optional) At this point, your Plesk instance is ready to be deployed. If you plan to deploy several instances or to deploy more of them in the future, you may want to group your instances by tagging them. You can manage every instance with the same tag at once.
  11. Click Create.

Your Plesk instance is being deployed. You can start working in Plesk once the deployment is finished.

To access Plesk for the first time:

  1. Connect to the instance using the SSH key you added earlier. You can use any SSH client, for example, PuTTY.
  2. Run the following command to generate a one-time login link:

    sudo plesk login

  3. Plesk will generate two login links. Go to the second login link https://<public-ip-address>:8443/, for example
  4. You will be redirected to the Plesk welcome screen. Provide your contact name and email, accept the End-User License Agreement, and set an administrator password (you will then log in to Plesk using that password). Once you have finished, click Enter Plesk to log in to Plesk.

    6 - Copy

    Note: If you log in to a Plesk instance that is still being deployed, you will see the maintenance screen. Once the deployment is finished, the maintenance screen will be gone and you will be able to start using Plesk.

Issues with Sending Email

If you cannot send email from Plesk, check if outbound connections on TCP port 25 are blocked. If they are, contact DigitalOcean support.