This article covers the manual setup of a Let’s Encrypt certificate on Webhosting. To use automatic setup, follow the guide Webhosting – Automatic HTTPS. To deploy your own certificate, follow the article Webhosting – Deployment of your own SSL certificate.
After setting it up in the administration, also configure HTTPS on the website according to the guide Webhosting – Website HTTPS Setup.
In this article you will learn:
- How to manually enable HTTPS on Webhosting
- How to set domains and subdomains in the certificate
- How to configure HTTPS on the website
- Common problems
- Frequently asked questions
Manual HTTPS activation on Webhosting
Manual HTTPS activation with a Let’s Encrypt certificate consists of:
- Activating SNI support
- Enabling HTTPS with a Let’s Encrypt certificate
- Setting up domains in the certificate
After activating the certificate, we recommend setting up HTTPS on the website.
Activating SNI support
HTTPS on a domain (SNI) is a Webhosting extension that enables deployment of HTTPS certificates. We provide it free of charge, and most web hosting services have it activated automatically and for free.
Check or enable it according to the guide Services – Add-on services:
- An active add-on service has a magnifying glass icon to the left of its name for settings/deactivation.
- An inactive add-on service has a green + button to the left of its name for activation.
SNI support alone is not enough to run a website over HTTPS. Continue by enabling the Let’s Encrypt certificate according to this guide, or deploy your own certificate according to the article Webhosting – Deployment of your own SSL certificate.
Enabling HTTPS with a Let’s Encrypt certificate
Enable HTTPS with a Let’s Encrypt certificate using these steps:
- Log in to the customer administration ⧉.
- In the top menu, select Hosting services Webhosting.
- Select your webhosting from the services list.
- In the left menu, select HTTPS.
- In the box HTTPS variant selection choose HTTPS with a Let’s Encrypt certificate.
- Confirm the selection with the Apply changes button.
Continue by adding domains and subdomains to the certificate.
Setting domains and subdomains in the certificate
Setting domains and subdomains in the certificate is a necessary step to make it work. If you do not perform or save the settings, HTTPS will not work on the website.
After each application of changes in the certificate, wait up to 90 minutes (30 minutes for activation, 60 minutes for propagation of changes) for the HTTPS setup for the given domains or subdomains to complete.
After enabling HTTPS with a Let’s Encrypt certificate according to the previous chapter, you will see a certificate domain settings link for the given item. If you have no domains set in the certificate, the link will also be shown in a red warning.
This link opens an interface that allows you to:
- Use the Add domains button to add domains and subdomains to the certificate that are either a name or a alias of the Webhosting.
- Use the cross icon on the left side of the table row to delete domains or subdomains.
- Use the checkboxes together with the Delete selected and Validate selected buttons to make bulk changes.
- Use the Apply changes button to start certificate generation.
Adding domains to the certificate
Click 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, if you want to add this domain and any subdomains.
- In the domain column, if you want to add only the domain.
- In the www subdomain column, if you want to add the www subdomain.
Using the checkboxes below the table, you can select or clear all corresponding options.
When finished, click the Add domains button and, if you are done, in the HTTPS administration click Apply changes. The certificate setup and propagation will take up to 90 minutes.
Continue with setting up HTTPS on the website.
Adding subdomains to the certificate
Click the Add domains button to open the interface for adding domains and subdomains.
Then follow these steps:
- In the left part of the Webhosting domains list, check the domain or domains to which you want to add subdomains.
- Into the Subdomains field, enter a list of subdomain names separated by commas. Enter only the subdomain names without the domain suffix (for example, eshop, not eshop.domain.tld).
- Click the Add domains button.
When you are done, in the HTTPS administration click Apply changes. The certificate setup and propagation will take up to 90 minutes.
Continue with setting up HTTPS on the website.
HTTPS setup on the website
If the website still uses HTTP after successfully setting up HTTPS in the customer administration, adjust its settings according to the guide Webhosting – Website HTTPS Setup.
Common problems
Common problems with HTTPS setup include:
- The domain does not point to Webhosting
- The domain has no DNS records set
- Non-specific domain error in the certificate
- An error appears on the page
- The website is accessible over HTTP
The domain does not point to Webhosting
Problem: The message domain is not pointed to this web hosting is displayed.
Cause: The domain’s A and/or AAAA records are not pointed directly to Webhosting. Most often it points to another hosting, or it uses a proxy such as CloudFlare, or WEDOS Global.
Solution: Make sure the domain is pointed to the webhosting on which you are activating HTTPS. If it uses our DNS servers (NSSET), you can point it to the service according to this guide. If the domain uses external DNS servers, make sure you have pointed it to the webhosting correctly, for example using diagnostics.
If the problem occurs with a subdomain, make sure the record with the subdomain name points to the webhosting, or the record with the name *, and that the subdomain does not have other DNS records at the same time.
If this error appears because the domain is placed on WEDOS Protection ⧉, contact us via the form ⧉ with a request for us to add the domains and subdomains to the certificate on our side.
The domain has no DNS records set
Problem: The message domain has no DNS records set is displayed.
Cause: The domain’s DNS servers or records have not propagated, or the domain has been deleted or suspended.
Solution: If you are adding a newly purchased domain, make sure it has been created and that enough time has passed for DNS server propagation since registration (typically 6 – 48 hours). For older domains, make sure the domain records exist with the DNS provider and that a DNS server change is not in progress.
Non-specific domain error in the certificate
Problem: In the certificate domain overview, Error – contact customer support is displayed.
Solution: If you do not see any cause of the error (for example the DNS problems mentioned above), check the DNS records and servers of the (sub)domain mentioned in the error message, then try removing the domain from the certificate, adding it again, and applying the changes.
If the error persists, contact customer support via the form ⧉. Include the webhosting name and inform support that removing and re-adding the domain failed.
Not found on accelerator
Problem: The error Not found on accelerator. appears on the website.
Cause: HTTPS is not activated correctly.
Solution: Check that HTTPS is set up correctly according to this guide and that at least 90 minutes have passed since the setup.
Unsecured website
Problem: HTTPS is set and working, but the website is also accessible over HTTP.
Cause: The website allows access via both HTTP and HTTPS and does not enforce a secure connection.
Solution: Set up HTTPS on the website according to the guide Webhosting – Website HTTPS Setup.
Frequently asked questions
I have the domain, DNS, and web hosting with you, I changed nothing, but the certificate says the domain does not point to the web hosting. What is happening?
The most common cause is the domain being operated through the protection WEDOS Protection. Contact us via the form ⧉ to verify and fix the certificate generation issue.