Hello 👋. This is an amazing repo, I love the concept of having a benchmark app deployed across multiple providers. Bravo to all the contributors.
Problems with Azure
There's only a few open issues and I didn't see any for this, so it seemed worth mentioning that as of right now (October 14, ~10pm PST) both of the Azure examples are returning errors. (As someone who has deployed to all of these providers before, I always found Azure's cloud to be an order of magnitude more complex while simultaneously being an order of magnitude more poorly documented, so I sympathize).
When visiting nitro-azure-demo
in a Chrome browser, the following message is displayed:
Your connection is not private
Attackers might be trying to steal your information from nitro-azure-demo.nuxtjs.org (for example, passwords, messages, or credit cards).
NET::ERR_CERT_COMMON_NAME_INVALID
This server could not prove that it is nitro-azure-demo.nuxtjs.org; its security certificate is from *.staticsites-prod-westus2.p.azurewebsites.net. This may be caused by a misconfiguration or an attacker intercepting your connection.
After proceeding to the allegedly unsafe site you see:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
After opening it again in a new tab I received a different error message.
404 Web Site not found.
You may be seeing this error due to one of the reasons listed below :
- Custom domain has not been configured inside Azure. See how to map an existing domain to resolve this.
- Client cache is still pointing the domain to old IP address. Clear the cache by running the command ipconfig/flushdns.
Checkout App Service Domain FAQ for more questions.
SWA is a lot less interesting. According to the error message, it is broken. Useful information for sure.
This page isn’t working
nuxt-sigma.azurewebsites.net is currently unable to handle this request.
HTTP ERROR 500
Remind me again what 500 means?
The HyperText Transfer Protocol (HTTP) 500 Internal Server Error server error response code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
Usually, this indicates the server cannot find a better 5xx error code to response.