Skip to content

Instantly share code, notes, and snippets.

@4D4B
Last active September 1, 2017 23:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save 4D4B/b8b9c3d14fdc88fd3a5663db751aa0ef to your computer and use it in GitHub Desktop.
Save 4D4B/b8b9c3d14fdc88fd3a5663db751aa0ef to your computer and use it in GitHub Desktop.
chromium devtools 404
chrome-devtools-frontend.appspot.com returns "404 Not Found"
When using devtools for remote debugging, the devtools version must match the
target browser version for compatibility. To achieve this the commit hash is
used to remote fetch the devtools. On arch and perhaps other distros, the
commit hash does not match the hash used for retrieving the corresponding
devtools (the correct hash is the parent commit hash due to an extra commit
during build - apparently). To resolve this you can determine the correct
hash and manually replace it in the url or modify the binary to the correct
hash.
To determine your current hash:
chromium --remote-debugging-port=9222
localhost:9222/json/version
The hash is specified in the WebKit-Version field following the @
To determine the correct / devtools hash:
Lookup current hash at https://chromium.googlesource.com/chromium/src/+/<hash>
The correct hash is the parent commit hash
Then you can modify the url eg: https://chrome-devtools-frontend.appspot.com/serve_file/@<hash>/inspector.html?ws=localhost:9222/devtools/page/...&remoteFrontend=true
Alternatively, modify the remote chromium library binary /usr/lib/chromium/chromium
Search for the _full_ current hash, replace with correct hash
Confirm changes using the same method used to determine current hash
Keywords:
chromium
chrome
devtools
404
not found
chrome-devtools-frontend.appspot.com
ERROR:CONSOLE(0)] "XMLHttpRequest cannot load https://chrome-devtools-frontend.appspot.com/serve_file/
inspector.js:22 Empty response arrived for script 'http://localhost:9222/devtools/screencast/screencast_module.js'
ERROR:CONSOLE(22)] "Empty response arrived for script 'chrome-devtools://devtools/bundled/screencast/screencast_module.js'", source: chrome-devtools://devtools/bundled/inspector.js (22)
ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: Screencast.ScreencastAppProvider", source: chrome-devtools://devtools/bundled/inspector.js (109)
ERROR:CONSOLE(109)] "Uncaught (in promise) Error: Could not instantiate: ProductRegistryImpl.Registry", source: chrome-devtools://devtools/bundled/inspector.js (109)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment