docker-selenium icon indicating copy to clipboard operation
docker-selenium copied to clipboard
verified publisher icon SeleniumHQ

[🐛 Bug]: Chrome does not respect http proxy environment variables

Open abbasovalex opened this issue 4 months ago • 3 comments

What happened?

I use selenium/node-chrome:109.0 when I add/pass env HTTPS_PROXY/https_proxy then Chromium does not work. Important observation: use proxy with login and password

Command used to start Selenium Grid with Docker (or Kubernetes)

docker-compose up -d --no-deps --force-recreate --build chrome109.0-1

Relevant log output

[root@spb-1 prodenv]# docker logs chrome109.0-1
2025-09-08 00:40:28,553 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2025-09-08 00:40:28,558 INFO RPC interface 'supervisor' initialized
2025-09-08 00:40:28,558 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-09-08 00:40:28,558 INFO supervisord started with pid 8
2025-09-08 00:40:29,561 INFO spawned: 'xvfb' with pid 10
2025-09-08 00:40:29,563 INFO spawned: 'vnc' with pid 11
2025-09-08 00:40:29,565 INFO spawned: 'novnc' with pid 12
2025-09-08 00:40:29,568 INFO spawned: 'selenium-node' with pid 13
2025-09-08 00:40:29,610 INFO success: selenium-node entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Generating Selenium Config
Configuring server...
Setting up SE_NODE_HOST...
Setting up SE_NODE_PORT...
Tracing is disabled
Selenium Grid Node configuration: 
[events]
publish = "tcp://selenium-hub:4442"
subscribe = "tcp://selenium-hub:4443"

[node]
grid-url = "http://selenium-hub:4444"
session-timeout = "300"
override-max-sessions = false
detect-drivers = false
drain-after-session-count = 0
max-sessions = 1

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName": "chrome", "browserVersion": "109.0", "platformName": "Linux"}'
max-sessions = 1

Starting Selenium Grid Node...
2025-09-08 00:40:30,636 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-08 00:40:30,636 INFO success: vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-09-08 00:40:30,637 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
00:40:30.891 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
00:40:30.904 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
00:40:31.315 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-hub:4442 and tcp://selenium-hub:4443
00:40:31.572 INFO [UnboundZmqEventBus.<init>] - Sockets created
00:40:32.592 INFO [UnboundZmqEventBus.<init>] - Event bus ready
00:40:33.107 INFO [NodeServer.createHandlers] - Reporting self as: http://172.19.0.7:5555
00:40:33.173 INFO [NodeOptions.getSessionFactories] - Detected 2 available processors
00:40:33.303 INFO [NodeOptions.report] - Adding chrome for {"browserVersion": "109.0","se:noVncPort": 7900,"browserName": "chrome","platformName": "LINUX","se:vncEnabled": true} 1 times
00:40:33.354 INFO [Node.<init>] - Binding additional locator mechanisms: relative
00:40:33.744 INFO [NodeServer$1.start] - Starting registration process for Node http://172.19.0.7:5555
00:40:33.747 INFO [NodeServer.execute] - Started Selenium node 4.8.0 (revision 267030adea): http://172.19.0.7:5555
00:40:33.760 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
00:40:34.076 INFO [NodeServer.lambda$createHandlers$2] - Node has been added

Operating System

Linux 5.14.0-590.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 30 21:16:05 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Docker Selenium version (image tag)

node-chrome:109.0

Selenium Grid chart version (chart version)

selenium/hub:4.0.0-20211102

abbasovalex avatar Sep 07 '25 21:09 abbasovalex

@abbasovalex, thank you for creating this issue. We will troubleshoot it as soon as we can.

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

github-actions[bot] avatar Sep 07 '25 21:09 github-actions[bot]

Can you try with image tag selenium/node-chrome:109.0-20250828?

VietND96 avatar Sep 08 '25 01:09 VietND96

Hello! Thanks for quick answer. I tried. There is next change:

  • Now if I type URI over http protocol then I see Chrome' auth popup. For exdmple, type "http://myip.com". For https URI still does not work.

Also if I into the container call printenv I see env for proxy with login and password. So I would have expected not see auth popup.

This is my docker-compose.yml with proxy credentials (real login and password were changed):

  chrome-test:
    container_name: "chrome-test"
    image: selenium/node-chrome:109.0-20250828
    shm_size: 2gb
    depends_on:
      - selenium-hub
    environment:
      - SE_EVENT_BUS_HOST=selenium-hub
      - SE_EVENT_BUS_PUBLISH_PORT=4442
      - SE_EVENT_BUS_SUBSCRIBE_PORT=4443
      - SE_NODE_GRID_URL=http://selenium-hub:4444
      - SE_NODE_MAX_SESSIONS=1
      - SE_NODE_MAX_INSTANCES=1
      - SE_VNC_PORT=5993
      - SE_NODE_PORT=5530
      - HTTPS_PROXY=https://<my login>:<my password>@proxy.pingnetwork.io:7777
      - HTTP_PROXY=http://<my login>:<my password>@proxy.pingnetwork.io:7776
      - https_proxy=https://<my login>:<my password>@proxy.pingnetwork.io:7777
      - http_proxy=http://<my login>:<my password>@proxy.pingnetwork.io:7776
    ports:
      - "6993:5993"
      - "5530:5530"

abbasovalex avatar Sep 11 '25 18:09 abbasovalex