A browser shows a secure connection when the domain loads over HTTPS with a valid certificate matching that hostname. Installing hosting alone is not enough. The domain must first resolve to the server that will answer the certificate request.
1. Confirm the domain is active
An expired, pending or suspended domain may not resolve consistently. Check the domain status and expiry date in My Domains before troubleshooting the certificate.
2. Check where DNS points
The root domain and any required www hostname must resolve to the intended hosting service. If they point to an old server, parking account or external platform, the Ecowebzim server cannot prove control of those names.
3. Allow propagation to finish
After changing nameservers or DNS records, different networks can temporarily return different answers. Certificate issuance should be retried only after the public records consistently reach the correct server.
4. Check the hosting account
The domain must exist on the correct DirectAdmin account as a primary, pointer or hosted domain. A parked copy under another account can conflict with normal provisioning and certificate issuance.
5. Let AutoSSL run
Ecowebzim uses Let's Encrypt for normal free certificate issuance, with ZeroSSL available as a secondary option. Certificates are normally installed and renewed automatically for eligible hosted domains.
When can support reissue the certificate?
A reissue is appropriate when the domain is active, resolves to the Ecowebzim server, exists on the correct hosting account and has no unresolved provisioning problem. Repeated issuance attempts before those conditions are met will not fix incorrect DNS.
Useful information for a support request
- The complete domain name
- The affected hostname, such as www or mail
- When DNS was last changed
- The browser error or certificate message
- The related hosting service, if known
Customers can use the SSL indicator in My Domains and ask the Ecowebzim Assistant to run the available domain-health checks before opening a ticket.
