In this article9 sections
Adding a website in Plesk looks simple: enter a domain, upload some files, and turn on HTTPS. The steps go wrong in a predictable order, though. The DNS record points at the wrong server, the certificate is requested before the domain resolves, or the site is reachable on HTTP but the redirect to HTTPS is missing. This guide walks through creating a website in Plesk on Windows hosting, pointing the domain at it, installing a free SSL certificate, and checking that the site serves HTTPS correctly. Work through the steps in order, and the certificate step will succeed the first time.
SiteHarbour’s Windows hosting plans include Plesk and a free SSL certificate for every site. The certificate step below uses the free option in Plesk, and the same order applies to any Plesk server.
Before you start
- A domain you control, and access to its DNS records at the registrar or in the DNS zone.
- Your Plesk login with permission to add websites.
- The hosting server’s IP address, shown in Plesk under the server details.
Step 1: Add the website
In Plesk, open Websites & Domains and select Add Domain. Enter the domain name, such as example.com, and choose the hosting type. Set the subscription to the one that matches your plan. Select OK.
Expected: the domain appears in the list under Websites & Domains, with a folder named httpdocs where your files go. Plesk creates the DNS zone for the domain automatically if the server hosts DNS for it.
Step 2: Point the domain at the server
If the domain’s DNS is managed elsewhere, add an A record that points the domain to the hosting IP address. Add a matching record for www if you use it:
example.com. A 203.0.113.10
www.example.com. A 203.0.113.10Replace the address with the one shown in Plesk. Check that the change has spread before you request a certificate:
nslookup example.comExpected: the answer shows the hosting address. If it still shows the old address, wait and check again. Requesting a certificate before the domain resolves to this server is the most common cause of a failed certificate request.
Step 3: Install the free SSL certificate
In Plesk, open the website and select SSL/TLS Certificates. Choose the option to install a free certificate for the domain, and include the www name if you use it. Select the option to secure the domain, and wait for the request to finish.
Expected: a message that the certificate was issued and installed, with an expiry date about three months ahead. The certificates renew automatically, so the date should not need attention.
If the request fails, read the reason Plesk shows. The usual causes are a DNS record that does not yet point here, a port 80 block at a firewall, or a domain name that is misspelled in the request.
Step 4: Turn on the redirect from HTTP to HTTPS
Installing a certificate does not stop visitors from using the plain HTTP address. In Plesk’s hosting settings for the domain, enable the option to permanently redirect HTTP to HTTPS. Select the option and save. Plesk writes the redirect for the site.
Expected: a request to the HTTP address ends at the HTTPS address. Check it from a terminal:
curl -sI http://example.com | head -n 3Expected: a 301 status and a location line that starts with https://.
Step 5: Upload the site files
Upload the site to the httpdocs folder with SFTP or Plesk’s File Manager. For a static site or a simple page, upload an index.html file to test. Open the HTTPS address and confirm the page loads with the padlock showing.
Step 6: Check the certificate and the mixed content
Open the site in a browser and check the certificate details. It should name your domain and the issuer. Then look for mixed content, which is a page that loads an image, script or stylesheet over plain HTTP. Browsers block those, and the padlock may show a warning. Change each address to HTTPS, or to a relative address, and reload.
In a site that is already built, search the files for http:// and update the links you own. Leave links to other sites that do not offer HTTPS alone, and check that they still work.
Common mistakes
- Requesting the certificate before DNS is ready. Check the address first.
- Forgetting the
wwwname. Visitors who type it get a certificate error if the certificate does not cover it. - No HTTP redirect. Both the HTTP and HTTPS versions of the site are then indexed, which splits your search traffic.
- Mixed content left in place. A single HTTP image can turn the padlock into a warning.
Frequently asked questions
How long does the certificate take to issue?
Usually a few minutes once the DNS points to the server. Allow more time when DNS is still spreading.
Do I need to renew the certificate myself?
No, the free certificate renews automatically while the domain still points to the server. If you move the domain elsewhere, the renewal stops.
Can I use a paid certificate instead?
Yes, for businesses that need a validated organization name shown to visitors. The free certificate gives the same encryption for most sites.
Why does the site show a certificate for another domain?
The domain is served by a different website in Plesk, or a cached certificate is still in use. Check the website that the domain points to, and clear the browser cache.
A new Plesk website takes four steps that must happen in order: add the domain, point the DNS at the server, install the certificate, then redirect HTTP to HTTPS. Check each one before you move on, and the certificate will issue cleanly. For the Windows side of the site, read how to redirect HTTP to HTTPS on IIS next.