Code-server: Chrome Debugger and Firefox Debugger

[sh7dm]

I can't run https://github.com/microsoft/vscode-chrome-debug nor https://github.com/firefox-devtools/vscode-firefox-debug on code-server, since they require browser window to open. My question is: can I force them to run with e.g. x11 forwarding or debug port forwarding? Almost any solution is acceptable!

[sh7dm]

A solution has been found by me:
As follows from this source fragment, I changed ui to workspace in package.json of extension I copied from local install. Both of extensions are functional! But I want to find a more simple & less hacky solution for that, probably it'll require code-server support. Thanks in advance!

[kylecarbs]

Interesting, they work as expected after that?

[sh7dm]

They work well, I tested them locally, but you can give them a remote-forwarded port if it's real remote development. ssh -f -n -R 6000:localhost:6000 user@host as I remember for Firefox with debug-port opened. Alternatively, x11 forwarding can be used.

[sh7dm]

I think code-server should disable incompatible exts by default, but giving user the ability to enable them from UI, of course taking the risk, with no warranty about how extensions will behave.

[kylecarbs]

I agree. We'll definitely fix :)

[sh7dm]

Hmm, I tested this with a real remote setup (client laptop + server PC in LAN) and Firefox Debugger fails printing weird errors to Log (Window). Server: Ubuntu 19.10, client: Win 10, Browser: FF. Probably this extension is incompatible with remote, but maybe it's not? Will capture the error in a moment.

[sh7dm]

Sorry for long wait.

[kylecarbs]

Hm, I'm pretty confused. Are you proxying the FF debug port?

[sh7dm]

Yes, it's remote-forwarding. SSH client is Putty. I have also tried just accessing client's port from server, since I'm connecting via LAN. It does connect, but throws those errors. Probably I should open a ticket to Firefox Debugger asking for official server support, shouldn't I?

[sh7dm]

Same with Ubuntu 19.10 & OpenSSH on client. The OpenSSH command is:
ssh [email protected] -p S -R 6000:localhost:6000 -L P:localhost:P -L 8080:localhost:8080
192.168.X.Y is server IP
S is SSH port there, not 22
P is code-server port, not 8080
8080 is an example app I try to debug.

[sh7dm]

Also, neither with Windows nor Ubuntu, Firefox didn't show the confirmation for connection, so probably there may be an issue with smth else.

[kylecarbs]

Weird issue. I couldn't see a reason why forwarding your debug port wouldn't work. Have you made any new discoveries with this?

[sh7dm]

Sadly, no. Maybe source lines from logs can tell us smth?