question

DavisDaniel-8667 avatar image
0 Votes"
DavisDaniel-8667 asked AgaveJoe edited

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

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.

windows-server-iisdotnet-aspnet-core-mvcdotnet-aspnet-core-webapi
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The app on port 433 is https://<yourdomain>/ The app on port 444 is https://<yourdomain>:444

You should talk with someone in your organization to get help. It is common to have two different domains that identify each web application.

0 Votes 0 ·

Yes. I think I figured out what I need to use to solve my issue, but I'm not sure exactly how to go about it. I have to use URL Rewrite and maybe ARR but I'm not sure how.

0 Votes 0 ·

You original post indicates that you created two separate applications bound to two different ports; 443 and 444. 443 is a standard port and assumed when using an HTTPS address. Port 444 is not a standard web site port and therefore 444 must be added to the URL as stated above; http://<your domain or ip>:444.

The common solution is using IIS's "Require Server Name Indication" or host headers when the host serves several different web applications. This is called shared hosting. Essentially, the web applications can share port 443 and are identified by their certificate and domain. Since you work for an organization, I'm sure there is someone at the organization that can help you configure IIS and use a proper certificate(s). Usually this type of configuration is part of an organization's security policy.

Also, if you are supposed to use URL Rewrite Module and Application Request Routing, then I'm positive that you need to talk with someone in your organization and not a forum.


0 Votes 0 ·

0 Answers