Plesk VPS - Getting Started Guide
Your Plesk VPS based on Ubuntu 22.04 comes fully configured - Plesk Obsidian is installed and initialized with the admin password you specified during order. The Plesk panel is ready to use immediately after your VPS is created.
Software Included
| Component | Details |
|---|---|
| Ubuntu | 22.04 LTS |
| Plesk Obsidian | 18.0 (Recommended preset) |
| Web Server | Nginx + Apache |
| Database | MariaDB |
| Postfix + Dovecot | |
| DNS | BIND |
| Security | Fail2Ban |
Step 1 - Your Credentials
Log in to your client panel and open your VPS service details. Find the IP address and root password (for SSH).
Plesk panel login:
- Username:
admin - Password: the Admin Password you entered during the order
Step 2 - Access Plesk Panel
Plesk panel is available immediately after your VPS is created:
https://your.server.ip:8443
Log in with username admin and the Admin Password from Step 1.
Note: Plesk uses a self-signed SSL certificate by default. Your browser will show a security warning - this is expected. Click "Advanced" and proceed to access the panel.
Step 3 - Add Your First Domain
In Plesk panel, click Add Domain and enter your domain name. Plesk will create the web space, DNS zone and mail configuration automatically.
Before adding a domain, point it to your server by creating an A record at your domain registrar:
| Type | Name | Value |
|---|---|---|
| A | @ | your.server.ip |
| A | www | your.server.ip |
DNS changes usually take a few minutes, but can take up to 24 hours. You can check the status at dnschecker.org.
Step 4 - Enable SSL for Your Domain
Plesk has a built-in Let's Encrypt integration. To enable a free SSL certificate for your domain:
- Go to Websites & Domains and select your domain
- Click SSL/TLS Certificates
- Click Install next to Let's Encrypt
- Enter your email and click Install
Plesk will obtain and install the certificate automatically. Renewal is also automatic.
Step 5 - Activate a License
Your VPS comes with a 14-day trial license that activates automatically. The trial is fully functional and supports up to 3 domains.
To continue using Plesk after the trial, you need to purchase and activate a license:
- Purchase a license key from plesk.com or an authorized reseller
- In Plesk panel, go to Tools & Settings → License Management
- Click Install Key and enter your license key
Plesk will activate the license immediately. No server restart is required.
What's Pre-Configured
- Web server: Nginx as reverse proxy + Apache for application processing
- Database: MariaDB, managed through Plesk panel
- Mail: Postfix (SMTP) + Dovecot (IMAP/POP3), ready for mailboxes
- DNS: BIND name server for hosting DNS zones
- Security: Fail2Ban protects SSH and panel from brute-force attacks
- IP remapping: Plesk automatically detects the correct IP after cloning
Post-Installation
Install Applications
Plesk includes a one-click installer for popular applications. Go to Applications in the panel to install WordPress, Joomla, Drupal and many others without using the command line.
Server Credentials
Plesk admin password is stored in /root/.plesk_credentials.
Updates
Plesk manages its own updates. To check for updates, go to Tools & Settings → Updates in the Plesk panel. OS updates can be applied via SSH:
apt update && apt upgrade -y
Troubleshooting
| Problem | Solution |
|---|---|
| Can't access Plesk panel | Make sure you use https:// and port 8443. Accept the self-signed certificate warning in your browser |
| Plesk panel loading slowly | Plesk initialization takes up to 2 minutes after first boot. Wait and refresh the page |
| Forgot Plesk admin password | SSH in and run: plesk bin admin --set-admin-password -passwd "newpass". Or check /root/.plesk_credentials |
| Trial license expired | Purchase a license from plesk.com and activate it in Tools & Settings → License Management |
| Domain not resolving | Check that your domain's A record points to the server IP. Use dnschecker.org to verify |
| Blocked by Fail2Ban | Use VNC console in your client panel to unban your IP: fail2ban-client set plesk-panel unbanip 1.2.3.4 |
| Can't connect via SSH | Check that port 22 is not blocked. Try VNC console as a fallback |