Use this guide when the HTTPS column shows SSL Enabled, but the browser displays a certificate warning, the site appears insecure, redirects behave incorrectly, or HTTPS does not work as expected.

If certificate provisioning remains pending, the Dashboard displays an error, or HTTPS does not show SSL Enabled, follow SSL certificate not activating instead.

Prerequisites

Before troubleshooting, confirm that:

  • The domain is added to the correct EDGE site
  • WordPress > Domains shows SSL Enabled under HTTPS
  • DNS points to the records shown in the Pressidium Dashboard
  • You are testing the exact affected hostname
  • You know whether the issue affects the root domain, www, or both

First check the certificate status

Open the site in the Pressidium Dashboard and check the SSL or domain status.

If the certificate is Pending, check that DNS points to EDGE and that DNS has had time to propagate.

If the certificate shows Error, review the domain, DNS records, and SSL configuration.

If the certificate is Enabled, continue with the browser and HTTPS checks below.

Check the browser error

Open the site using HTTPS:

https://example.com

Click the browser security icon near the address bar and review the certificate details.

Check that:

  • The certificate is valid
  • The certificate matches the domain
  • The certificate has not expired
  • The browser trusts the certificate
  • The warning is not caused by page content loaded over HTTP

The exact wording differs by browser, but the cause is usually one of these:

  • Pending or inactive certificate
  • Expired certificate
  • Domain mismatch
  • Untrusted certificate
  • Mixed content
  • Cached browser state
  • DNS still resolving to the wrong destination

Common issues and solutions

Browser shows “Not Secure”

This can happen when the page loads over HTTP, when HTTPS is not fully active, or when the page includes insecure resources.

Check:

  1. The URL starts with https://.
  2. The certificate is enabled in the Dashboard.
  3. The page does not load images, scripts, stylesheets, fonts, or iframes over http://.
  4. WordPress Address and Site Address use HTTPS if the site is expected to run fully over HTTPS.

If the certificate is enabled and the warning only appears on specific pages, mixed content is likely.

Browser shows “Your connection is not private”

This usually means the browser does not trust the certificate, the certificate does not match the domain, or the certificate is not active yet.

Check:

  • The certificate status in the Dashboard
  • The certificate domain name
  • The exact hostname you are visiting
  • Whether you are using the root domain or www
  • Whether DNS points to EDGE
  • Whether the browser is showing cached certificate information

Try a private browsing window or a different browser after confirming the certificate status.

Certificate name does not match the domain

A certificate mismatch means the certificate was issued for a different hostname than the one being visited.

Check:

  • Whether you are visiting www.example.com or example.com
  • Whether both versions are added and configured
  • Whether DNS for both versions points to EDGE
  • Whether redirects send visitors to a hostname that is not covered by the certificate

Make sure every hostname visitors use is configured in EDGE and points to the correct records.

Certificate appears expired

EDGE-managed certificates renew automatically. Custom certificates must be updated before they expire.

Check that:

  • DNS still points to EDGE
  • The affected hostname is configured in EDGE
  • The certificate details in the browser show the expected hostname
  • The issue appears in more than one browser or device
  • A custom certificate has not passed its expiration date

For an EDGE-managed certificate, contact Support if renewal appears to have failed.

For a custom certificate, update it by following Manage SSL Certificates.

Mixed content warning

Mixed content happens when an HTTPS page loads some resources over HTTP.

Common examples include:

  • Images loaded from http://
  • Scripts loaded from http://
  • Stylesheets loaded from http://
  • Fonts loaded from http://
  • Embedded content loaded from http://

To fix it:

  1. Open the browser developer console.
  2. Look for mixed content warnings.
  3. Identify the HTTP resources.
  4. Update those URLs to HTTPS.
  5. Check WordPress Address and Site Address.
  6. Clear any plugin, page, or browser cache.
  7. Retest the page.

Mixed content is usually a site-content issue, not a certificate provisioning issue.

HTTPS works in one browser but not another

This may be caused by browser cache, old certificate data, or browser-specific security state.

Try:

  • Clearing browser cache
  • Testing in a private window
  • Testing in another browser
  • Testing from another device or network

If only one browser shows the issue after other browsers work correctly, the problem is likely local browser cache or browser state.

HTTPS redirects incorrectly

Redirect issues can make SSL appear broken even when the certificate is valid.

Check:

  • The site’s redirect configuration in the Dashboard
  • Whether Force redirect to HTTPS is enabled when needed
  • WordPress Address and Site Address values
  • Redirect rules in WordPress plugins
  • Redirect rules at the origin server
  • Whether root and www redirect to a hostname covered by the certificate

If a redirect sends visitors to a hostname that is not configured in EDGE, add and configure that hostname or update the redirect target.

Origin TLS or Strict Mode causes connection errors

If EDGE connects to the origin over HTTPS, the origin certificate and TLS configuration can affect the connection between EDGE and the origin.

Check:

  • The origin server has a valid, non-expired SSL certificate
  • The origin hostname matches the certificate used by the origin
  • Strict Mode is used only when the origin certificate is valid
  • Override SNI is configured only when the origin requires a specific SNI value

If the origin certificate is invalid and Strict Mode is enabled, switch to the correct origin TLS setting or fix the SSL certificate at the origin.

SSL is active but the site still does not load

If the certificate is enabled and trusted, the problem may not be SSL.

Check:

  • DNS resolution
  • Origin availability
  • Redirect rules
  • Firewall rules
  • Whether the site is configured correctly in the Dashboard

Use Site Not Loading After Setup if HTTPS is valid but the site itself does not load.

Troubleshooting checklist

Use this checklist before contacting Support:

  • Checked SSL status in the Dashboard
  • Confirmed domain verification is complete
  • Confirmed DNS points to EDGE
  • Confirmed DNS has propagated
  • Tested the exact affected hostname
  • Checked both root and www versions if both are used
  • Reviewed the browser certificate details
  • Checked for mixed content
  • Checked redirect behavior
  • Tested in a private browser window
  • Tested from another browser or device
  • Captured the exact browser error message

Verification

The SSL issue is resolved when:

  • The site loads over https://
  • The browser shows a secure connection
  • The certificate matches the visited domain
  • The certificate is valid and trusted
  • No mixed content warnings appear in the browser console
  • Root and www versions behave as expected
  • Important pages, forms, login, checkout, and account areas load correctly

Best practices

Keep DNS and SSL stable by following these practices:

  • Complete domain verification before routing live traffic.
  • Keep DNS records pointing to the correct EDGE values.
  • Avoid changing DNS repeatedly during propagation.
  • Configure both root and www versions if visitors use both.
  • Use HTTPS URLs in WordPress settings and site content.
  • Fix mixed content warnings as soon as they appear.
  • Test SSL after domain, DNS, redirect, or origin TLS changes.

Need help?

Contact Support if:

  • HTTPS shows SSL Enabled, but browsers continue to display a certificate warning
  • The certificate does not match the affected hostname
  • An EDGE-managed certificate appears expired
  • Mixed content remains after the affected HTTP URLs have been corrected
  • HTTPS redirects continue to loop or send visitors to the wrong hostname
  • Strict Mode or origin TLS prevents EDGE from reaching the origin
  • HTTPS is valid, but the site still does not load correctly
  • You cannot identify the cause of the browser warning

Include:

  • The EDGE site and affected hostname
  • Whether the issue affects the root domain, www, or both
  • The exact browser warning
  • The browser and device used
  • A screenshot of the certificate details
  • The status shown under WordPress > Domains
  • Your current DNS records
  • Any recent DNS, redirect, SSL, or origin TLS changes
  • The date, approximate time, and timezone when the issue occurred
  • The troubleshooting steps you already completed

Where to go next