Pulling my hair out trying to set up a Blazor Server Side application on IIS.
I've already installed the application on one test server without too much difficulty however I've now run into difficulty deploying to the client's server.
To ensure the issue wasn't with my application I tested using the Blazor Server-Side template and the same issue is found.
If I open Microsoft Edge on the server and browse to the URL of the application everything works perfectly
However, if I browse to the same URL on my local Edge browser I get a redirect from https://portal... to the servers IP address https://172.16... and then a timeout.
Could this be caused by a firewall setting blocking something that Blazor requires or a DNS issue?
Note that if I just have the website pointing to a simple website then it works fine both on the server and on my local browser.