A
A
Alexey2017-12-14 09:59:37
Google Chrome
Alexey, 2017-12-14 09:59:37

Chrome Headless remote debugging?

I'll start with a description and a question:
It is necessary to perform remote debugging using Chrome Headless, namely, share a port on a Raspberry Pi that has Chromium installed and have access to it using any Chrome client, since the port remains closed at the moment.
Q: How can I make it possible to open a port and use Google Chrome?
On the Raspberry Pi 3 Model b, the chromium browser is installed and running in headless mode.

chromium-browser --headless --disable-gpu --remote-debugging-port=8601

List of open ports on Raspberry Pi:

[email protected]:~ $ sudo netstat -lptu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 localhost:8601          0.0.0.0:*               LISTEN      24878/chromium-brow

Because Raspberry Pi is at home, there is port forwarding:
Chrome Headless 8601 8601 TCP/UDP
From the Internet when scanning nmap, this port does not appear in the open list. In fact, I do not have access to it either with Chrome Dev Tools or with a simple scan.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Adva, 2017-12-14
@azovl

Your Chrome only listens for requests from the same host (localhost:8601). You need to bind it when running on the external interface: https://groups.google.com/a/chromium.org/forum/#!t...

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question