Overview

Users may receive trust errors if a certificate does not match the exact hostname they are visiting.

Symptoms

• Users report inconsistent or failed access to the affected service, device, or application.
• Normal business or home workflows are interrupted, delayed, or no longer reliable.
• The issue may be isolated to one user or may affect multiple systems depending on the root cause.

Cause

Missing SAN coverage, incorrect wildcard assumptions, or the wrong certificate being bound to the site are common causes.

Resolution

Review the certificate subject and SAN entries, verify server bindings, and replace the certificate if it does not include the required subdomain.

1. Confirm the exact symptoms and identify who or what is affected.
2. Check for recent changes such as updates, password changes, hardware swaps, DNS changes, or policy adjustments.
3. Test the most likely root cause first and document all findings clearly.
4. Apply the corrective action in the least disruptive way possible and verify the issue is fully resolved.
5. Record the final outcome, any user communication, and any recommended follow-up work.

Prevention

Track hostname coverage carefully whenever new subdomains, services, or environments are added.

When to Contact Support

If the issue continues after standard troubleshooting, affects multiple users, involves data loss risk, or raises security concerns, it should be escalated to a qualified technician promptly.