This article deals with the manual setup of the Let’s Encrypt certificate on Webhosting. To use the quick setup, follow the Webhosting – HTTPS Quick Setup guide. To deploy your own certificate, follow the article Webhosting – Own SSL Certificate. To set up HTTPS on WebSite, use the article WebSite – HTTPS.

After setting up HTTPS in the administration panel, make sure to also configure it on your website according to the instructions Webhosting – Configure HTTPS on Web.

In this article, you will learn:

• How to manually turn on HTTPS on Webhosting
• How to set up domains and subdomains in the certificate
• How to configure HTTPS on the web
• Common issues
• Frequently asked questions

Manual activation of HTTPS with Let’s Encrypt certificate consists of:

1. Activating SNI support
2. Turning on HTTPS with Let’s Encrypt
3. Setting up domains in the certificate

After activating the certificate, configure HTTPS on your web.

HTTPS on Domain (SNI) is a Webhosting add-on enabling the deployment of HTTPS certificates. We provide it for free and most Webhostings have it activated automatically.

Check whether it is enabled according to the guide Webhosting – Add-ons.

SNI support alone is not enough to enable HTTPS. Continue by activating the Let’s Encrypt certificate according to this guide, or deploy your own certificate according to the article Webhosting – Own SSL Certificate.

To enable HTTPS with a Let’s Encrypt certificate, follow these steps:

1. Log into the customer administration panel. 
2. In the navigation bar, select Web & Email Hosting Webhosting.
3. Select the webhosting you want to set HTTPS on.
4. In the left menu, select HTTPS.
5. In the Select HTTPS Variant, select HTTPS with Let’s Encrypt Certificate.
6. Confirm by clicking the Make Changes button.

Continue by adding domains and subdomains to the certificate.

Setting domains and subdomains in the certificate is a necessary step to make it work. If you don’t enter or apply the settings, HTTPS won’t work on the site.

After applying changes in the certificate, wait up to 90 minutes (30 minutes for activation, 60 minutes for the changes to propagate) to complete the HTTPS settings for the domains or subdomains.

After enabling HTTPS with a Let’s Encrypt certificate according to the previous chapter, you will see a link to set the certificate domains. If you do not have any domains set in the certificate, the link will also be displayed in a red warning on top of the page.

This link will take you to an interface that allows you to:

• Use the Add Domains button to add domains and subdomains to the certificate that are either the name or the alias of the Webhosting.
• Use the x icon in the left part of the domain or subdomain table row to delete the entry.
• Edit items in bulk using check boxes in conjunction with the Delete selected and Validate Selected buttons.
• Use the Apply Changes button to start generating the certificate.

Use the Add Domains button to open the interface for adding domains and subdomains.

In the Webhosting Domains table, check the box:

• in the left part of the table to add the domain and any subdomains.
• in the Domain column to add just the domain.
• in the www Subdomain column to add the www subdomain.

Toggle the corresponding options using the check boxes below the table.

When you’re done, click the Add Domains button, and then Apply Changes in HTTPS Administration. Setting up the certificate and propagating the changes should take up to 90 minutes.

Continue to set up HTTPS on the website.

Use the Add Domains button to open the interface for adding domains and subdomains.

Next, follow these steps:

1. In the left part of the Webhosting Domains list, check the domain or domains to which you want to add subdomains.
2. In the Subdomains box, type a comma-separated list of subdomain names. Only enter subdomain names without the domain itself (e.g. eshop, not eshop.domain.tld).
3. Click the Add Domains button.

When you’re done, click Apply Changes in HTTPS Administration. Setting up and propagating the certificate will take place within 90 minutes.

Continue to set up HTTPS on the website.

If the website still uses the HTTP protocol after successfully setting up HTTPS in the customer administration panel, adjust its settings according to the instructions Webhosting – Configure HTTPS on Web.

Common issues with HTTPS setup include:

• Domain not directed to Webhosting
• Domain has no DNS records
• Unspecified domain error
• The site displays an error
• The website is still unsecured

Issue: An error message says Domain not directed to Webhosting.

Cause: The domain’s A or AAAA DNS records are not directed to the Webhosting. Most often they are directed to another hosting or use a proxy such as CloudFlare or WEDOS Global.

Solution: Make sure the domain is pointed to the web host where you enable HTTPS. If it uses our DNS servers (NSSET), you can direct it to the service according to this guide. If the domain uses third-party DNS servers, make sure you direct it to the web host correctly, for example using diagnostics.

If there is a problem with a subdomain, make sure that a record with the name of the subdomain or a record with the name * is directed to the Webhosting and the subdomain has no other DNS records.

If you are seeing this error because the domain is placed on WEDOS Global, contact us via the form and ask us to add domains and subdomains to the certificate.

Issue: An error message says domain has no DNS records.

Cause: The doomain’s DNS servers or records haven’t propagated yet, or they are deleted.

Solution: If you are adding a newly purchased domain, make sure that it has been set up and that enough time has passed since it was set up to for the DNS servers to propagate (usually up to 6 – 48 hours). For older domains, make sure that the domain has DNS records with the DNS server provider and that a recent DNS server change is not propagating.

Issue: A message says Error – contact customer support.

Solution: If you don’t see any cause for the error (such as the DNS issues above), try removing the domain from the certificate, adding it again, and applying the changes.

If the error persists, contact customer support via the form. Provide the Webhosting name and inform support that removing and re-adding the domain failed.

Question: I have the domain, DNS and web hosting with you, I have not changed anything, but the certificate suddenly says that the domain does not direct to Webhosting. What’s happening?
Answer: Contact us via the form to check and correct the issue with the certificate generation.