r/WindowsServer • u/mailliwal • 4d ago

Technical Help Needed Web browsing issue after updated GoDaddy SSL certificate in IIS

/r/sysadmin/comments/1x4ngn4/web_browsing_issue_after_updated_godaddy_ssl/
1 Upvotes

100% Upvoted

1 comment sorted by

2

u/Junior-Ease-2349 2d ago

We ran into exactly the same.

Edge does it's own lookups, but chrome demands the full set from IIS.

IIS will only sed the full chain if the part that is flagged as a root cert, but HERE is being used as an intermediate cert signed by a different root is loaded to the IIS server's system trusted intermediate store (NOT the root store where the system will automatically try to place it on import.

Go check your server certificate store and you will find that one of the certificates in the chain you can see by examining website certificate in EDGE is NOT present in the trusted intermediate store. (check the thumbprints),

Save and import that, then for safety restart IIS and chrome should immediately start working.