How to Access Plesk on Windows Server: Login, Ports, and First-Time Setup

Overview

Plesk is a web hosting control panel that runs on both Linux and Windows Server. On a Windows Server VPS or dedicated machine, the Plesk Windows login process is slightly different from what you might expect — particularly around ports and how the admin credentials are initially set. This article covers how to get into Plesk for the first time, what to do if the login page won’t load, and how to recover access if you’re locked out.

Most users land here because they’ve just provisioned a new Windows VPS and can’t figure out where the Plesk interface actually lives, or because their browser is throwing a connection error. Both situations are common and fixable.

If you’re running Plesk Obsidian (18.x) or Plesk Onyx (17.x) on Windows Server 2019 or 2022, this guide applies to you. Some menu labels differ slightly between versions, but the core access method hasn’t changed.

Prerequisites

• A Windows Server VPS or dedicated server with Plesk already installed (Plesk Obsidian 18.x recommended)
• The server’s public IP address — available in your Host & Tech client portal
• Administrator or root-level credentials for the server (RDP access is helpful but not required for basic Plesk login)
• Port 8443 (HTTPS) or 8880 (HTTP) open in Windows Firewall and any upstream firewall or security group rules
• A modern browser — Chrome, Firefox, or Edge. Internet Explorer will not work correctly with Plesk’s UI

Step-by-Step: Accessing Plesk on Windows Server

Step 1: Open the Plesk Login URL

Plesk on Windows Server listens on port 8443 for HTTPS by default. Open your browser and go to:

https://YOUR_SERVER_IP:8443

Replace YOUR_SERVER_IP with the public IP of your server. For example: https://198.51.100.42:8443

You’ll almost certainly see a browser SSL warning on a fresh install because Plesk uses a self-signed certificate until you assign a proper domain and generate a Let’s Encrypt cert. This is normal. Click Advanced and then Proceed (Chrome) or Accept the Risk and Continue (Firefox) to get to the login page.

📝 Note: If you’ve already pointed a domain to this server and configured Plesk to use that hostname, you can also access Plesk via https://yourdomain.com:8443. This avoids the SSL warning entirely once a valid certificate is in place.

Step 2: Log In as Administrator

On the Plesk login screen, enter your credentials:

• Username: admin
• Password: This is set during Plesk installation. On a Host & Tech VPS, it’s typically included in your welcome email or available in the client portal under your server’s details.

Click Log In. On first login, Plesk may prompt you to complete the initial setup wizard — choose your view (Service Provider or Power User), set your contact email, and install a licence key if one hasn’t been applied automatically.

📝 Note: The Power User view is better for managing a single server or a small number of sites. Service Provider view is for resellers or hosting businesses managing multiple customers. You can switch views later under Tools & Settings > Switch to Service Provider View.

Step 3: Retrieve or Reset the Admin Password via RDP

If you don’t have the admin password, connect to the server via RDP, open a Command Prompt or PowerShell as Administrator, and run:

cd "C:Program Files (x86)Pleskadminbin"
plesk.exe --show-login-link

This outputs a one-time login URL you can paste directly into your browser. It bypasses the password entirely and drops you into an active Plesk session. Use it immediately — the link expires after a few minutes.

To set a new admin password outright, run:

plesk.exe bin admin --set-admin-password -passwd "YourNewPassword123!"

⚠ Warning: Use a strong password here. Plesk’s admin account has full control over every domain, database, and email account on the server. A weak password on a public-facing server is a real risk.

Step 4: Confirm Firewall Rules Allow Port 8443

If the login page won’t load at all, the most likely cause is a blocked port. Check Windows Firewall first via PowerShell:

netsh advfirewall firewall show rule name="Plesk" verbose

If no rules come back, add them manually:

netsh advfirewall firewall add rule name="Plesk HTTPS" protocol=TCP dir=in localport=8443 action=allow
netsh advfirewall firewall add rule name="Plesk HTTP" protocol=TCP dir=in localport=8880 action=allow

Also check whether your Host & Tech VPS has a cloud firewall or security group applied at the network level — these rules sit above the OS and won’t show up in Windows Firewall at all. Log into the client portal and verify that port 8443 is permitted inbound. Our VPS SSD Hosting plans include firewall management through the portal.

Step 5: Access Plesk from the Server Itself (Local Access)

If you’re already RDP’d into the server and just want to open Plesk locally, you can use localhost:

https://localhost:8443

This is useful for initial configuration when the server IP isn’t yet resolving correctly or when you’re troubleshooting a certificate issue without exposing the problem externally.

Common Issues & Troubleshooting

This site can’t be reached / Connection Refused on Port 8443

This almost always means either the Plesk service isn’t running, or the port is blocked. Connect via RDP and check the Plesk service status:

sc query plesksrv

If the state isn’t RUNNING, start it:

net start plesksrv

If the service starts but you still can’t connect externally, go back to Step 4 and verify both the Windows Firewall rules and any upstream cloud firewall in your hosting portal.

Invalid Login or Incorrect Password

The admin password set during Plesk installation is separate from your Windows Administrator password. They’re not linked. People mix these up constantly. Use the --show-login-link method from Step 3 to get in without needing the password, then reset it once you’re inside under Tools & Settings > Change Password.

Plesk Login Page Loads but Redirects to a Blank Page or Loops

This is usually a session or cookie issue. Clear your browser cache and cookies for the site, then try again. If that doesn’t fix it, try an incognito/private window. In my experience, this also happens when the system clock on the server is out of sync — Plesk’s session tokens are time-sensitive. Check server time:

w32tm /query /status

If the clock is drifting, sync it:

w32tm /resync /force

SSL Certificate Warning Won’t Let Me Proceed

Some corporate browsers or strict security policies block self-signed certificates entirely and don’t show the “proceed anyway” option. The proper fix is to assign a real hostname to your server and generate a Let’s Encrypt certificate in Plesk under Tools & Settings > SSL/TLS Certificates. As a temporary workaround on a managed machine, you can use HTTP on port 8880 — though I wouldn’t do this long-term on a production server.

“Plesk licence key has expired” or Licence Error on Login

Plesk will lock you out of most functions if the licence expires, but you can still log in to the interface. Go to Tools & Settings > Licence Management and either retrieve an updated key or enter a new one. If your server was provisioned through Host & Tech with a Plesk licence included, contact support — the key renewal is usually handled on our end and may just need a manual trigger.

FAQ