Troubleshooting Website SSL Certificates and Mixed Content

A certificate warning and a mixed-content warning are different problems. First identify whether the browser rejects the certificate itself or loads an HTTPS page that still references HTTP resources. Avoid changing DNS, redirects and application URLs all at once.

Check the certificate destination

1. Read the exact browser error and hostname.
2. Verify that the domain resolves to the intended hosting service, including IPv6.
3. Inspect certificate coverage and validity dates for the bare domain and www.
4. Check the hosting panel’s certificate issuance or renewal result.
5. If a CDN is present, inspect the visitor-facing certificate and origin configuration separately.

Certificate issuance requires proving control of the domain. HTTP validation needs the challenge reachable through the relevant web route; DNS validation needs the correct authoritative TXT record. Use the validation method provided by your hosting system rather than adding arbitrary records.

Find insecure resources

For mixed content, inspect browser developer tools for the blocked URL. Update the actual source of that URL, such as a theme setting, template or stored media reference, to a valid HTTPS destination. Confirm the destination supports HTTPS before changing it.

Clear the relevant site and CDN caches after the underlying fix. Do not treat disabling browser security or bypassing certificate checks as a production solution. If a third-party resource cannot be served securely, replace or remove that resource.

Test the complete navigation path

Check the homepage, a media-heavy page, login and forms in a private window. Inspect the redirect chain for loops and confirm every expected hostname lands at one consistent HTTPS address. A padlock on the homepage alone does not prove all pages are fixed.

Review domain records if the certificate belongs to an unexpected server, or the migration guide if old URLs remain after a move.