Webstorm 2020.2.1 Remote Debugging do not work

Looks like a permissions issu on opening a socket (similar to https://appuals.com/fix-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/). Seems that some certain dynamic port numbers are blocked by a firewall/proxy/etc.
Does the issue persist after IDE restart/system reboot? If yes, please try shutting down the IDE and then removing both ~\AppData\Roaming\JetBrains\WebStorm2020.2\options\web-browsers.xml and ~\AppData\Roaming\JetBrains\WebStorm2020.2\options\other.xml files - does the issue persist?

Elena you are awesome! Deleted these two files and everything is working as expected! Amazing. Thank you very much!

Using Rider, I only have other.xml, and this fix works. It did twice!

Deleting other.xml worked for me too.  Thanks Lucas K for well described issue and Elena for giving clear fix.

I had no web-browsers.xml file.  Deleting the other.xml file worked for me too.  It was at C:\Users\jhouser\AppData\Roaming\JetBrains\IntelliJIdea2020.3\options

Edit:  Almost worked.. now I need a debugger statement in the code or else the IntelliJ debugger will never pick up on breakpoints.  Once the first debugger statement is triggered; breakpoints work as expected.

How weird' I would have sworn this worked w/o issue last week.

I am facing same issue for IntelliJ Idea. I tried to delete the files mentioned above but it did not work.

Should I do anything else for IntelliJ Idea ?

Thank you, Elena, it worked for me.

I just removed the property "js.chrome.debugger.port..." and "last_opened_file_path" from other.xml and that was enought.

FYI - worked for me as well on WebStorm 2021.1.2 (and only other.xml)

i deleted other.xml and web-browsers.xml but  not working.

(i m using ubuntu )

this my event log

Waiting for connection to localhost:40079.
Please ensure that the browser was started successfully with remote debugging port opened.
Port cannot be opened if Chrome having the same User Data Directory is already launched.

Most probably the next auto-generated port number doesn't work for you as well

If you are sure that the port 40079 is not occupied by the other app/blocked by firewall, you can check if it's excluded from the dynamic ports range using netsh interface ipv4 show excludedportrange protocol=tcp and then replace the 40079 port with some port valid on your system in other.xml

i don't understand how to do this

Waiting for connection to localhost:45261. Please ensure that the browser was started successfully with remote debugging port opened. Port cannot be opened if Chrome having the same User Data Directory is already launched.

What problems doing this have you faced?

as far as I can see, you are using the wrong configuration for debugging; npm start runs react-scripts start, running it in debugger makes no sense unless you'd like to debug the react-scripts; you need using JavaScript Debug run configuration to attach the debugger to your page.

• create a JavaScript Debug run configuration with your app URL
• run the npm start to build your app and start the dev server
• debug the JavaScript Debug run configuration above

Please see https://www.jetbrains.com/help/webstorm/2021.1/react.html#react_running_and_debugging_debug for instructions on debugging React applications

>Waiting for connection to localhost:45261

if closing all chrome instances prior to starting the debugger doesn't help, please try the steps from https://intellij-support.jetbrains.com/hc/en-us/community/posts/360009567459/comments/4406239534354 above

>then i see in chrome

do you mean that you can see Apache web server start page if you open localhost:3000 in browser? It's strange, as the run console shows that the React dev server is started on this URL... Anyway, this problem is not related to debugging

 https://intellij-support.jetbrains.com/hc/en-us/community/posts/360009567459/comments/4406239534354 

I don't understand how to do it here

>When you press the link that appears in the picture with CTRL+SHIFT+CLICK. Apache2 Ubuntu Default Page opens in a new Chrome tab

this means that the Apache server is listening on http://192.168.0.20. This, again, has nothing to do with debugging

>I don't understand how to do it here

what is unclaer namely?

Anyway, I gave up on debug.
I can not.
Thank you for your interest

I am facing the same problem with a freshly installed WebStorm 2021.3.2 on macOS Monterey 12.1. When I try debugging a new instance of Chrome gets opened on the about:black page and after a few seconds I get the following message in PyCharm:

Waiting for connection to localhost:49680. 
            Please ensure that the browser was started successfully with remote debugging port opened. 
            Port cannot be opened if Chrome having the same User Data Directory is already launched.

I have tried deleting the two .xml files you mentioned. I have restarted the IDE and rebooted the machine, but nothing helps. What could I do? Thanks.

Found the problem, for me it was having added these two lines in WebStorm.app.vmoptions

-Djava.net.preferIPv4Stack=false
-Djava.net.preferIPv6Addresses=true

Removing them made the debugger work.

If you are running WebStorm on CentOS and you have reached the current page by an Internet search like "WebStorm Could not initialize class com.intellij.javascript.debugger.console.jcef.JCE", you might have searched for the following workaround for a CentOS problem:

Add ide.browser.jcef.enabled=false in Help | Edit Custom Properties, then restart the IDE.

See https://vocon-it.com/2022/06/13/solved-webstormcentos-bug-could-not-initialize-class-com-intellij-javascript-debugger-console-jcef-jce/ for more details.

My problem was the Hyper-v port exclusion range. Thanks Elena Pogorelova.

I have the same problem, delete file works, thaks Elena Pogorelova

Hello, the fix did works for me also with WebStorm2021.1, but after upgrade to WebStorm2022.1 Issue persits and I am not able to find any work around !!

2023-03-09 19:43:34,950 [ 304957]   INFO - #o.j.b.BuiltInWebServer - Channel will be closed due to error
2023-03-09 19:43:36,804 [ 306811]   WARN - #c.j.d.w.WipLocalVmConnection - null
io.netty.channel.StacklessClosedChannelException
    at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, ChannelPromise)(Unknown Source)
2023-03-09 19:43:42,455 [ 312462]   INFO - #c.i.a.o.PathMacrosImpl - Saved path macros: {}
2023-03-09 19:43:43,034 [ 313041]   INFO - #c.i.c.ComponentStoreImpl - Saving appEditorSettings took 16 ms, GeneralSettings took 16 ms, NodeJsLocalInterpreterManager took 15 ms, PluginAdvertiserExtensions took 32 ms, TemplateSettings took 15 ms, editorConfigEncodings took 532 ms
2023-03-09 19:43:44,002 [ 314009]   INFO - #c.i.o.c.i.s.StoreUtil - saveProjectsAndApp took 1609 ms
2023-03-09 19:47:22,316 [ 532323]   INFO - #c.i.i.a.RevealFileAction - Exit code 1
2023-03-09 19:47:22,765 [ 532772]   INFO - #c.i.c.ComponentStoreImpl - Saving appActionsLocalSummary took 15 ms, RunnerLayoutSettings took 16 ms
2023-03-09 19:47:22,796 [ 532803]   INFO - #c.i.c.ComponentStoreImpl - Saving Project(name=react, containerState=COMPONENT_CREATED, componentStore=C:\git_clones\easydoct\Dev\EasyDoct.Fo\js\react)ServiceViewManager took 16 ms
2023-03-09 19:47:39,641 [ 549648]   INFO - #c.i.u.WinFocusStealer - Foreground lock timeout set to 200000
2023-03-09 19:47:39,762 [ 549769]   INFO - #c.i.u.WinFocusStealer - Foreground lock timeout set to 0
2023-03-09 19:47:40,617 [ 550624]   WARN - #c.i.j.d.c.j.JCEFConsoleHtmlPanel - Failed to load http://localhost:63342/a03365f2-eea1-451a-ad19-6dae9187a990/frontend/console.html?internal=false
Err ERR_ABORTED: ERR_ABORTED

Any tips ? 

Tried with Edge Browser and its working well !!!

Igolus it must be a problem introduced by recent Chrome update. Chrome 111.* rejects the requests unless started with --remote-allow-origins=*; the fix is available in 2023.1 Beta. See https://youtrack.jetbrains.com/issue/WEB-59211/Cant-attach-debugger-to-Chrome-Dev-111-Invalid-handshake-response-getStatus-403-Forbidden

Elena Pogorelova I was pulling my hair out when my debugger suddenly stopped working and moving to the 2023.1 beta fixed the issue

I have the same problem. Switching to 2023.1 didn't solve this issue for me. Before with 2022.3 chrome was opened with a new window and address "about:blank" and Jetbrains didn't recognize the connection to the browser. Now with 2023.1 Chrome opens with address "localhost:4200" (that is the correct address), but it only shows the loading spinner and a white page. I'm using Chrome 111.0.5563.64 (Official Build) (arm64). I even can't open the web dev tools. The page seems to be unresponsive.

Is there any workaround?

EDIT: I found a solution: You have to deselect the option "Ensure breakpoints are detected when loading scripts" option in Run/Debug Configurations -> <your Javascript Debug configuration>

We aren't aware of such issues in 2023.1; please file a new ticket to youtrack, https://youtrack.jetbrains.com/issues/WEB, attaching the idea.log and a screenshot of your JavaScript Debug run configuration