Azure Static Web Apps asset fails to load because the secure connection fails
Failed to load resource: A TLS error caused the secure connection to fail.
A deployed Azure Static Web Apps page referenced an asset over HTTPS, but the browser could not establish a valid secure connection for that asset URL.
Failed to load resource: A TLS error caused the secure connection to faildeployment
Observed message
Failed to load resource: A TLS error caused the secure connection to fail.
Why it happens
Metadata or asset URLs point at a custom domain that is not fully configured or not serving a valid certificate yet.
The site is deployed on the autogenerated Static Web Apps hostname, but icons or Open Graph assets still reference another HTTPS domain.
The app uses a custom domain in metadata before Azure Static Web Apps finishes domain and certificate setup.
How to fix it
Confirm that every referenced asset URL uses a hostname that is live and serving a valid certificate.
If the site is still being tested on the autogenerated SWA domain, avoid hard-coding metadata asset URLs to a different production domain.
Review Azure Static Web Apps custom-domain and default-domain settings so traffic and asset references resolve consistently over HTTPS.
