How to Enable an SSL Certificate with the Plesk panel

To enable an SSL certificate through the Plesk panel, first verify that the domain points to the correct server and that your account is allowed to manage certificates. Then create or upload the certificate from the domain’s SSL/TLS section, enable HTTPS in the site settings, and test the same address again. If certificate validation fails, target the finding in the DNS or validation record instead of changing every setting.

What access and conditions are required before starting?

This process can be performed on a shared hosting account with Plesk installed when you have domain or subscription administrator access. On a managed VDS or server, you may also need access to the relevant subscription and, where necessary, to the SSL features configured by the server administrator. If you do not have a server or manage Plesk yourself, you may review the Turkey VDS server plans page only to examine suitable hosting environments; the link does not guarantee an SSL feature or management service.

Before starting, check that the domain’s A record points to the correct server. If IPv6 is in use, inspect the AAAA record as well; an old IPv6 address may send some visitors to a different server. During a certificate request, the domain generally needs to be reachable for validation over HTTP. A CDN, firewall, or provider-specific DNS setting may affect this validation.

Make a note of the current certificate selection, HTTPS redirect status, and DNS values. If possible, create a current backup of the site files and configuration. Changing only one factor at a time makes it easier to understand which action produced the result.

Enabling an SSL certificate through the Plesk panel

1. Select the domain: In Plesk, open Websites & Domains and enter the management screen for the relevant domain. If there is more than one subscription, confirm that you selected the correct domain and that the change will not be applied to another site.
2. Open the SSL/TLS screen: In the SSL/TLS certificates section for the domain, find the option to create a new certificate or the automatic certificate option offered by the provider. The menu name and available certificate providers may vary according to the Plesk version, licence, and hosting company permissions.
3. Verify the domain names: Add the main domain to the certificate. If you also use the www subdomain, include it only if its DNS record points to the same server and the site responds under that name. If a separate name is used for email, determine whether the certificate will be used by the mail service according to the provider’s configuration.
4. Submit the request and read the result: Start the creation or upload process. A successful result should show the certificate status, validity information, or the selected active certificate. If you receive a validation error, inspect the domain name and method identified in the error message instead of submitting the request repeatedly.
5. Enable HTTPS: If the certificate appears to be active, confirm that SSL support is enabled in the domain settings and, if available, enable the permanent HTTP-to-HTTPS redirect in a controlled manner. Test the main site first, followed by the subdomains you use; do not apply the redirect to all domain names without considering them individually.

Fixing a validation error according to the finding

If the error occurs only during the certificate request, check the validation message in Plesk’s certificate screen and the current records in DNS management. If the domain points to the old server, direct the A record to the correct target and wait for the DNS change to propagate. If the A record is correct but errors occur on connections using IPv6, check whether the AAAA record points to the current server. If the old record is no longer used, decide whether to remove it only after confirming your DNS and IPv6 plan; do not delete DNS records at random.

Suppose Plesk validation fails for your example domain, the A record points to the server, but the AAAA record still contains the address of the previous server. In this situation, the certificate provider may send some requests to the old server. The appropriate action is first to correct the AAAA record to the correct address, consider deliberately removing it if IPv6 is not being used, and then retry only the certificate request. If the new error indicates that the HTTP validation file cannot be reached or that a port is blocked, inspect the firewall, CDN cache, or provider restriction instead of changing DNS again.

A validation failure and a site failing to redirect after HTTPS has been enabled are not the same problem. If the certificate is created successfully but the page remains on HTTP, check the redirect selection in the domain’s hosting settings and the application’s own base URL setting separately. Enabling all redirects at once can hide which layer is responsible when a loop occurs.

How do you verify the change and safely roll it back?

After the certificate process succeeds, revisit the same failed operation: the same domain and URL that did not open previously. In the browser’s certificate details, confirm that the domain is covered, that a validity date is shown, and that there is no certificate warning. Also check in Plesk’s certificate screen that the new active certificate is selected. This time, note the operation time and inspect new lines in the access or error log for the domain; do not treat the old error record as evidence of the new result.

If the site opens over HTTPS but a particular subdomain does not, check whether that name was added to the certificate and whether its DNS record points to the same server. If the certificate is correct but a redirect loop occurs, first disable the HTTPS redirect you just enabled and return to the previous value you recorded. Then inspect the application’s URL setting or proxy configuration by itself. If you need to undo the certificate selection, select the previous certificate you noted before the operation; disabling security checks or changing file permissions in bulk is not a safe correction.

As the next step, first compare the domain’s certificate status and DNS records in Plesk at the same time. If the two layers are consistent, only then enable the HTTPS redirect again and test the main URL and the problematic subdomain separately.