I am hosting my Angular/.NETCore 8.3.1 application through an Azure Windows VM hosting the API and WebUI with IIS and attempting to use SSL/HTTPS (port 44301 or any other) and causes application to not respond It would seem that the UI is able to hit the vm-site files (HTTP port 80) but fails to ever attempt to access the API files
Within the VM I can see that using a browser I can hit the API and it does load up (based on system and API logs)
Whenever the WebUI attempts to reach the API it fails to even make the attempt to hit the API (based on server log and API log inactivity)
There was a case during troubleshooting that I can see that the WebUI would attempt to hit the API and it would get rejected due to CORS
Is there any documentation that walks through standing up the site with a wildcard SSL and getting the application to run on HTTPS
6 Answer(s)
-
0
Hi @smry,
Sorry, there is no document for that. Do you see any error on browser console when you are running your WebUI ?
-
0
there was 2 consistent errors from what I can remember The first was relating to CORS mismatch, the second failed in the first GetAll method like when it can't find the API
to confirm, no one else is reporting SSL issues and you guys are able to test that there is no issue on the application, correct?
-
0
Hi @smry,
Yes, right. But when using Azure there might be problems related to Azure's CORS settings and application's CORS settings. You can try to disable CORS origins in Azure portal and try again.
By the way, does it work on your local PC ?
-
0
I can hit the Swagger page from a local browser I can hit the WebUI page from local and external I was never able to ping the API from outside of the virutal machine
-
1
Hi,
But the API project doesn't have any limitation about such access. Probably Azure is preventing access.
By the way, did you try this ?
You can try to disable CORS origins in Azure portal and try again.
-
0
"Azure is preventing access." this ended up being the issue
Azure had a visual error which wouldn't show that the port wasn't saved so the application was blocking all traffic Refreshed, reset Azure, all working
