Why do some clients reject my new IIS certificate?

November 16, 2026 3 answers
Asked by 2x+cachewicket_594

After updating a GoDaddy certificate on IIS for the R1 chain, some clients get NET::ERR_CERT_AUTHORITY_INVALID. Chrome on an iPhone fails, but Edge on a desktop works. The root, intermediate and site certificate are installed in their respective Windows certificate stores. What should I check?

Answers

5d!circuitbasket_719

Start by checking the chain the server actually sends, not just what appears in the Windows certificate console. An external TLS checker can flag an incomplete chain or a missing intermediate.

IIS builds the chain from the certificates available to the server. Confirm the site is bound to the new leaf certificate and that the matching intermediate is available in the local computer's intermediate certificate store. Then test the public endpoint again.

Jorven+6t:

If there's a proxy or load balancer terminating TLS in front of IIS, check its certificate chain too. The public test may be seeing that device rather than IIS.

Reply to this answer
8g!ferrulepouch_351

Installing the R1 root on the IIS server does not make the iPhone trust it. Those are separate trust stores. The desktop succeeding could mean it trusts a chain that the phone doesn't, or that it has an intermediate available which the phone doesn't.

Check whether GoDaddy provides an alternate chain using the R1 certificate cross-signed by the older G2 root. The self-signed R1 root and the cross-signed certificate can have the same subject name, so compare their issuers rather than relying on the name alone. Use the chain GoDaddy specifies for compatibility and verify what the server sends afterward.

Reply to this answer
8t!clampfolder_492

Make sure both devices are reaching the same endpoint before chasing browser differences. Split DNS, IPv6, or a proxy could put them on different servers. Compare the leaf certificate and chain presented to each client.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions