azure static web app PR_END_OF_FILE_ERROR

Question

I am trying to access

https://polite-smoke-0c6531b03.1.azurestaticapps.net/

Which is the default auto generated url for a Azure Static Web App. Puzzled as to why Chrome and Fire Fox (and Virgin Media router) prevents loading.

This is not the first static web app i have created (first without api tho').

The site is the result of Azure DevOps pipleine, i can down load the build artifact and run that locally without issues, The publish step in the pipeline finishes successfully (plus you can see the files being copied across)

This is the config file that is included in the build step.

staticwebapp.config.json

{
  "globalHeaders": {
    "content-security-policy": "frame-ancestors 'self'; upgrade-insecure-requests",
    "Permissions-Policy": "autoplay=()",
    "Referrer-Policy": "no-referrer",
    "X-Content-Type-Options": "nosniff",
    "X-Frame-Options": "SAMEORIGIN",
    "X-Permitted-Cross-Domain-Policies": "none"
  },
  "navigationFallback": {
    "rewrite": "/index.html",
    "exclude": ["/images/*.{png,jpg,gif}", "/css/*"]
  }
}

Answer 1

anonymous user thank you for reporting this issue. We have a similar issue reported on GitHub:

After diving further into this, it turns out that the ISP had blocked the domain due to phishing concerns. We believe this is happening as new SWA's may have the '.1.azurestaticapps.net' subdomain. This new subdomain is a side effect of architectural improvements and for the most part should be transparent to interactions with SWA.
If you are hitting SSL_PROTOCOL_ERROR or hitting DNS issues when reaching the default hostname of your SWA, you may need to contact your ISP to allowlist your domain as they may have incorrectly flagged it.
We will keep this issue open so others may comment if they are hitting similar issues with their ISPs.

Would you mind testing with a different internet provider?

Answer 2

@Simona Cotin , thanks for the reply.

I've recreated a SWA and redeployed project. It looks like Virgin Media UK is blocking the new site (default url https://zealous-water-0f899e503.1.azurestaticapps.net/)

Accessing the new site with Vodafone mobile network is okay

I've used this service, it reports are not positive:

https://www.ssltrust.co.uk/ssl-tools/website-security-check?domain=zealous-water-0f899e503.1.azurestaticapps.net