chrome-remote-interface: Host header is specified and is not an IP address or localhost.
| Component | 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
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 16 (11 by maintainers)
Commits related to this issue
- Ensure that the HTTP host header always contains an IP Address Fix #340. — committed to cyrus-and/chrome-remote-interface by cyrus-and 6 years ago
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
webSocketDebuggerUrlissue 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.