HttpPlatformHandler Returns Random Port but Node is Set to 3000: A Fix

Are you experiencing issues with your Node.js application because of a random port assigned by the HttpPlatformHandler? Don't worry, this article will guide you through the process of fixing this issue, even if you're an entry-level user. Let's dive in!

Understanding the Issue

When you're running a Node.js application on a Windows server, it's common to use the HttpPlatformHandler to improve the performance of your application. However, sometimes you may encounter an issue where the HttpPlatformHandler assigns a random port to your application instead of the one you've specified in your Node.js configuration (usually port 3000). This can cause your application to malfunction, and you may see errors such as "EADDRINUSE" or "ECONNREFUSED".

The Fix

The solution to this issue is to configure the HttpPlatformHandler to use a specific port. This can be done by modifying the web.config file in your application's root directory. Here's a step-by-step guide on how to do this:

1. Open the web.config file in a text editor.
2. Locate the <handlers> section and add the following code:

<handler name="httpplatform" path="*.js" verb="*" modules="httpPlatformHandler" resourceType="Unspecified">
  <httpPlatform processPath="node.exe" arguments=".\server.js" stdoutLogEnabled="false" stderrLogEnabled="false">
    <environmentVariables>
      <environmentVariable name="PORT" value="3000" />
    </environmentVariables>
  </httpPlatform>
</handler>

2. Save the web.config file and restart your application.

By adding the <environmentVariable name="PORT" value="3000" /> line, you're telling the HttpPlatformHandler to use port 3000 for your Node.js application. This should resolve the issue of the HttpPlatformHandler assigning a random port and causing errors in your application.

Additional Tips

Here are a few additional tips that can help you troubleshoot and resolve this issue:

• Check the package.json file in your application's root directory. Make sure that the "start" script is set to the correct port. For example:

"scripts": {
  "start": "node server.js"
}</code>

• Check the server.js (or the main entry point of your application) to ensure that the server is listening on the correct port. For example:

const server = app.listen(3000, () => {
  console.log('App listening on port 3000!');
});</code>

• Check the event viewer for any errors related to the HttpPlatformHandler. This can help you identify any issues with the handler and the configuration.