Your site opens, but the browser shows "Not Secure" or a broken padlock. In most cases the cause is one of the following.
1. The certificate has not been issued yet (the usual culprit)
Once your domain points to SiteBoma, the server needs 5 to 10 minutes to notice it and request a free Let's Encrypt certificate. Give it 15 minutes, then refresh. If the warning remains, request it again in DirectAdmin: open SSL Certificates, choose "Free & automatic certificate from Let's Encrypt" and save.
2. The address starts with http:// instead of https://
Enter the address with https:// at the front, or redirect visitors automatically (see step 5).
3. Mixed content: some files still load over HTTP
If your pages pull in images, scripts or stylesheets from plain http:// addresses, the padlock gets a yellow warning. Change those links to https://, or to the protocol-relative form //example.com/. On WordPress, the free "Really Simple SSL" plugin can fix this for you.
4. Check the certificate with our tool
Our free SSL checker shows who issued your certificate and when it expires. A generic self-signed certificate, or one labelled "DEFAULT", means the Let's Encrypt certificate has not been issued yet.
5. Redirect everything to HTTPS
Turn on "Force SSL with HTTPS redirect" under DirectAdmin → SSL Certificates, or put these lines in your .htaccess file:
RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]Still not fixed?
Send us a support ticket that includes the domain name. On weekdays our team will look into it within an hour.