404 Not Found error when attempting to remote debug a headless instance of chromium

[Travis Bruce]

I'm running a headless instance of chromium on a raspberry pi on my network. Here is the chromium command line args

chromium-browser --no-sandbox --headless --remote-debugging-port=9222 --remote-debugging-address=192.168.1.126 file:///home/pi/myhtmlfile.html

After starting up, this is printed to the terminal

DevTools listening on ws://192.168.1.126:9222/devtools/browser/b72e0837-f641-42d8-970a-7b690757c4f5

Then, on my desktop PC, I open chrome and navigate to http://192.168.1.126:9222. There I see my html file that is running so I click the link which redirects me to this long url

https://chrome-devtools-frontend.appspot.com/serve_file/@abb5172872b726072a64dfabaf45894c6ecf7369/inspector.html?ws=192.168.1.126:9222/devtools/page/B3084E0A587456BE1FB70FBFDB5E1CD&remoteFrontend=true

At this point I receive the 404 error (screenshot attached).

Does anyone know what I am doing wrong?

[Travis Bruce]

Update since no one replied and I figured out a little bit more.

I switched to non-headless mode temporarily. In this mode remote debugging worked just fine, however the url I was redirected to was much different.

Instead of being on the chrome-devtools-frontend.appspot.com domain, the link was: http://localhost:9222/devtools/inspector.html?ws=localhost:9222/devtools/page/A9246D168C9702DD6C420E5C6B4FC22C

So then, I switched back to headless mode, and using this new url as the template, got the correct hex value to put after /page/ by going to the url that 404'd.

This resulted in the url (also had to replace localhost with the ip): http://192.168.1.126:9222/devtools/inspector.html?ws=192.168.1.126:9222/devtools/page/EB2C8BD9E579EBEB76090094ECC9A81

Which worked just fine. It seems chromium is just plain redirecting to the wrong url when in headless mode.

So, I can successfully remote debug now, but it's a real pain because I have to splice together the proper url.

[PhistucK]

Sounds like a bug, can you reproduce with Chrome (obviously not on Raspberry Pi since it is not supported, right?) with similar setup (headless on remote machine with the same flags)?

If so, you better report this at crbug.com.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chrome DevTools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/29200584-ce39-49cc-8523-be5561963c5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.