Webstorm debugging: connection refused localhost/127.0.0.1: ... Follow
Please sign in to leave a comment.
You are using Attach to Node.js/Chrome run configuration to debug application that runs in browser. This won't work - this configuration is intended to be used for attaching to remote Node.js process, not for client-side debugging.
I'm not seeing the debug option in the menu?
(I can click on the floating chrome symbol on the html file and run the programme in the browser, and then use the chrome debugger, but can't see the webstorm one.)
I do see the attach option set - do I need to disable this somehow?
>I'm not seeing the debug option in the menu?
very strange... Should be there. Can you see it in .html file menu in Project window?
>I do see the attach option set - do I need to disable this somehow?
Didsable what? What is attach option set? Attach to Node.js/Chrome run configuration?
I'm in the project window here. No debug option on the menu.
(The second screenshot in last post shows the run configuration I referred to above)
>I'm in the project window here. No debug option on the menu.
No, you are in the editor, the project tool window is closed. You can click the 1: Project button in the upper left corner to open it
But you can delete it if you like: in Run | Edit configurations, select your donations configuration and press --- (Alt+Del)
Thanks for the help. I cannot get it to work though.
You are still opening editor menu. Please select your index.html in the Project tree view and right-click to open the file menu
BTW, can you check if you check if you can see these menu items after disabling Material Theme UI plugin in Settings | Plugins? It has some known issue with menus/buttons rendering
Yes, I can see the debug menu on index.html (the boiler plate Hello World code), but not on my html file. I have to give up now as no more time
does your donationanimation.html belong to the project? I can't see this file in your project tree on the left
I've lost my ability to attach the debugger to my nodejs app as well, certainly look like a new issue.
Please start a new thread, providing the detailed problem description