A browser certificate warning means it could not establish the expected trust for that address. It may involve an expired certificate, a hostname mismatch, or another configuration issue. Record the warning rather than bypassing it.
Check the address and scope
- Confirm the exact domain and whether the problem affects the www address, the address without www, or a subdomain.
- Check that your device date and time are correct.
- Compare another browser or device if available. Record whether all visitors are affected or only one device.
- Note whether the browser blocks the page entirely or the page loads with a warning about insecure content. These are different problems.
Check the certificate status
If you have authorized cPanel access, look for SSL/TLS Status or the equivalent tab in SSL/TLS Certificates, depending on the interface. Note the affected hostname and any validation error.
A recent DNS change, a missing hostname, or a certificate-authority validation problem can affect issuance. If a proxy or CDN sits in front of your hosting, its certificate configuration may also need review. Do not assume that repeatedly requesting a new certificate will resolve the underlying cause.
Avoid making unrelated changes
Do not disable HTTPS redirects, remove security settings, or bypass a certificate warning to enter passwords. Avoid changing nameservers just to test a certificate. Tell AvrinTech about a recent hosting migration, domain change, or SSL update so the relevant layer can be checked.
What to send us
- The exact affected URL and warning text or code.
- A screenshot with confidential information removed.
- When the issue began and which devices or networks reproduce it.
- Any cPanel validation message and recent DNS or hosting changes.
If your site takes payments or collects customer information, say whether those functions are affected. We can then assess the relevant certificate and configuration without guessing at the cause.
Further guidance: cPanel: SSL/TLS Status.
