How to Install Plesk Obsidian on a VPS with Serverspace

Plesk Obsidian is a commercial server control panel designed to simplify the management of websites, domains, SSL certificates, databases, email accounts, backups, and hosting services through a graphical web interface.

Without a control panel, many routine hosting operations must be completed manually over SSH. An administrator needs to create web server configurations, manage virtual hosts, install PHP versions, prepare databases, issue certificates, configure mail services, and maintain backups.

Plesk combines these operations in one interface and helps administrators prepare a VPS for web hosting with fewer manual steps. The panel is suitable for website owners, developers, system administrators, digital agencies, and companies that need to manage several domains from one server.

This guide explains how to deploy Plesk Obsidian through the Serverspace control panel, complete the first login, configure the server hostname, add a domain, upload website files, create a database, issue an SSL certificate, set up email, organize backups, secure the panel, and troubleshoot common problems.

What Is Plesk Obsidian?

Plesk Obsidian is a server and web hosting control panel that runs on top of a supported Linux or Windows Server operating system.

The panel provides tools for:

• adding domains and subdomains;
• creating websites and configuring document roots;
• managing DNS records;
• selecting PHP versions and handlers;
• creating databases and database users;
• issuing and renewing SSL/TLS certificates;
• creating email accounts;
• uploading and editing website files;
• managing FTP accounts;
• configuring scheduled tasks;
• installing supported web applications;
• creating backups;
• reviewing website logs;
• monitoring resource usage.

Plesk does not replace the operating system or the underlying web server. Instead, it provides a management layer for services such as Nginx, Apache, PHP, MariaDB, MySQL, DNS, FTP, and mail components.

Common Plesk Use Cases

Plesk Obsidian can be used for:

• hosting a business website;
• managing several WordPress installations;
• creating a hosting environment for a web agency;
• deploying an online store;
• managing websites for clients;
• hosting PHP applications;
• maintaining staging and production environments;
• controlling multiple domains from one panel;
• administering databases;
• creating domain-based email accounts;
• automating SSL certificate renewal;
• migrating websites from another hosting provider.

The panel is especially convenient when one VPS hosts several projects that require different domains, PHP versions, databases, system users, and backup policies.

Plesk vs Manual VPS Administration

On a clean VPS, an administrator normally configures the following components manually:

• Nginx or Apache;
• virtual hosts;
• PHP and PHP-FPM;
• DNS services;
• FTP access;
• mail services;
• SSL certificates;
• databases;
• system users and permissions;
• backup jobs;
• software updates.

Plesk automates many of these tasks.

For example, adding a new website generally requires the administrator to:

1. enter the domain name;
2. select the hosting type;
3. define the document root;
4. choose a PHP version;
5. upload the website files;
6. issue an SSL certificate.

SSH access remains available, so experienced administrators can combine the web interface with command-line tools.

How a Plesk Server Is Structured

A simplified website request path looks like this:

Plesk manages the configuration that connects these components to a particular domain.

Important Plesk concepts include:

• Server — the virtual machine running the operating system and Plesk.
• Plesk Panel — the web-based administration interface.
• Subscription — a set of hosting resources and settings assigned to one or more sites.
• Domain — a domain name added to the panel.
• Webspace — the environment containing the website files and hosting settings.
• Service plan — a reusable template for subscription limits and features.
• Customer — an account that owns websites and subscriptions.
• Reseller — an account that can create customers and subscriptions.

A personal VPS does not necessarily require customers, resellers, or complex service plans. The server administrator can manage all websites directly.

Plesk Editions and Licensing

Plesk is distributed as a commercial product.

Available features can depend on the license edition, including:

• the number of domains;
• customer account support;
• reseller management;
• access to specific extensions;
• hosting provider functionality;
• advanced administration tools.

A basic edition may be sufficient for one or several personal websites.

A web agency or hosting company managing many customer projects may require a license with a higher domain limit and support for customer or reseller accounts.

Before deploying a production server, verify:

• whether a license is included with the application;
• whether a trial period is available;
• which Plesk edition will be installed;
• how many domains the license supports;
• how the license will be renewed.

Recommended VPS Resources

The required configuration depends on the number of websites, expected traffic, enabled services, and application complexity.

A test server can start with:

• 1–2 vCPUs;
• 2 GB of RAM;
• 20–30 GB of SSD or NVMe storage;
• a public IPv4 address;
• a supported operating system.

For several production websites, consider:

• 2–4 vCPUs;
• 4–8 GB of RAM;
• 40–80 GB of SSD or NVMe storage;
• additional disk space for backups;
• network bandwidth appropriate for the expected traffic.

More resources may be necessary when:

• many websites are hosted on the same VPS;
• resource-intensive CMS platforms are used;
• the server also handles email;
• large databases are stored locally;
• backups are created on the system disk;
• websites receive many concurrent requests;
• antivirus and antispam components are enabled;
• applications run background workers or scheduled jobs.

Plesk Network Ports

Not every port in the following table must be opened. The required firewall rules depend on the services enabled on the VPS.

Database ports should not normally be exposed to the entire Internet. Websites hosted on the same VPS can connect to the database through localhost.

Deploying Plesk Obsidian Through the Serverspace Control Panel

Plesk Obsidian is available in the Serverspace 1-Click Apps catalog.

This deployment method removes the need to download the installer manually or select individual components. Serverspace creates the virtual machine and prepares a ready-to-configure Plesk environment.

Step 1. Start Creating a Server

Sign in to the Serverspace control panel, open the vStack cloud section, and click Create server.

The virtual machine creation wizard will open.

Step 2. Select Plesk Obsidian

At the image selection stage, open the Applications or 1-Click Apps tab.

Find Plesk Obsidian and select the application.

Step 3. Choose a Data Center

Select the region in which the VPS will be deployed.

Consider:

• the geographic location of website visitors;
• latency to external services;
• data residency requirements;
• the location of backup storage;
• the region of other project infrastructure.

For a website with a regional audience, selecting a nearby data center can help reduce page load latency.

Step 4. Configure Server Resources

Choose:

• the number of vCPUs;
• the amount of RAM;
• the disk capacity;
• network bandwidth;
• the virtual machine name.

A practical starting configuration for a small production server is:

• 2 vCPUs;
• 4 GB of RAM;
• 40 GB of NVMe storage.

Example instance names:

or:

Step 5. Configure SSH Access

Select:

• a root password;
• an SSH public key.

SSH key authentication is preferable for a production environment.

Do not store the private key:

• inside a website directory;
• in the Plesk File Manager;
• in a public repository;
• inside an unencrypted website backup;
• in an unprotected text file.

Step 6. Deploy the VPS

Review the configuration and start the deployment.

Serverspace will automatically:

• allocate the selected computing resources;
• create the virtual disk;
• assign a public IP address;
• install the operating system;
• deploy Plesk Obsidian;
• prepare the server for initial configuration.

Wait until the VPS status changes to Active.

Why Deploy Plesk in Serverspace?

This deployment model separates infrastructure management from website administration.

Serverspace is used to control:

• vCPUs;
• RAM;
• virtual disks;
• the public IP address;
• network parameters;
• the virtual machine state.

Plesk is used to manage:

• domains;
• websites;
• PHP settings;
• SSL certificates;
• databases;
• email accounts;
• FTP users;
• backups;
• hosting users;
• scheduled tasks.

VPS resources can be adjusted independently from the website configuration stored in Plesk.

Separate Websites by Workload

Not every project needs to be hosted on the same virtual machine.

Example infrastructure:

Separating workloads reduces the impact of one website or service on the rest of the infrastructure.

Connecting to the Server via SSH

Copy the VPS public IP address from the Serverspace control panel.

Connect:

Replace YOUR_SERVER_IP with the actual server address.

During the first connection, review the host fingerprint and confirm:

Enter the root password or use the private SSH key.

Checking the Plesk Installation

Display the installed version:

List the managed services:

Check whether port 8443 is listening:

Generate a temporary administrator login link:

The command will return a one-time URL that can be opened in a browser.

First Login to Plesk

Open:

The browser may display a certificate warning because the panel initially uses the server IP address or a temporary certificate.

On a Linux server, the first login may be completed with:

• the Plesk administrator account;
• the root username and server password;
• a one-time link generated with plesk login.

During the initial setup, the panel may request:

• the administrator name;
• a contact email address;
• a new password;
• the server hostname;
• the intended server usage;
• license information.

Use an email address that you monitor regularly because Plesk can send system and security notifications to it.

Configuring the Server Hostname

Use a fully qualified domain name for the server:

Check the current hostname:

Change it when necessary:

Create a DNS record:

A correct hostname is particularly important when the VPS runs mail services or uses a trusted certificate for the Plesk panel.

Understanding the Plesk Interface

The main sections include:

• Websites & Domains — websites, domains, hosting settings, and SSL.
• Mail — email accounts and mail domain settings.
• Applications — supported CMS and application installers.
• Files — browser-based file management.
• Databases — databases, users, and administration tools.
• Statistics — resource and traffic usage.
• Extensions — additional Plesk components.
• Tools & Settings — server-wide administration.

The available sections depend on the Plesk edition, installed components, and the permissions of the current user.

Adding the First Domain

Open Websites & Domains and click Add Domain.

Configure:

• the domain name;
• the hosting type;
• the document root;
• the system username;
• a password;
• the preferred domain;
• SSL/TLS support.

Example domain:

Example document root:

Plesk will create the required directories and generate the web server configuration.

Pointing the Domain to the VPS

To open the website from the new server, configure the domain DNS records.

A basic configuration is:

Check the records:

(http://www.example.com[/code)]

DNS changes may require time to propagate.

Uploading Website Files

Open:

Navigate to:

Upload:

• HTML files;
• a PHP application;
• a website archive;
• static assets;
• application configuration files.

The entry point of a static website is usually:

For a PHP application:

Files can also be transferred through FTP, SFTP, Git, or the command line.

Creating an FTP Account

Create a separate FTP account when another person needs access to website files.

Configure:

• the username;
• a strong password;
• the home directory;
• access restrictions.

Do not give a website developer access to the entire server when access to one domain directory is sufficient.

Selecting a PHP Version

Open the PHP settings of the required domain.

Plesk allows you to configure:

• the PHP version;
• the handler type;
• memory_limit;
• upload_max_filesize;
• post_max_size;
• max_execution_time;
• error display;
• additional PHP directives.

For a production website:

• use a supported PHP version;
• disable display_errors;
• avoid unnecessarily large resource limits;
• verify CMS and plugin compatibility.

Creating a Database

Open:

Click Add Database.

Specify:

• the database name;
• the associated website;
• a database user;
• a strong password.

Example application settings:

Do not use a database administrator account in the configuration of an ordinary website.

Importing a Database

A database can be imported:

• through Plesk tools;
• through phpMyAdmin;
• from the command line;
• from a backup.

Example command-line import:

The command line is often more reliable for large SQL dumps than a browser-based interface.

Issuing an SSL Certificate

After the domain points to the VPS, open its SSL/TLS settings.

Request a free certificate and select:

• the primary domain;
• the www subdomain;
• the administrator email;
• additional hostnames when required.

After issuance, enable:

• SSL/TLS support;
• HTTP-to-HTTPS redirection;
• secure webmail access when mail is enabled.

Test the website:

(https://example.com[/code)]

Securing the Plesk Panel with a Trusted Certificate

The administration panel should also use a trusted certificate.

The general process is:

1. configure a valid hostname;
2. create the corresponding DNS record;
3. issue an SSL certificate;
4. assign the certificate to the Plesk panel.

After configuration, open the panel through:

(https://server.example.com:8443[/code)]

This is more convenient and secure than repeatedly opening the server IP and accepting a browser warning.

Creating an Email Account

When the mail service is enabled, open the Mail section.

Create an address such as:

Configure:

• the mailbox name;
• a strong password;
• the storage limit;
• forwarding when required;
• an automatic reply when required.

Correct DNS configuration is necessary for reliable mail delivery.

DNS Records for Email

A mail domain may require:

• an MX record;
• an A record for mail.example.com;
• an SPF record;
• a DKIM record;
• a DMARC record;
• a PTR record for the public IP.

Example SPF:

Example DMARC:

Without a correct PTR record and a trusted IP reputation, messages may be delivered to spam folders.

Installing WordPress

Plesk can install and manage WordPress through the graphical interface.

A typical deployment includes:

1. selecting the target domain;
2. opening WordPress Toolkit;
3. starting the installation;
4. entering the website information;
5. creating the administrator account;
6. choosing the language;
7. starting the deployment.

After installation, verify:

• HTTPS configuration;
• the selected PHP version;
• automatic update settings;
• the backup schedule;
• administrator account security;
• unused plugins and themes.

Configuring Scheduled Tasks

Use the scheduled task interface for commands that must run periodically.

Examples:

• executing a script;
• cleaning temporary files;
• updating application data;
• sending reports;
• running CMS commands;
• creating additional backups.

Example:

Use absolute paths and review task output or logs.

Creating Backups in Plesk

Backup Manager can save:

• subscription settings;
• website files;
• databases;
• mailboxes;
• DNS settings;
• hosting accounts.

Depending on the environment, the panel may support:

• full backups;
• incremental backups;
• manual backup creation;
• scheduled backups;
• local storage;
• remote storage through supported extensions.

Do not keep the only backup on the same disk as the hosted websites.

Recommended Backup Strategy

An example backup schedule:

• daily database backups;
• daily incremental website backups;
• weekly full backups;
• several retained backup generations;
• an off-server copy;
• regular restoration tests.

Check available disk space:

Find large directories:

Updating Plesk

Updates can be installed from the Plesk interface.

A command-line update is also available:

Before a major update:

• create a backup;
• verify available disk space;
• check extension compatibility;
• schedule a maintenance window;
• test the hosted websites after completion.

Installing Plesk Extensions

Extensions can add functionality for:

• backups;
• monitoring;
• security;
• Git integration;
• Docker management;
• WordPress administration;
• website migration;
• cloud storage;
• additional development tools.

Before installing an extension, review:

• its purpose;
• licensing conditions;
• version compatibility;
• resource usage;
• the developer’s reputation;
• the permissions it requires.

Avoid installing extensions that are not needed by the current environment.

Configuring the Firewall

Allow only the services that are actively used.

A basic website server may require:

• 22/TCP;
• 80/TCP;
• 443/TCP;
• 8443/TCP;
• 8447/TCP for Plesk updates.

Open mail, DNS, or FTP ports only when the corresponding services are enabled.

Before changing firewall rules:

• keep the current SSH session open;
• open a second SSH connection;
• verify that port 22 is allowed;
• confirm that port 8443 remains accessible.

Restricting Access to the Panel

Additional security measures include:

• allowing administrator access only from trusted IP addresses;
• changing the default admin username;
• using a strong unique password;
• enabling multi-factor authentication;
• disabling root login through the web interface;
• reviewing active administrative accounts regularly.

Change the administrator login through the CLI:

Use the new username during subsequent logins.

Monitoring Server Resources

Check memory usage:

Monitor current load:

Check disk space:

List the processes consuming the most memory:

Display listening ports:

Regular monitoring can reveal:

• insufficient RAM;
• low disk space;
• unexpected load increases;
• suspicious processes;
• website performance issues;
• excessive backup accumulation.

Useful Plesk Commands

Plesk Security Checklist

• Use SSH key authentication instead of a password.
• Protect the panel with a trusted certificate.
• Change the default admin username.
• Enable multi-factor authentication.
• Restrict panel access to trusted IP addresses.
• Do not expose database ports publicly.
• Create a separate database user for every website.
• Update Plesk and the operating system regularly.
• Remove extensions that are no longer required.
• Separate websites with different trust levels.
• Store backups outside the primary VPS.
• Test the restoration procedure.
• Monitor logs and server resources.
• Use different passwords for Plesk, FTP, email, and databases.
• Do not store credentials in public web directories.

Common Plesk Problems

The Panel Does Not Open on Port 8443

Check whether the port is listening:

Review the firewall:

Test the local interface:

(https://127.0.0.1:8443[/code)]

If the local request succeeds, inspect the cloud firewall or external network rules.

Unable to Log In to Plesk

Generate a temporary login link:

Also verify:

• the administrator username;
• the keyboard layout;
• IP-based access restrictions;
• whether the default admin login was changed;
• whether the panel service is available.

The Domain Does Not Open

Check DNS resolution:

Check the server response:

(http://example.com[/code)]

Verify:

• the A record;
• the assigned IP address;
• hosting settings;
• files in the httpdocs directory;
• web server configuration;
• firewall rules.

The Website Returns a 502 Error

Possible causes:

• PHP-FPM is not running;
• an incompatible PHP version is selected;
• the VPS has insufficient memory;
• the web server configuration is invalid;
• the application backend does not respond.

Run:

Review the domain logs after the repair.

An SSL Certificate Cannot Be Issued

Check:

• domain DNS records;
• port 80 availability;
• an incorrect AAAA record;
• the www record;
• external website availability;
• certificate authority rate limits.

The VPS Is Running Out of Disk Space

Check storage:

Find large directories:

Common causes include:

• old backups;
• large mailboxes;
• logs;
• website cache;
• large databases;
• uploaded archives.

The Database Is Unavailable

Verify:

• the database name;
• the database username;
• the password;
• DB_HOST;
• the MariaDB or MySQL service state;
• the user privileges;
• available disk space.

Email Is Delivered to Spam

Check:

• PTR;
• SPF;
• DKIM;
• DMARC;
• the server hostname;
• the public IP reputation;
• the email content;
• whether the IP is present on blocklists.

Plesk Reports Configuration Problems

Check the installation:

Repair the web server configuration:

Create a backup before allowing an automatic repair tool to modify a production environment.

When Plesk Obsidian Is a Good Choice

Frequently Asked Questions

Deploy Plesk Obsidian with Serverspace

The Plesk Obsidian application in Serverspace allows you to create a web hosting server without manually installing the panel and its basic components.

After deployment, you receive:

• a dedicated virtual machine;
• a public IP address;
• an installed Plesk environment;
• configurable VPS resources;
• SSH access to the operating system;
• a graphical interface for website management;
• domain and DNS tools;
• database administration;
• SSL certificate support;
• a backup management system.

The server can be used for:

• business websites;
• WordPress projects;
• online stores;
• customer websites;
• staging environments;
• domain-based email;
• several independent web applications.

The administrator retains access to the underlying operating system and can manage the firewall, logs, updates, files, and system services.

Conclusion

Plesk Obsidian combines website, domain, PHP, database, SSL, email, user, and backup administration in one web interface.

The panel reduces the amount of manual server configuration and can be used for both a single website and a VPS hosting several independent projects.

Deploying Plesk through Serverspace simplifies the initial server setup. Select Plesk Obsidian from the application catalog, configure the VPS resources, and deploy the virtual machine.

After installation, complete the initial configuration, verify the license, assign a valid hostname, protect the administration panel, add domains, issue SSL certificates, and configure off-server backups.