Hi julienMLO,
Thank you for posting in the Microsoft Community Forums.
- Check the certificate details
First, make sure that the Common Name (CN) or Subject Alternative Name (SAN) field on your SSL certificate actually contains the FQDN (Fully Qualified Domain Name) you are trying to access. You can use the OpenSSL utility to view the certificate details:
openssl s_client -connect yourdomain.com:443 -servername yourdomain.com | openssl x509 -text -noout
Look for the “Subject:” and “X509v3 Subject Alternative Name:” sections in the output and make sure they contain the correct domain name.
- Validate the certificate chain
Ensure that the certificate chain is complete and that all required intermediate certificates are properly installed. A missing or misconfigured certificate chain may also cause this error. You can view the certificate chain in your browser, usually found in the “Certificate Information” section of the Certificate Errors page.
- Check the Edge's certificate store
Although you have checked that the root certificate authority is located in Edge's certificate store, you need to make sure that all relevant intermediate certificates are there as well; Edge uses the operating system's certificate store, so you can also check these certificates in your operating system's certificate management tool.
- Clearing the Cache and Cookies
Sometimes old data in the browser cache and cookies can interfere with SSL certificate validation. Try to clear the cache and cookies of Edge browser and then re-visit the website.
- Check GPO Settings
Ensure that the GPO settings are correct and have been properly applied to the affected computer. Check for any policies that may prevent Edge Browser from properly recognizing or trusting certificates.
- Updates and compatibility
Make sure your Edge browser and operating system are updated to the latest version. Older versions of the browser or operating system may contain known issues related to SSL certificate validation.
- Testing with Other Browsers
Try accessing the same URL using another browser, such as Chrome or Firefox, to confirm that the issue is specific to the Edge browser. This will help determine if the issue is caused by a specific implementation or configuration of the Edge browser.
Best regards
Neuvi