-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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]: Squid Proxy being injected into session creation when on gitlab. #9967
Comments
@alex4200, 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
After troubleshooting the issue, please add the Thank you! |
Looking at this issue it looks like a proxy is blocking the calls for some reason. It could be related to #9925 or something else. Please can you put a list of all the environment variables that are in use in your CI and any other bits of information that we can use to help debug. We don't have a gitlab setup so this will require you to help us. |
There are five variables that are related to a proxy: HTTPS_PROXY=http://some.url:80 other variables:
|
Hi, we are suffering from this issue, I cant see any PR but I can see a commit (153298f) is there any ticket that remains open for us to track this? |
I have the same problem, and if I roll back Selenium to version 3.141.0. then the problem disappear. |
This has been released in 4.1. I don't have a proxy environment so if you have a look at the change that was made and are able to help fix it that would be great. The code should be handled now for gitlab since we're now handling |
The above mentioned error I experienced with selenium 4.0 does not seem to happen again with selenium 4.1. It really looks there was a bug and it is fixed now. Thanks! |
Perfect! |
I still have this issue on selenium 4.1.0 (3.141.0 - work correctly, just update selenium version) proxy variables:
chrome var:
in gitlab-ci.yml selenium as service:
specify remote url in app:
log snap with error:
|
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. |
If people are setting no_proxy for certain values to get around the need to have a proxy for localhost, mostly, then we should set the poolmanager to proxymanager if not in no_proxy or poolmanager if it is. Fixes SeleniumHQ#9925 Fixes SeleniumHQ#9967
What happened?
When I run a gitlab pipeline with a short test code with selenium 4.0 it fails. With selenium 3.141 it works. No other change has been made
How can we reproduce the issue?
Relevant log output
Operating System
ubuntu I guess
Selenium version
4.0.0
What are the browser(s) and version(s) where you see this issue?
chrome: 92.0.4515.107-1_amd64
What are the browser driver(s) and version(s) where you see this issue?
chromedriver: 92.0.4515.43
Are you using Selenium Grid?
no
The text was updated successfully, but these errors were encountered: