Firefox and Firefox Developer refusing connection from VS Code debugger

[nathan-alvarez0925]

This issue started after the latest updates in both Firefox (v117) and Firefox Developer (v118 beta). Start debugging in VS Code has connection actively refused. No issues before latest updates.

[Gabones]

I'm having the same problem with Firefox (v116) and Firefox Developer (v118), Vscode (v1.82.1), Debugger for Firefox (v2.9.8)

[ChrisMSaltire]

I believe this is the same as #337. I noticed it first just after updating VSCode to 1.82.0.

[blm768]

This seems to also be related to #306. As a workaround, adding "host": "127.0.0.1" to the entry in launch.json seems to fix the issue.

[crazyjat]

This started happening to me today when I updated to VS Code 1.82.1.

I was able to get around the issue for attach by adding host: "127.0.0.1" as mentioned above, but this does not work for launch configurations.

The issues is that VS Code is now prioritizing ipv6, which doesn't work with firefox debugger. No idea how to fix. Please help!

[kayzzen01]

The solution I found so far was this command:

netsh interface portproxy add v6tov4 listenaddress=::1 listenport=6080 connectaddress=127.0.0.1 connectport=6080

It works, but I'm not able to use breakpoints. I think this might be another problem. If anyone can do it, I'd be happy to know how 😆

[llgarrido]

This seems to also be related to #306. As a workaround, adding "host": "127.0.0.1" to the entry in launch.json seems to fix the issue.

With this workaround I can see the console messages in VS but the breakpoints still do not work.

[maxenko]

This was happening in VSCode insiders for me a while ago, I guess it made it downstream to stable.

[hbenl]

Fixed in version 2.9.10.

[niklasholm]

I think this can be closed

[juliandescottes]

cc @hbenl should be fixed by your recent release, can we close it?

[hbenl]

@juliandescottes Yes, this is fixed and this issue can be closed, but I don't have the permissions to close it.

[janodvarko]

Done, thank you!