Cannot launch HTTP Toolkit after patching

[RaphxelS]

Hello, After the patch, the app doesn't open.

Spec: Win10 22H2 HTTP Toolkit v1.18.0

[XielQs]

Can you share a screenshot of your cmd after applying the patch?

[RaphxelS]

Nothing happen after the node . start

[XielQs]

can you cd into httptoolkit directory and start httptoolkit directly from cmd?

cd %localappdata%\Programs\httptoolkit "HTTP Toolkit.exe"

[RaphxelS]

Nothing happens

[XielQs]

what is your nodejs version?

[RaphxelS]

C:\Users\Raphael>node --version v18.16.0

[XielQs]

maybe try reinstalling node js?

[XielQs]

and try the latest version of program

[IrvanWijayaSardam]

Having the same issue right here

[XielQs]

can you do "node . start" and share a screenshot?

[MestreKarin]

It's working like a charm. My specs:

Windows 11 Pro. Patched both 1.17.2 and 1.18.0. Node v20.7.0

I only modified the appPath in index.js because I downloaded the standalone version.

May I ask: isn't possible to enable this button? I thought it was enabled in pro.

Anyways, thank you man 👍

[IrvanWijayaSardam]

got this error, http toolkit 18.1.0, node version on the image

[XielQs]

It's working like a charm. My specs:

Windows 11 Pro. Patched both 1.17.2 and 1.18.0. Node v20.7.0

I only modified the appPath in index.js because I downloaded the standalone version.

May I ask: isn't possible to enable this button? I thought it was enabled in pro.

Anyways, thank you man 👍

I think it is a httptoolkit bug, probably they will fix it soon

[XielQs]

got this error, http toolkit 18.1.0, node version on the image

Maybe restore the patch and upgrade the npm version and try again?

[IrvanWijayaSardam]

now it's working, just reinstall the HTTP Toolkit , and try patch again, i'm using this node version

[XielQs]

yea i think i can never understand that, but good to see that it's working!

[m7zr]

It's working like a charm. My specs:

Windows 11 Pro. Patched both 1.17.2 and 1.18.0. Node v20.7.0

I only modified the appPath in index.js because I downloaded the standalone version.

May I ask: isn't possible to enable this button? I thought it was enabled in pro.

Anyways, thank you man 👍

click on the + and you will see everyting

[XielQs]

Closing it due to inactivity, if anyone encounters an error with this subject I'm going to reopen it!!

[pergolafabio]

Hey, installed v1.18.1 but if i patch, the program never loads, it waits on this screen:

i filled : dummy@example.com , should i use something else?

node version 20.15.1 npm version 10.7.0 ,

i dont get any error when patching?

[pergolafabio]

if i do : node . start , it just stuck at this screen

[XielQs]

can you run node . start and provide a screenshot?

[pergolafabio]

i tried restore, did patch again, and now it indeed works!!

not sure why it didnt work first time? i now used a different email address? could that cause it? i used dummy@example.com at first :-)

[XielQs]

i don't think so, but good to see it's working!

[pergolafabio]

thnx , much appreciated for this app!

[reporter29]

I was running into the same issue and the suggestions from @IrvanWijayaSardam and @pergolafabio did not fix it. My fix was to

1. node . restore (or skip this if you haven't patched yet)
2. node . start and let toolkit fully load, then ctrl + C (I noticed some files were being downloaded that didn't happen during my initial start after patching the application for the first time)
3. node . patch
4. node . start or open the application directly via shortcut.

Just putting this here in case it helps anyone else.

[XielQs]

I was running into the same issue and the suggestions from @IrvanWijayaSardam and @pergolafabio did not fix it. My fix was to

1. `node . restore` (or skip this if you haven't patched yet)

2. `node . start` and let toolkit fully load, then `ctrl + C` (I noticed some files were being downloaded that didn't happen during my initial start after patching the application for the first time)

3. `node . patch`

4. `node . start` or open the application directly via shortcut.

Just putting this here in case it helps anyone else.

Thank you for the information! I'm still not entirely sure about the source of the error. Despite trying it multiple times on different devices and machines without any issues, it somehow worked for me without any errors or bugs.

[XielQs]

should be fixed with ce887f5 (i guess)