How to fix the sudden ERR_CERT_AUTHORITY_INVALID in Azure Static Web App

Question

I have an Azure Static Web App with custom domains that was working well. Suddenly, the browser sends this SSL certificate related error message:

"It looks like the webpage might be having issues, or it may have moved permanently to a new web address.

ERR_CERT_AUTHORITY_INVALID"

I am not sure what is causing this when all has been working without a problem and I did not change anything.

Answer 1

@Kan , Thanks for posting this question.

Apologies you're experiencing this issue, I understand the issue started without any changes from your end. Typically, the error message, "ERR_CERT_AUTHORITY_INVALID", indicates that there is an issue with the SSL certificate for your Azure Static Web App. This error can occur if the SSL certificate has expired, is not trusted by the browser, or if there is a mismatch between the domain name and the SSL certificate.

To isolate the issue, you may try the following steps:

1.Ensure that the SSL certificate is valid and has not expired. You may check the validity of the SSL certificate by opening the WebApp in a browser and clicking on the padlock icon in the address bar. This will show you the details of the SSL certificate, including the expiration date.
Review the Custom domains blade/settings for your Static Web Apps blade on Azure Portal.

2.You may leverage Static WebApps diagnostics from Azure Portal> Navigate to your Azure Static Web Apps in the Azure Portal. (screenshot below)
In the left navigation, click on Diagnose and solve problems - Review - “Configuration and Management (Custom domain), and “Availability and Performance”  options.

Also, if you haven’t done this already, you may confirm, that the domain name/SSL certificate is issued by a trusted certificate authority. (by the same steps above) - You may check the issuer of the SSL certificate by opening the WebApp in a browser and clicking on the padlock icon in the address bar. This will show you the details of the SSL certificate, including the issuer and the domain name.

If you have checked all of the above and are still facing the issue, please provide some more info on the specific steps you are taking and the exact error messages you are receiving. I'll follow-up with you further.

Note: Kindly do not share any PII date on the public forum.