Read the exact browser error before changing configuration. Certificate warnings can be caused by the certificate itself, DNS pointing elsewhere, a proxy, or the visitor’s device clock.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Check the hostname: The certificate must cover the exact name being visited, such as example.com and www.example.com.
- Check DNS and proxies: Confirm every A and AAAA answer reaches the server or proxy where the certificate is installed.
- Check validity and chain: Renew expired certificates and reinstall the complete provider-supplied chain when required.
- Check redirects: Avoid competing HTTP-to-HTTPS or www redirects at the proxy, web server, application, and plugin layers.
- Check page assets: If the page loads but shows warnings, update embedded resources, fonts, scripts, and forms to HTTPS.
- Retest cleanly: Use a private window and an independent checker after caches and CDN configuration have updated.
Important notes
- Do not bypass a certificate warning when entering credentials or payment information.
- If a CDN terminates SSL, both the visitor-to-CDN and CDN-to-origin connections need correct settings.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
