Azure Static Web Apps Custom Domain Returns 404 and TLS/SSL Certificate Mismatch

Manish Agrawal 5 Reputation points
2026-08-23T06:05:12.7533333+00:00

Hello Microsoft Azure Support,

I am experiencing an issue with my Azure Static Web App custom domain. The custom domain is showing as Ready/Validated in Azure, but the website returns HTTP 404 and the TLS/SSL certificate being served does not match the custom domain.

Static Web App: manish-portfolio-ui

Resource Group: DevPortfolio-RG

Default Static Web App URL: [https://proud-stone-0c4d65500.7.azurestaticapps.net]

Custom Domain: [https://www.manishtechnologysolution.com]

Azure Custom Domain Status: Ready / Validated Error: null DNS

Configuration: www CNAME -> proud-stone-0c4d65500.azurestaticapps.net

The default Azure Static Web App URL works correctly and returns HTTP 200, confirming that the application and deployment are working. However, the custom domain: [https://www.manishtechnologysolution.com] returns: HTTP/1.1 404 Site Not Found TLS/SSL Certificate Issue: I inspected the TLS certificate being presented by the custom domain using OpenSSL. The certificate currently being served is: CN=*.msha-slice-0-hk1-1-ase.p.azurewebsites.net The Subject Alternative Name (SAN) does not contain: [www.manishtechnologysolution.com] Because of this certificate mismatch, browsers report: NET::ERR_CERT_COMMON_NAME_INVALID The expected TLS certificate should contain: DNS:www.manishtechnologysolution.com Troubleshooting already performed: 1. Verified that the Azure Static Web App deployment is working. 2. Verified that the default Static Web App URL returns HTTP 200. 3. Verified that the custom domain exists in Azure. 4. Verified that Azure CLI reports the custom domain status as Ready. 5. Verified that Azure CLI reports errorMessage as null. 6. Verified the DNS CNAME configuration. 7. Verified public DNS resolution. 8. Verified that HTTPS traffic reaches the Azure infrastructure. 9. Verified that the custom domain returns HTTP 404. 10. Verified the TLS certificate using OpenSSL and confirmed the hostname mismatch. Based on these checks, the issue does not appear to be with the application deployment or DNS configuration. Please investigate the Azure Static Web Apps custom-domain edge routing and managed TLS/SSL certificate provisioning for: [www.manishtechnologysolution.com] Specifically, please verify why the custom domain is showing Ready/Validated while Azure is returning 404 and serving an unrelated *.azurewebsites.net TLS certificate instead of a certificate containing the custom hostname. Please check whether the custom-domain edge mapping or managed TLS certificate provisioning is stuck or incorrectly configured on the Azure side. I can provide the Azure CLI --debug output, DNS results, curl output, and OpenSSL certificate details if required. Thank you.

Azure DNS
Azure DNS

An Azure service that enables hosting Domain Name System (DNS) domains in Azure.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TP 163K Reputation points Volunteer Moderator
    2026-08-23T09:20:16.75+00:00

    Hi Manish,

    I did some investigating and it appears you have conflicting TXT records. For _dnsauth.www you have _vgnibt42zpvmzteycfvrslj54yh1i0l and _bynquvg6g8tr5uu5ub8aexu2ch3q9aj

    Please perform below steps, in sequence:

    1. In GoDaddy portal, delete both _dnsauth.www TXT records (_vgnibt42zpvmzteycfvrslj54yh1i0l and _bynquvg6g8tr5uu5ub8aexu2ch3q9aj)

    2. In GoDaddy portal, delete @ TXT record (_u9tzaegm5xfq7wc9vh715xwp9etwq0i)

    3. In Azure portal, delete www.manishtechnologysolution.com custom domain from your Static Web App

    4. Wait 1 hour (for TTL to expire on the TXT records)

    5. Open your GoDaddy portal (if not still open), sign in, and navigate to DNS page, ready to create new TXT for below step

    6. In Azure portal, navigate to your Static Web App, Settings -- Custom domains. Click Add -- Custom domain on other DNS. Enter www.manishtechnologysolution.com in the box, click Next, for Hostname record type, select TXT, click Generate code. Watch screen, when token appears immediately copy it and switch to your GoDaddy portal

    7. Quickly add _dnsauth.www TXT record with new code you copied in previous step, set TTL to 600 seconds

    8. Refresh in Azure portal custom domains blade every 5 minutes to see if validation is complete. It should switch to Validated within about 15 minutes

    9. Once it says Validated, wait 1 minute and then test www.manishtechnologysolution.com in your browser

    Please reply back here with your results, whether positive or negative.

    Above is 100% written by me, an actual human.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.