Plesk access

Open Plesk for your hosting service

The quickest route is the secure “Log in to Plesk” button beside your active hosting service in the UKC Client Area. It selects the correct server and normally signs you in without asking for a separate Plesk password.

Use Client Area loginIt identifies the hosting server and creates a secure Plesk session.

One service, one serverDifferent hosting plans can be assigned to different UKC servers.

Click once and waitRepeated clicks can create competing sessions or trigger protection.

Recommended route

Open Plesk from My Services

  1. Sign in to the UKC Client Area.
  2. Open Services, then My Services.
  3. Select the active hosting plan containing the website or mailbox.
  4. Choose Log in to Plesk once and wait while the secure session is created.
  5. Confirm the expected domain appears under Websites & Domains before changing anything.

Choose the correct service

Your account may use more than one Plesk server

The domain or service name shown in My Services helps identify the right plan. The server hostname normally follows the UKC naming pattern, such as ukc10.uk, ukc11.uk, ukc12.uk or ukc13.uk.

If the domain is missing after login, return to My Services and check the other active hosting plan rather than adding it to the wrong subscription.

Direct URL

Use the assigned server hostname when necessary

Plesk normally listens securely on port 8443. For example, a service assigned to UKC12 can use https://ukc12.uk:8443. Use only the hostname shown for your hosting service; a different UKC server will not contain your subscription.

The Client Area route remains preferable.

It avoids remembering a server URL and normally provides single sign-on.

Troubleshooting

If Plesk does not open

  • Wait for the first request: session creation can take several seconds.
  • Check the new tab: a browser may open Plesk separately or block the new window.
  • Retry in a private window: this can clear a stale Client Area or Plesk session.
  • Try another network: local filtering may block port 8443.
  • Pause after repeated failures: protection may temporarily limit the public IP address.

Account security

Use a trusted device and verify the hostname

Check that the browser address is the expected UKC server over HTTPS before entering credentials. Sign out when using a shared device. Never send a Client Area, Plesk or mailbox password in a support ticket.

Need help?

Tell us which service fails to open

Include the hosting service/domain, assigned UKC hostname, exact error, approximate time, browser/device and your current public IP address. Say whether the Client Area button and direct :8443 URL behave differently.

Still unable to reach Plesk?Open a ticket with those details and no passwords.

Open a support ticket

Was this answer helpful?

« Back