Quick introduction:
- I have Blazor Webassembly standalone app, hosted on Azure App service with custom domain and Azure provided SNI SSL, let’s say clients.company.com (Azure app original URL – company-clients.azurewebsites.net)
- To reduce cost it has been decided to change hosting to Azure Static Web App
Sequence of actions:
- Create new Azure Static Web App (company-clients-static). Standard hosting plan
- Deploy code (Azure generated static web app pipeline)
Site works perfectly with funny generated URL https://gentle-fox-039244h02.5.azurestaticapps.net - Remove custom domain from Azure App service
- Add custom domain to Azure Static Web App
- Stop Azure App service, just in case 🙂
After couple of hours, I tried to access clients.company.com and got “Unsecure connection” and ERR_CERT_COMMON_NAME_INVALID. Details show that cert, used for this site, has wildcard *.azurewebsites.net. I expected Static Web App will get new Azure generated SNI SSL cert for custom domain and at least wildcard *.azurestaticapps.net and that after changing hosting from App service to static web app and moving custom domain to static web app, site will be accessible as https://clients.company.com, but is’s not due to cert error
Does anybody have similar issue and have any idea how to solve it?
Thanks in advance.
user22132760 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.