I am also facing the issue with SSL - In my scenario it is my machine's antivirus is causing the problem. Can you try setting the custom domain as the default one and check whether the issue persist?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi Folks
We’ve deployed an Application Gateway with WAF and front-end Public IP in front of a Static Web App. The Static Web App has the default Azure assigned name (something.azurestaticapps.net) and the custom name of the application is abc.xyz.com. It’s an Azure-only environment, meaning there’s no AD DS (on-prem) and so AAD is used for authentication.
We’ve added custom domain (abc.xyz.com as TXT and www.abc.xyz.com as CNAME as per guidance here https://learn.microsoft.com/en-gb/azure/static-web-apps/custom-domain?wt.mc_id=azurestaticwebapps_inline_inproduct_general&tabs=azure-dns#add-domain-using-txt-record-validation)
The issue we’re facing is that when an Internet user browse for the app abc.xyz.com, after the authentication passes (so AAD is out of picture), the URL in the browser automatically changes to something.azurestaticapps.net:80 and it generates the following error:
I’ve followed the guidance in the articles:
However, the issue still persists. Any pointers if someone has already seen / resolve this issue.
Thanks
Taranjeet Singh
I am also facing the issue with SSL - In my scenario it is my machine's antivirus is causing the problem. Can you try setting the custom domain as the default one and check whether the issue persist?