Configure Mesh Central on Windows Server using IIS

[ashishbhojani]

I have a Windows Server with multiple websites hosted on IIS. I have installed MeshCentral on the server, and it is working fine when accessed via http://localhost/.

I want to host MeshCentral on IIS and make it accessible publicly via a domain. How can I achieve this? Any guidance would be appreciated!

[si458]

you would need to use IIS as a reverse proxy, try this from microsoft website
https://learn.microsoft.com/en-us/iis/extensions/url-rewrite-module/reverse-proxy-with-url-rewrite-v2-and-application-request-routing
EDIT: the link above describes how to set it up as https://my.domain.com/meshcentral/ which is a bad idea
but it will give u hints/tips how to setup the reverse proxy side of things

[ashishbhojani]

Thanks @si458 for quick reply.
I have already setup the Reverse Proxy in IIS like this

But when I try to access the domain, it gives me a 302 response code.

I have added Static Public IP of my Server as a Server Name in Mesh Central Configuration.

Am I missing anything?

[si458]

302 is a redirect which isnt what you want but deepseeks response below

To create a reverse proxy using IIS (Internet Information Services) so that requests to https://my.domain.com are forwarded to http://localhost, you can use the URL Rewrite and Application Request Routing (ARR) modules in IIS. Here's a step-by-step guide:

---

Step 1: Install Required Modules

1. URL Rewrite Module:

   • Download and install the URL Rewrite module from the official Microsoft site.

2. Application Request Routing (ARR) Module:

   • Download and install the ARR module from the official Microsoft site.

---

Step 2: Configure ARR

1. Open IIS Manager.
2. In the left-hand tree view, select the server node (not a specific site).
3. Double-click on Application Request Routing Cache.
4. In the right-hand pane, click Server Proxy Settings.
5. Check the box for Enable proxy.
6. Optionally, configure other settings like timeouts or connection limits.
7. Click Apply in the right-hand pane.

---

Step 3: Configure URL Rewrite

1. In IIS Manager, select the site you want to configure (e.g., my.domain.com).
2. Double-click on URL Rewrite.
3. In the right-hand pane, click Add Rule(s).
4. Choose Blank Rule under the "Inbound Rules" section.
5. Configure the rule as follows:
   • Name: Give the rule a name (e.g., "ReverseProxy").
   • Match URL:
     • Requested URL: Matches the Pattern
     • Using: Wildcards
     • Pattern: * (this matches all URLs).
   • Conditions:
     • Add a condition if needed (e.g., to match specific paths or headers).
   • Action:
     • Action Type: Rewrite
     • Rewrite URL: http://localhost/{R:0} (this forwards the request to localhost).
     • Check Append query string if you want to forward query parameters.
6. Click Apply.

---

Step 4: Bind the Domain to IIS

1. In IIS Manager, select the site you are configuring.
2. In the right-hand pane, click Bindings.
3. Add a binding for https://my.domain.com:
   • Type: https
   • Host name: my.domain.com
   • SSL certificate: Select the appropriate SSL certificate for your domain.
4. Click OK.

---

Step 5: Test the Configuration

1. Open a browser and navigate to https://my.domain.com.
2. The request should be forwarded to http://localhost, and you should see the response from your local server.

---

Optional: Debugging and Logging

• If the reverse proxy isn't working, check the IIS logs (C:\inetpub\logs\LogFiles) for errors.
• Enable failed request tracing in IIS for more detailed debugging.

---

Notes:

• Ensure that the local server (http://localhost) is running and accessible.
• If you're using a non-standard port for localhost (e.g., http://localhost:8080), update the Rewrite URL in Step 3 accordingly.
• If you're using a self-signed certificate for https://my.domain.com, make sure it's trusted by your browser or client.