IIS with Url running front and backend, different ports, all calls go to backend?

Davis, Daniel 1 Reputation point
2021-08-16T17:35:15.897+00:00

I'm currently running 2 sites on my IIS, a reactjs front end and an ASP Net Core backend for api calls. The server IP already has a URL for the server as a whole. My problem is that if I do any call anything with the url provided by my organization, it seems to be going to the backend. When I go to the base url my browser says it can't find anything (but when I browse on the server itself it's 100% there). I have the two sites on different ports, 443 and 444.

How can I split them up so that when I go to the base url it actually goes to the front end, but then backend calls still work? This is my first time seriously setting up a server and using IIS, so please be basics 101 with any answers. My expertise is more in the coding, not the deployment, but I'm eager to learn a new hat.

Internet Information Services
ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,612 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.