Node.js crashing on start

[eduardomarchetti]

--- Launching HTTP Toolkit desktop v1.20.1 at 2025-08-06T03:08:55.390Z ---
Server cleanup check completed
Port check completed
Starting server
'node' is not recognized as an internal or external command, operable program or batch file.

I've solved it by reinstalling Node.js in my desktop but, not before trying to reinstall toolkit, since node was installed, and I was using it without any other problem ocurred.

I guess it is more like a suggestion, but, there is a way to figure when node.js is not being recognized and ask to install it again, or to locate the installation folder?

[pimterry]

Sorry for the delay in replying here! I'm not sure what's causing this, but it's not related to your system node installation - HTTP Toolkit is designed to use its own bundled version of Node in all cases. It's not really tested with versions other than the standard bundled release, so it's possible you could get weird behaviour using your system version.

On Windows, for a fresh install that bundled node version should exist at C:\Users\<username>\AppData\Roaming\httptoolkit\resources\httptoolkit-server\bin\node.exe initially, and C:\Users\<username>\AppData\Local\httptoolkit-server\client\<version>\bin\node.exe for any updated server versions. I have no idea why that wouldn't be picked up - on Windows it's all kicked off by the httptoolkit-server.cmd script in the same directly, which explicitly checks for that node binary and uses it. If you look in this directories, is node.exe present? If you run httptoolkit-server.cmd does it work as expected?