Remote debugging host
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: ulty277, Unassigned)
Details
(Whiteboard: [webdriver:backlog])
Steps to reproduce:
I'm trying to run Firefox in a vm and expose it for remote connections to access from puppeteer.
This is the command I'm using to launch the browser.
firefox --headless --remote-debugging-port=9222 --remote-debugging-host=0.0.0.0 --remote-allow-hosts=x.x.x.x
Actual results:
Firefox is listening on 127.0.0.1 and accepts only calls from the local machine. Despite many efforts I'm not able to make Firefox listens to my public ip or 0.0.0.0. This is the output I'm getting while launching
*** You are running in headless mode. [GFX1-]: glxtest: Unable to open a connection to the X server WebDriver BiDi listening on ws://127.0.0.1:9222 [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
Expected results:
Firefox should be listening to my machine's public address and accept the incoming requests. With chrome I'm able to achieve the above use case. Chrome listens on 0.0.0.0 when adding the --remote-debugging-address
google-chrome --headless --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0
|
||
Comment 1•9 months ago
|
||
Please note that --remote-debugging-host is not available as an argument for Firefox as of this time. As such it is also not taken into account.
Due to security implications we didn't allow Marionette and WebDriver BiDi to listen on all interfaces on the host. Usually it's expected from users to setup the correct routing so that WebDriver clients can reach the specific end-points.
If we would consider adding this feature we most likely have to add some extra checks so that the user is aware of the risks doing that.
Adding this feature would help us to run Firefox on cloud and connect from anywhere via client. Also, if an invalid argument is specified it's better to show that as an error/warning.
|
||
Comment 3•9 months ago
|
||
We should at least support connecting to a known IP, not necessarily support 0.0.0.0 (or that would require additional prefs)
Thank you for setting the priority. May I know, in general, how long it might take to address this enhancement?
Description
•