This procedure is for an authorized administrator of a self-managed VPS or dedicated server. Confirm your Nabtech service permits that administration and that the required Plesk licence is available. Check the official supported operating-system matrix immediately before installing. Use a clean OS without another hosting panel, a resolvable hostname, adequate resources, working DNS resolution and a tested provider console. Back up any data before changing a reused server; installing over an unrelated live stack is not a migration strategy.

1. Connect by SSH using an authorized root session. Confirm the hostname, OS release, disk space and package-manager health. Apply appropriate base-system updates and restart first if they require it.
2. Choose the supported installer method. For a standard default deployment, obtain the current one-click installer from Plesk:
   Command example

   curl -fSL https://autoinstall.plesk.com/one-click-installer -o plesk-one-click-installer
   less plesk-one-click-installer
   sh plesk-one-click-installer

   Review the downloaded script and source before execution. If you need component selection, use the official interactive installer instead.
3. Read the installer output and resolve a prerequisite error before continuing. Do not ignore a hostname, repository or unsupported-OS error merely because an old tutorial called it a warning.
4. After successful installation, open the trusted initial-login link supplied by the installer. Keep that link private. Complete the contact information, administrator password, licence and required agreement steps.
5. Configure a valid TLS certificate for the panel hostname and review firewall access. Permit only the necessary administration and hosting services; restrict management access to trusted networks where practical. Do not disable the whole firewall to test the panel.
6. Review updates, backup destinations, mail and DNS roles, and default hosting settings before adding production subscriptions. Create a test site first rather than immediately changing customer DNS.

Confirm HTTPS panel login, licence status and component health. Test a small website, database and any mail services you actually plan to provide. Verify an off-server backup and a controlled restore so the installation is operationally useful rather than merely displaying a dashboard.

If installation stops, retain the exact error and installer logs, check the supported OS and repository access, and resolve the stated cause. If the panel cannot be reached, inspect the listening service and specific firewall rules through the console. Do not run several installers concurrently or install a second panel over the failed attempt.

• Logging in to Plesk securely
• Creating and downloading a full subscription backup in Plesk
• Adding another website domain in Plesk
• Creating a website database in Plesk

• Plesk: Installing Plesk For Linux In One Click
• Plesk: Installing Plesk For Linux Using Installer Console