Use the supported Plesk upload path for your certificate files, then confirm that the website is serving the new certificate. Plesk Obsidian commonly provides SSL It!, while manual certificate repository controls remain available through Advanced Settings.
01 Choose the appropriate upload path
- Download the issued certificate and current intermediate chain. Confirm where the matching private key was generated and whether it is already in this domain's Plesk repository.
- Open Websites & Domains > your domain > SSL/TLS Certificates.
- For a supported prepared PEM upload through SSL It!, select Upload and supply the required file. Protect any file that includes the private key.
- For separate files or an existing CSR entry, open Advanced Settings, select the corresponding certificate entry, and upload the certificate and CA certificate into their labelled fields. Supply a matching private key only when it is not already retained there.
- For the manual repository workflow, select the certificate in the domain's Hosting Settings and save. Confirm SSL/TLS support is enabled.
- Visit the public HTTPS site and inspect its actual certificate. Test the required hostname aliases and check the complete chain.
Common questions
Why does Plesk show my certificate but the browser shows another?
Check assignment to the domain, the responding IP and any proxy in front of the server. A repository entry is not proof of the certificate on every endpoint.
Does this also protect webmail and mail clients?
Those services need appropriate name coverage and assignment. Check their separate certificate settings and the server's supported mail configuration.
Should I enable HSTS immediately?
First verify all required HTTPS names, renewals and redirects. HSTS can make an unresolved certificate problem prevent browser access.