This article addresses the manual setup of a Let's Encrypt certificate on Webhosting. To use the automatic settings, follow the instructions in Webhosting - Automatic HTTPS. To deploy a custom certificate, follow the Webhosting - Deploying a Custom SSL Certificate article.
After setting it up in the administration, set up HTTPS on the website according to the Webhosting - Setting up HTTPS on the website instructions.
In this article you will learn:
- How to manually enable HTTPS on web hosting
- How to set up domains and subdomains in a certificate
- How to set up HTTPS on a website
- Common problems
- Frequently Asked Questions
Manual activation of HTTPS on web hosting
Manual activation of HTTPS with a Let's Encrypt certificate consists of:
- Activate SNI support
- Enabling HTTPS with a Let's Encrypt certificate
- Setting domains in a certificate
After activating the certificate, we recommend setting up HTTPS on the site.
Activate SNI support
HTTPS on Domain (SNI) is a web hosting extension that allows the deployment of HTTPS certificates. We provide it for free and most web hosts have it activated automatically and free of charge.
Check or switch on according to the instructions in Services - Additional services:
- An active add-on service has a magnifying glass icon to the left of its name for setting/deactivating it.
- An inactive supplementary service has a green + button to the left of its name to activate it.
SNI support alone is not enough to run a site over HTTPS. Continue by enabling Let's Encrypt certificate according to this guide, or deploy your own certificate according to the Webhosting - Deploying your own SSL certificate article.
Enabling HTTPS with a Let's Encrypt certificate
To enable HTTPS with a Let's Encrypt certificate, follow these steps:
- Log in to customer administration ⧉.
- In the top menu, select Hosting Services Webhosting.
- Select your web host in the list of services.
- Select HTTPS from the left menu.
- In the Select HTTPS option box, select HTTPS with Let's Encrypt certificate.
- Confirm your selection with the Make changes button.
Continue by adding domains and subdomains to the certificate.
Setting up certificate domains and subdomains
Setting up domains and subdomains in the certificate is a necessary step to make it operational. If you do not make or save the settings, HTTPS will not work on the site.
After each application of certificate changes, wait up to 90 minutes (30 minutes to activate, 60 minutes to propagate changes) to complete the HTTPS settings for the domain or subdomain.
When you enable HTTPS with Let's Encrypt as described in the previous section, you will see a certificate domain settings link next to the entry. If you do not have any domains set in the certificate, the link will also appear in red.
This link will take you to the interface that allows you to:
- Use the Add Domains button to add domains and subdomains to the certificate that are either the name or alias of the Web host.
- Delete a domain or subdomain by clicking the cross icon in the left row of the domain or subdomain table.
- Checkboxes in conjunction with the Delete Selected and Validate Selected buttons perform bulk editing.
- Click Apply Changes to start the certificate generation.
To add domains to a certificate
Click Add Domains to open the interface for adding domains and subdomains.
In the Web Host Domains table, select the check box:
- In the left side of the table, you want to add this domain and any subdomains.
- In the Domain column, if you want to add just the domain.
- In the www subdomain column, to add a www subdomain.
You can check or uncheck all the corresponding options below the table.
When you are finished, click Add Domains and, when you are finished, click Apply Changes in the HTTPS administration. The certificate will be set up and signed within 90 minutes.
Continue by setting up HTTPS on the site.
To add subdomains to a certificate
Click Add Domains to open the interface for adding domains and subdomains.
Then follow these steps:
- In the Web Hosting Domains list on the left, check the domain or domains to which you want to add subdomains.
- In the Subdomains box, type a comma-separated list of subdomain names. Only list subdomain names without a domain ending (e.g. eshop, not eshop.domena.tld).
- Click the Add Domains button.
When you are finished, click Apply Changes in the HTTPS administration. The certificate will be set up and signed within 90 minutes.
Continue by setting up HTTPS on the site.
Setting up HTTPS on the web
If the site is still using HTTP after successfully setting up HTTPS in the customer administration, adjust its settings according to the Webhosting - Setting up HTTPS on a website instructions.
Common problems
Common problems with HTTPS settings include:
- The domain does not point to a web host
- Domain does not have DNS records set
- Non-specific domain error in the certificate
- The page displays an error
- Web is accessible via HTTP
Domain does not point to web hosting
Problem: The message domain is not directed to this webhost.
Cause: A and/or AAAA domain records are not pointed directly to the Webhosting. Most often it is routed to another hosting, or uses a proxy such as CloudFlare or WEDOS Global.
Solution: Make sure the domain is directed to a web host where you activate HTTPS. If it uses our DNS servers (NSSET), you can point it to the service by following these instructions. If the domain is using foreign DNS servers, make sure you point it to the webhost correctly, for example by using diagnostics.
If the problem occurs with a subdomain, make sure that the web host is pointing to a record with the subdomain name, or a record with the name *, and the subdomain does not have any other DNS records.
If you are getting this error due to a domain being placed on the WEDOS Protection ⧉, please contact us via the ⧉ fomule to request that we add the domains and subdomains to the certificate from our side.
Domain does not have DNS records set
Problem: The message domain does not have DNS records set is displayed.
Cause: the domain has no DNS servers or records, or it is deleted or shut down.
Solution: If you are adding a newly purchased domain, make sure that it is established and that enough time has passed since its creation for the DNS servers to be propsed (usually 6 - 48 hours). For older domains, make sure that domain records exist with the DNS server provider and that DNS servers are not being changed.
Non-specific domain error in the certificate
Problem: Error is displayed in the certificate domain overview - contact customer support.
Solution: If you don't see any cause for the error (for example, the DNS issues mentioned above), check the DNS records and servers of the (sub)domain listed in the error message, and then try removing the domain from the certificate, re-adding it, and applying the changes.
If the error persists, please contact customer support via the &boxboxbox;. Provide the name of the web host and inform support that the removal and re-addition of the domain failed.
Not found on accelerator
Problem: The website displays a Not found on accelerator error .
Cause: HTTPS is not properly activated.
Solution: Make sure you have set up HTTPS correctly according to this guide and at least 90 minutes have passed since the setup.
Insecure site
Problem: HTTPS is up and running, but the site is also accessible via HTTP.
Cause: the web allows access via HTTP and HTTPS, it does not enforce secure connections.
Solution: Set up HTTPS on the site by following the instructions in Webhosting - Setting up HTTPS on the site.
Frequently Asked Questions
I have the domain, DNS and webhosting with you, I haven't changed anything, but the certificate says that the domain is not directed to the webhosting. What's wrong?
The most common cause is running the domain through WEDOS Protection. Contact us via fomular⧉ to verify and correct the certificate generation issue.