How to serve NodeJS application from IIS/Windows Server Edition OS without using iisnode?

Question

So, I've written a NodeJS application on Windows having Server Edition OS, My application basically communicates with other Softwares installed in the same system by executing some commands using NodeJS child process.

Everything is working fine on localhost, as my server has a static IP, I want to serve the application to public. How can I do this without using iisnode?

I tried using iisnode, but I am falling into issues since then, I am able to server my site, but due to some permission issues on C drive, the cmd command gives Access Denied error.

Lex Li · Accepted Answer · 2023-02-13 07:47:09Z

1

Option 1:

Run your Node.js app at a local binding such as http://localhost:8080 Reference
Set up IIS as reverse proxy Reference

iisnode is a dead project you definitely shouldn't use it any more.

Option 2:

Use HttpPlatformHandler to launch your Node.js app,

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
    <handlers>
      <add name="httpPlatformHandler" path="*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" />
    </handlers>
    <httpPlatform stdoutLogEnabled="true" stdoutLogFile=".\node.log" startupTimeLimit="20" processPath="C:\Program Files\nodejs\node.exe" arguments=".\app.js">
            <environmentVariables>
                <environmentVariable name="PORT" value="%HTTP_PLATFORM_PORT%" />
                <environmentVariable name="NODE_ENV" value="Production" />
            </environmentVariables>
        </httpPlatform>
  </system.webServer>
</configuration>

Reference

Note that due to your Node.js installation, C:\Program Files\nodejs\node.exe might be a mapped path. You have to use the actual path instead, such as C:\Users\<user name>\AppData\Roaming\nvm\v16.13.2\node.exe.

Note that you also need to give IIS_IUSRS enough permissions to access node.exe.

edited Feb 13, 2023 at 7:47

answered Jun 18, 2020 at 13:11

Lex Li

64k12 gold badges126 silver badges163 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Amir Saleem Over a year ago

I am trying out the first option. I have issues in the configuration. Proxy server always redirects to the index route, here is my configuration: <rule name="Reverse Proxy to Alteryx Communicate" stopProcessing="true"> <match url="^api" /> <action type="Rewrite" url="localhost:5000{R:0}" /> </rule>

Amir Saleem Over a year ago

I want all routes to /api to my own server with full URL, currently it is redirecting to index path

samwu Over a year ago

@AmirSaleem Your pattern is incorrect, and your rewrite url is missing a "/". you can try this rule:

<rule name="Reverse Proxy to Alteryx Communicate" stopProcessing="true"> <match url="^(api.*)" /> <action type="Rewrite" url="localhost:5000/{R:0}" /> </rule>

Amir Saleem Over a year ago

Thanks for your answer, your solution worked. One more thing, how do I enforce HTTPS on this?

Collectives™ on Stack Overflow

How to serve NodeJS application from IIS/Windows Server Edition OS without using iisnode?

1 Answer 1

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related