Webstorm - When I try to use debugger got message "Debugger didn't connect during timeout"

OS: Windows 11

App: Webstorm 2023.1 (but tried in different version but have same problem)

Language: NodeJS

Library: mochaJS

A day back debugger is working. But stopped working suddenly, when I try to use debugger got message "Debugger didn't connect during timeout" and cant use breakpoints. 

I tried: install another version, remove options folder. But problem still is there.

3
13 comments

Looks like Node.js can't connect from WSL to your Windows host
Here are the instructions on how to set up Windows to work with WSL ( you have to make sure that Protected network connections is disabled for WSL for Private, Public and Protected networks).

0

I tried but message doesnt change. I tried deactivate firewall completly but doesnt work.

0
Please could you also try the `Fix WSL Firewall settings` action (available from **Help > Find action**) as suggested in
https://youtrack.jetbrains.com/issue/WEB-51649/NodeJS-Debugger-does-not-work-with-debug-runs-anymore-for-WSL2#focus=Comments-27-5058396.0-0?

Best regards,
Lena
0

Same here. It was working yesterday but stopped today. 

I have already disabled Norton and Windows Firewall completely.

Already tried to "Fix WSL Firewall" settings.

Already tried to change nameserver to host machine in WSL /etc/resolv.conf

0

Elena Pogorelova tried, but problem is still there.

0

please could you check if a workaround from WEB-59241 description helps?

0

Esquiroas I changed this port back to default value (63342) and it's working again.

 

0

Elena Pogorelova - I just wanted to inform Jetbrains that 5 of us at work are having this problem. IDE in Windows, using WSL2 Ubuntu. This issue appeared last week with the update PhpStorm update or windows update.

 

I was able to follow the workaround from WEB-59241 and it DID work. However it's not idea to have to go into C:\Program Files\JetBrains\PHPStorm and hack away on the debugConnector.js

 

Hopefully Jetbrains will figure out the root cause so we don't need to have all employees do this.

0
Please could you collect the logs per request in https://youtrack.jetbrains.com/issue/WEB-59241/NodeJSs-inspect-port-in-WSL-is-not-reachable-from-the-IDE-in-Windows#focus=Comments-27-6880891.0-0 and create a new youtrack ticket, attaching the logs and your settings (File > Manage IDE Settings > Export Settings...)?
0

Hi Elena Pogorelova, reading the thread that you sent, in this comment (https://youtrack.jetbrains.com/issue/WEB-59241/NodeJSs-inspect-port-in-WSL-is-not-reachable-from-the-IDE-in-Windows#focus=Comments-27-7268888.0-0) I found the solution for my problem. Just update wsl to last version:

wsl --update --pre-release
0

I've been getting this too, but on Mac, with Webstorm 2023.1.  It started off as an occasional thing, but now I simply can't debug with Webstorm.  Which is pretty problematic, as I kind of need a debugger.

0

Tools you issue must be different; please share the detailed problem description within a support ticket

0

I'm still getting this issue on macOS running WebStorm 2024.1

0

Please sign in to leave a comment.