Host header is specified and is not an IP address or localhost.
See original GitHub issueComponent | Version |
---|---|
Operating system | Ubuntu 16.04 |
Node.js | 8.11.1 |
Chrome/Chromium/… | 66.0.3359.117 |
chrome-remote-interface | 0.25.5 |
Is Chrome running in a container? YES
Getting the error in the latest version of stable chrome
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
"Host header is specified and is not an IP address or localhost ...
This specific issue is not unique to Cloud Run. It originates from an existing change in the Chrome DevTools Protocol which generates this ......
Read more >Host header or origin header is specified and is not whitelisted ...
I need to use the IP 172.17.0.1 (instead of the usual localhost) since I need to run chromedriver in a Docker container, and...
Read more >Host header is specified and is not an IP address or localhost
So starting from version 66 Chrome stops accepting HTTP connections to the debugging protocol server if the "host header is specified and is...
Read more >Host Header - What is an HTTP Host Header injection?
The HTTP host header is a request header that specifies the domain that a client (browser) wants to access. This header is necessary...
Read more >Trusted Host settings | Installing Drupal
If the Host header of the HTTP request does not match the defined ... (or localhost IP address, 127.0.01 in this example) to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In my case, I used k8s service name as the link URL, so I bypass the restriction by using DNS lookup to turn host name to IP address, then use it to connect the headless chrome instance.
It works.
Like this:
It could be but since the
webSocketDebuggerUrl
issue appears to be a bug of Chrome I would wait a response from the Chromium team.The simplest workaround is IMHO using the IP address directly.