-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: selenium.common.exceptions.WebDriverException: Message: <empty> #2285
Comments
@tamis-laan, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
When helm install (upgrade) successfully, a note displays with the Hub URL that can be accessed from outside. What is it? |
I changed the url to: driver = webdriver.Remote(
# command_executor="http://selenium-grid-selenium-hub.default.svc.cluster.local:4444/wd/hub",
command_executor="http://selenium-grid-selenium-hub.default.svc:4444",
options=chrome_options
) I also tried BTW nothing is logged by the hub deployment when trying to connect. |
When you running the script on host, I don't think host could reach the DNS
Then point your WebDriver tests to http://localhost:4444/wd/hub |
@VietND96 No I'm running the script as a kubernetes deployment in the same default namespace. I also tested it using a port forward as you described and I get the same error message. |
I am not sure how the service type LoadBalancer works in Minikube. I would suggest another config that you can try hub:
serviceType: NodePort And in script connect to http://localhost:31444/wd/hub |
I have run into this as well after bumping the chart version from Turns out the empty message shown by the python client is accompanied by a Setting the following chart value should resolve the issue: basicAuth:
enabled: false I don't know about the reasoning behind enabling basic auth by default, I'd not expect it, especially since it is just |
@tamasfe, thank you for your answer. It's correct, the basic auth is enabled by default in chart. In this case, the grid URL in binding would be driver = webdriver.Remote(
command_executor="http://admin:admin@localhost:4444",
options=chrome_options
) |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Exception message from the binding is improved via SeleniumHQ/selenium#14601 |
What happened?
I'm trying to run the selenium helm chart and connecting using python:
But I get the following error:
The error message non descriptive as the it's empty.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
Minikube
Docker Selenium version (image tag)
4.22.0
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: