You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting a driver (chrome or firefox, it doesn't matter), macosx firewall may issue a dialog asking
for a permission for incoming connections. The culprit is free_port() in common.service.utils
free_socket.bind(('0.0.0.0', 0)) should be either
free_socket.bind(('127.0.0.1', 0))
or
free_socket.bind(('localhost', 0))
Note that the obtained free port is used afterwards
with localhost, the ideal option should be free_socket.bind(('localhost', 0))
The dialogue closes itself almost immediately so a user has no chance to allow for 0.0.0.0 bindings.
One can go around the issue by assigning the port itself.
To Reproduce
One needs to make sure that we haven't given a permission to a firewall to allow to python bind to 0.0.0.0.
Then a simple python script will trigger the dialogue
from selenium import webdriver
driver = webdriver.Chrome(options=options)
Expected behavior
You should not use 0.0.0.0 when binding.
Environment
OSX, latest chromedriver (but it doesn't matter since this is triggered in common.utils), latest selenium
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
When starting a driver (chrome or firefox, it doesn't matter), macosx firewall may issue a dialog asking
for a permission for incoming connections. The culprit is free_port() in common.service.utils
free_socket.bind(('0.0.0.0', 0)) should be either
free_socket.bind(('127.0.0.1', 0))
or
free_socket.bind(('localhost', 0))
Note that the obtained free port is used afterwards
with localhost, the ideal option should be free_socket.bind(('localhost', 0))
The dialogue closes itself almost immediately so a user has no chance to allow for 0.0.0.0 bindings.
One can go around the issue by assigning the port itself.
To Reproduce
One needs to make sure that we haven't given a permission to a firewall to allow to python bind to 0.0.0.0.
Then a simple python script will trigger the dialogue
from selenium import webdriver
driver = webdriver.Chrome(options=options)
Expected behavior
You should not use 0.0.0.0 when binding.
Environment
OSX, latest chromedriver (but it doesn't matter since this is triggered in common.utils), latest selenium
The text was updated successfully, but these errors were encountered: