This article covers manual setup of a Let’s Encrypt certificate on Webhosting. If you want to use automatic setup, follow the guide Webhosting – Automatic HTTPS. If you want 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 – Configuring HTTPS on the website.
In this article you will learn:
- How to manually enable HTTPS on Webhosting
- How to set domains and subdomains in the certificate
- How to set 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 domains in the certificate
After activating the certificate, we recommend setting HTTPS on the website.
Activating SNI support
HTTPS on a domain (SNI) is a Webhosting extension that allows deployment of HTTPS certificates. We provide it free of charge, and most webhostings have it activated automatically and free of charge.
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 in these steps:
- Log in to the customer administration ⧉.
- In the top menu, select Hosting services Webhosting.
- Select your Webhosting in 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 the certificate domains and subdomains
Setting domains and subdomains in the certificate is a necessary step to make it work. If you do not make the settings or do not save them, 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 HTTPS setup to complete for the given domains or subdomains.
After enabling HTTPS with a Let’s Encrypt certificate according to the previous chapter, you will see the link certificate domain settings for the given item. If you have no domains set in the certificate, the link will also appear in a red warning.

This link takes 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 a alias of the Webhosting.
- Use the cross icon on the left side of a domain or subdomain row to delete it.
- Use checkboxes together with the Delete selected and Validate selected buttons to perform bulk edits.
- Use the Apply changes button to start certificate generation.

Adding domains to 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, 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.
With the checkboxes below the table, you can select or clear all corresponding options.

When you are done, click the Add domains button and, if finished, click Apply changes in the HTTPS administration. The certificate setup and propagation will take up to 90 minutes.
Continue with setting HTTPS on the website.
Adding subdomains to the certificate
Use 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 you want to add subdomains to.
- In the Subdomains field, enter a list of subdomain names separated by commas. Enter only subdomain names without the domain suffix (for example, shop, not shop.domain.tld).
- Click the Add domains button.

When you are done, click Apply changes in the HTTPS administration. The certificate setup and propagation will take up to 90 minutes.
Continue with setting HTTPS on the website.
Setting HTTPS 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 – Configuring HTTPS on the website.
Common problems
Common problems with HTTPS setup include:
- The domain does not point to the Webhosting
- The domain has no DNS records set
- Non-specific domain error in the certificate
- An error is displayed on the page
- The website is accessible over HTTP
- HTTPS does not work on the www subdomain
The domain does not point to the Webhosting
Problem: The message the domain is not pointed to this Webhosting is displayed.

Cause: The domain’s A and/or AAAA records do not point directly to Webhosting. Most often it points to another hosting, or uses a proxy such as CloudFlare or WEDOS Global.
Solution: Make sure the domain points to the webhosting where 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 foreign 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 named * does, and at the same time the subdomain has no other DNS records.
If this error appears because the domain is placed on WEDOS Protection ⧉, contact us via the form ⧉ with a request to add the domains and subdomains to the certificate on our side.
The domain has no DNS records set
Problem: The message the 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 is set up and that enough time has passed since registration for DNS servers to propagate (usually 6 – 48 hours). For older domains, make sure that the DNS records exist at the DNS provider and that a DNS server change is not in progress.
Non-specific certificate domain error
Problem: The overview of certificate domains shows Error – contact customer support.
Solution: If you cannot see any cause of the error (for example, the DNS problems mentioned above), check the DNS records and servers of the (sub)domain listed 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 ⧉. Provide 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. is displayed 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 over both HTTP and HTTPS and does not enforce a secure connection in any way.
Solution: Set HTTPS on the website according to the guide Webhosting – Configuring HTTPS on the website.
Non-working www subdomain
Problem: We have a certificate added on the subdomain, including the www version. The subdomain itself works, but the www version does not. The certificate is active for both.
Cause: This problem is common for domains using WEDOS.protection. The certificate for the fourth-level domain (such as www.sub.domain.tld) is located on the Webhosting, but not on the proxy server, so the connection is evaluated as unsecured.
Solution: Redirect the www subdomain to the fully secured non-www subdomain. If you use our default .htaccess file, add this code immediately below RewriteEngine On:
# 301 redirect www.sub.domain.tld -> sub.domain.tld
RewriteCond %{HTTP_HOST} ^www\.([^.]+\.[^.]+\.[^.]+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [R=301,L]
Frequently asked questions
I have the domain, DNS and webhosting with you, I did not change anything, but the certificate says the domain does not point to the webhosting. What is happening?
The most common cause is that the domain is routed through the protection service WEDOS Protection. Contact us via the form ⧉ regarding verification and fixing the problem with certificate generation.