If your site broke right after enabling SSL, it's almost always one of three things: the certificate hasn't finished issuing yet, your site is loading some resources over plain http:// (mixed content), or a redirect rule is looping. Work through the checks below in order.
Check the certificate actually issued
We issue free Let's Encrypt SSL automatically, but it can only happen after your domain's DNS is pointed at us. If you added the domain or just changed nameservers, the certificate typically issues within about 5 minutes of DNS resolving correctly. Until then, visitors will see a "not secure" warning or a certificate error, not a broken page.
To confirm the cert is live, check the domain's status: on the Meridian cPanel theme, the Dashboard shows a "No Certificate" card with a "Fix SSL Issue" action when something's wrong; in classic cPanel, open SSL/TLS Certificates and check the domain's status there. If DNS was only just updated, allow more time for propagation. If you're unsure whether your domain is even pointed at us yet, that's a separate problem from SSL itself.
Look for mixed content
This is a common cause of a site that "half loads" after SSL goes on: the page itself loads over https://, but it references images, scripts, or stylesheets hard-coded to http://. Browsers block or flag that mixed content, so you get a broken layout, missing images, or a console full of errors even though the padlock shows.
Open your browser's developer tools (F12), go to the Console tab, and reload the page. Mixed content warnings will name the exact insecure URL. Common causes:
- On most WordPress sites, the
siteurlandhomeoptions are still set tohttp://. Fix this in Settings → General in wp-admin, or via phpMyAdmin if you're locked out of the dashboard. - Hard-coded
http://links in theme files, a page builder's saved content, or a database full of old absolute URLs. - Third-party embeds (fonts, widgets, ad scripts) that were never updated to protocol-relative or HTTPS URLs.
For WordPress specifically, a search-and-replace across the database (swapping http://yourdomain.com for https://yourdomain.com) is a common fix once you've confirmed that's the actual problem.
Check for a redirect loop
If the browser shows "too many redirects" instead of a broken layout, you likely have two things both trying to force HTTPS at once, for example a .htaccess rule forcing https:// plus a plugin or app setting doing the same thing, and they're fighting each other or redirecting to the wrong form of the URL. Check your site's .htaccess in File Manager for any RewriteCond %{HTTPS} block, and check whether your CMS has its own "force SSL" setting turned on at the same time. Only one should be doing the redirect.
If you're using our Cloudflare CDN goodie on this domain, the SSL/TLS mode there matters too. If your origin server is already serving valid HTTPS (which it will be, once the certificate above has issued), Full or Full (strict) is the right mode. Flexible mode talks to your origin over plain HTTP, which combined with an origin-side forced-HTTPS redirect can create a loop. Check and adjust the mode from the Cloudflare CDN page in the portal.
Clear your own cache first
Before assuming anything is actually broken, clear your browser cache or try a private/incognito window. Browsers aggressively cache redirect responses and mixed-content states, so a fix on the server side can look unfixed in a browser that already cached the old behavior.
When to contact support
If the certificate still hasn't issued after DNS has clearly propagated, or you've checked for mixed content and redirect loops and the site is still broken, open a ticket from Support → New ticket in the portal. It reaches a real person, not a bot. If the issue involves credentials or account access, use the secure-share panel in the ticket rather than pasting passwords into the message.