How to Install an SSL Certificate with the Plesk panel

To install an SSL certificate through the Plesk panel, first verify that the domain’s DNS records point to the server, then request a suitable certificate or select an existing one from the SSL/TLS Certificates screen. After certificate validation succeeds, assign it to the domain in the hosting settings; reopen the HTTPS address to confirm that the certificate is being served for the correct domain.

What access is required before starting the Plesk panel SSL certificate setup?

This process depends on access to subscription or domain management in Plesk. If you use shared hosting, you may see only the domain and SSL/TLS screens made available to you; the certificate extension, automatic renewal, or DNS management may be restricted by the provider. On a server managed by an administrator, the Plesk administrator or server administrator may be able to change additional settings.

Before starting, check which IP address the domain and, if necessary, the www subdomain point to. If the DNS change was made recently, different networks may still show old records. Note the existing certificate’s name, expiration date, and the domain to which it is assigned. This allows you to restore the previous assignment first if a change produces an unexpected result. Do not change DNS, certificate, and redirect settings at the same time.

Requesting a certificate through the Plesk panel

Select the domain and validation scope

1. Open Websites & Domains or the equivalent domain management screen in your language. Select the domain to be configured and enter the SSL/TLS Certificates section. If this screen is not visible, certificate management is not enabled for your subscription; instead of randomly changing server settings, use the method provided by your hosting provider.
2. Review the existing certificates. If a certificate has not expired and covers the domain, check whether it is already assigned instead of requesting a new one. If a new certificate is required, select the certificate provider included in the Plesk installation or the enabled automatic certificate extension. The provider name and validation options vary between installations.
3. Add the main domain, its www form if it is used, and any other subdomains that are actually in use to the certificate scope. If an email address is requested, enter an address you can access. Confirm the certificate request and follow the validation result in the status, notification, or error area of the same screen.

If the certificate request does not complete, note the error message and when it occurred. A common cause of domain validation failure is that the DNS record does not point to the Plesk server, or that the domain points to a different IPv6 record. If the record appears correct but validation still fails, investigate the firewall, whether the HTTP validation request is being blocked, and whether the domain is being routed through another redirection service.

Distinguish the error type based on the evidence

For example, suppose you requested a certificate for exampledomain.com and the Plesk panel error area says that the validation address could not be reached. If you find in DNS management that the domain points to the old server IP, the targeted correction is to direct the DNS record to the correct server and wait for propagation; repeatedly changing certificate settings is not the solution. If DNS is correct but only www.exampledomain.com fails, check that subdomain’s separate record. If the main domain succeeds, the problem may not be with the certificate service but with a missing subdomain record.

Assigning the certificate to the domain and verifying HTTPS

1. When the certificate has been created successfully, return to the domain’s hosting or SSL/TLS settings. Select the newly created certificate from the certificate list and save it. Before enabling HTTPS redirection at this stage, it is safer to verify that the regular HTTPS connection works; otherwise, a failed certificate assignment could direct all HTTP requests to an incorrect address.
2. In the browser, reopen the same URL that previously failed, such as https://exampledomain.com. In the certificate details, check that the supplied domain matches the address, that the certificate is valid, and that the browser does not show a trust-chain error. Then note when the certificate assignment was saved in the Plesk panel and reload the same URL to confirm that the new state, matching the time of the change, displays the correct certificate.
3. After HTTPS works, enable permanent redirection from HTTP to HTTPS if necessary. Also test absolute HTTP links within the site and the administration screens. If the page opens over HTTPS but some resources are still loaded over HTTP, the certificate installation may be complete; this new issue is generally related to link addresses in the theme, application, or content.

If the same certificate or domain error persists after the change, restore the previous certificate assignment and disable mandatory HTTPS redirection. This prevents visitors from being forced onto a non-working TLS connection. The next step is to share the time of the new error and the validation notification in the Plesk panel with the provider’s support channel; do not send private keys, passwords, or access tokens. If the problem is DNS-related, requesting the certificate again before DNS propagation is complete may not change the result.

When should you consider a different server option?

Certificate installation by itself does not indicate a need for more CPU or memory. However, if you manage many sites, applications, and automated tasks at the same time in Plesk, administrator access and resource planning may become separate requirements. First determine which settings are restricted in the hosting account; the SSL extension’s absence alone does not mean that a more powerful server is required. If you are researching server options, you may review the Turkey VDS server plans page only to examine the available options; suitability, the Plesk license, and management responsibilities must be verified separately.

The first safe next step is to note your domain’s DNS target and the current certificate assignment in the Plesk panel, then retry only the certificate validation. After a successful result, check the HTTPS address and every domain covered by the certificate one by one.