WSL2 chrome debug with Error running browser: connect ECONNREFUSED 127.0.0.1:53579
See original GitHub issueDescribe the bug WSL2 chrome debug not possible, browser opens for a moment then closes, with messege:
Error running browser: connect ECONNREFUSED 127.0.0.1:53579
To Reproduce Steps to reproduce the behavior:
- On windows 10, install WSL2
- Install VSCODE (insiders or stable)
- Try debug javascript
launch.json:
{
"name": "Launch Chrome",
"request": "launch",
"type": "pwa-chrome",
"url": "http://localhost:5000",
"trace": true,
"webRoot": "${workspaceFolder}"
},
Log File vscode-debugadapter-00e1f992.json
Vscode -> 1.56.0-insider Javacript Debugger (Nightly) v2021.4.2617
Additional context Curiously installing older versions of the javascript debugger also give the same error, even versions 3 months old Also installing older versions of Debugger for chrome and Remote WSL also fails with the same error
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
ECONNREFUSED error with WSL 2 with Chrome Debugger ...
It is a bug of vscode. This issue can be fixed by replacing extensions 'JavaScript Debugger' with 'JavaScript Debugger (Nightly)'.
Read more >ECONNREFUSED error with WSL 2 with Chrome Debugger ...
HTML : ECONNREFUSED error with WSL 2 with Chrome Debugger on VSCode [ Beautify Your Computer ... Your browser can't play this video....
Read more >WSL2 Node interpreter: ECONNREFUSED when debugging ...
try debugging the attached project (located on Windows) - debugger fails with "Error in debuggerConnector: connect ECONNREFUSED " error:.
Read more >Having some issues with Edge. Would like to ask a couple ...
Upon choosing a random windows, debugging fails with error message "Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:9222" Why ...
Read more >Error: connect ECONNREFUSED 127.0.0.1:443 - Postman
I got the following error: Error: connect ECONNREFUSED 127.0.0.1:443 ... signed certificate using any installed browser (Chrome, Firefox even…
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
getting this error on vs code
version 1.66.2
The following worked for me. If I open my project using the “Remote - WSL” VS Code extension, e.g. by typing code /my/folder in Linux, I get this issue. However, if I open the folder as a “normal Windows folder” rather than a WSL folder by browsing to \\wsl$ in Explorer I can debug OK.