> For the complete documentation index, see [llms.txt](https://docs.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neevcloud.com/neevcloud-guide/neevcloud-knowledgebase/set-up-plesk-in-ubuntu.md).

# Set up Plesk in Ubuntu

**Plesk** is a web hosting and server management control panel that allows administrators and web hosting companies to manage thousands of virtual hosts on a single machine. It offers automation tools that reduce the time web professionals spend on managing websites and the server environment. Plesk supports both Linux/Unix and Windows operating systems, providing a graphical interface for managing websites, email accounts, databases, and more.

## **Prerequisite:**&#x20;

*It works on all Linux distributions.*

Operating System: **Ubuntu 22.04**

Minimum hardware requirements: 2GB RAM and 32GB of storage

A sudo user or root privileges.

### Install Plesk Control Panel on Ubuntu 22.04

Plesk is a popular web hosting control panel that allows you to manage your hosting server. This guide covers the installation of Plesk on Ubuntu 22.04.

### Update && Upgrade&#x20;

Update System Packages Update your Ubuntu 20.04 server's package index:

```
sudo apt update && sudo apt upgrade -y
```

**Download Plesk Installer** Use the curl command to download the Plesk installer script:

```
wget http://autoinstall.plesk.com/plesk-installer
```

<figure><img src="/files/mAoGontOvXvr7ixb4U0m" alt=""><figcaption></figcaption></figure>

**Make Installer Executable** Change the permissions to make the script executable:

```
sudo chmod 755 plesk-installer
```

**Run Plesk Installer** Execute the installer script to initiate the Plesk installation:

```
sudo ./plesk-installer
```

Hit **“F”** if you are using a *fresh* server. Or **“q”** if you need to back up your system data.

<figure><img src="/files/SPGh02gurZ2Ha9Ie3GMK" alt=""><figcaption></figcaption></figure>

*Would you like to assist Plesk in enhancing its products by sharing information about encountered issues, including installation and upgrade problems? \[Y/n]:*

<figure><img src="/files/eya4EEH66MJsjb18YH9A" alt=""><figcaption></figcaption></figure>

*Proceed with the advised approach.*

<figure><img src="/files/kJOZXNiS65ef2iejZef8" alt=""><figcaption></figcaption></figure>

*Go forward with the Product Installation*

<figure><img src="/files/LVZpsmr7abqBOoiRKnSb" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/ZHXfKnyrHWqxmstmRyP0" alt=""><figcaption></figcaption></figure>

*Follow the on-screen instructions to complete the installation process.*

**Post-Installation**

After installing Plesk on Ubuntu 22.04, access the Plesk control panel by navigating to `https://<YOUR_SERVER_IP:8443` your web browser. Log in using the admin credentials established during the installation.

**Conclusion**

Congratulations on successfully installing Plesk on your Ubuntu 22.04 server. With Plesk's intuitive interface, you can now effortlessly manage your websites, databases, and email accounts.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.neevcloud.com/neevcloud-guide/neevcloud-knowledgebase/set-up-plesk-in-ubuntu.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
