Eligible hosted domains can use automated Let’s Encrypt certificates after DNS points to the server.
Applies to: Reseller DNS, SSL and email
Each customer account needs correct DNS, SSL and email configuration. The reseller controls customer-facing setup, but Tudor Internet controls the underlying shared platform and network.
Before you start
- Sign in with the reseller account rather than a customer SiteWorx login.
- Identify the affected SiteWorx account, package and domain.
- Record the current package, DNS and account settings before making a production change.
- Allow for DNS caching and avoid making unrelated DNS changes during the same maintenance window.
Step-by-step
- Create the SiteWorx account and domain.
- Point DNS to the hosting server.
- Enable or request Let’s Encrypt in SiteWorx.
- Force HTTPS only after the certificate is valid.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| Certificate issuance fails. | The domain does not resolve to the hosting server, an incorrect AAAA record exists, or validation requests are redirected or blocked. | Confirm public A and AAAA answers, allow HTTP validation to reach the account and retry only after DNS is correct to avoid rate limits. |
| The browser still shows an old or invalid certificate. | A proxy, CDN, alternate hostname or cached connection is presenting a different certificate. | Check the certificate actually served for each hostname and test both IPv4 and IPv6 paths before reinstalling anything. |
Important notes
- Make production changes in a planned window, keep the old configuration recorded and avoid changing several dependent services at the same time.
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The reseller service and affected SiteWorx account
- The package name and current resource use
- The exact action attempted and error returned
- Whether the issue affects one or multiple customer accounts
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Troubleshoot SSL for a reseller customer domain
- DNS and nameservers for reseller customers
- Use included SiteLock Lite and 360 Monitoring Lite on reseller hosting
- Plan private nameservers for reseller customers
Last reviewed: 2026-07-18.
