Sudden HTTP 500 errors on node.js server

This page summarizes the projects mentioned and recommended in the original post on /r/node

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • iisnode

    Hosting node.js applications in IIS on Windows (by Azure)

  • As I said, this happened out of a sudden without any hardware or software changes. After I restarted the app on IIS it just went back to normal. I have no idea why this happened@ A few months ago something similar happened, we started getting random HTTP 500 errors (the issue was aggravated when the app was under heavy load) but the requests were returning in under 200 ms (not like now that they finish after 2 minutes). While investigating I came across this, suggesting I should set server.keepAliveTimeout = 0, indeed, that solved the issue completely, even under heavy load no HTTP 500 errors were returned, awesome! But now, this happened, I don't know if it's related in any way. Here is a graph I made with Log Parse Studio, each column is 10 minutes.

  • treblle-node

    The official Treblle SDK for NodeJS/ExpressJS. Seamlessly integrate Treblle to manage communication with your dashboard, send errors, and secure sensitive data.

  • You should try https://github.com/Treblle/treblle-node It’s a service we are developing that helps you debug APIs and help solve these mysteries. It’s free - just install the NPM package, create an account, enable it and hope it helps.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • IISNode

    Hosting node.js applications in IIS on Windows

  • Some relevant things: https://github.com/tjanczuk/iisnode/issues/323 https://stackoverflow.com/a/43440775 https://github.com/tjanczuk/iisnode/issues/643 (this sounds just like your issue): 500.1011/1013 errors Also: Check d:\home\LogFiles\Application\logging-errors.txt for uncaught extensions on the Windows machine Take it with a grain of salt, but it sounds like to me that the host machine is terminating the iisnode instance (or associated processes).

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts