Remote chrome dev tools debugging

Questions / Help
#1

Hi! I run a node process started with node --inspect=0.0.0.0 (which I can safely do since it declares no service and its app doesn’t have any public IP address), I am trying to create a tunnel so that I can debug it locally with Chrome DevTools, so I run:

fly proxy 9230:9229

And add localhost:9230 to the target discovery settings of chrome://inspect, unfortunately Chrome doesn’t find my node process.
I also tried different local ports (and the default 9229) with no more success.

Is there anything obvious I missed?

Thanks

#2

I can also confirm that in my app logs I do see:

Debugger listening on ws://0.0.0.0:9229/0a3535dd-8219-41ae-abc0-a7f6ca160c3c

#3

If you’re talking to it over a WireGuard tunnel (ie, with flyctl proxy), it’ll need to bind to its fdaa: IPv6 address — you can’t talk IPv4 over our WireGuard tunnels.

#4

Thanks, it works perfectly now! :slightly_smiling_face:

#5

Yay! I did a tech support! :slight_smile:

1 Like