From f521596a8bab4cfa2abc6c667b7159711b8f49ad Mon Sep 17 00:00:00 2001 From: Kay Joosten Date: Fri, 4 Sep 2026 09:34:50 +0200 Subject: [PATCH] fix(stepup): add --remote-allow-origins=* to Behat chrome container Chrome/Chromium hardened the DevTools (CDP) WebSocket origin check: it now rejects connections with a missing/null Origin header unless started with --remote-allow-origins. A newer lscr.io/linuxserver/chromium:latest build crossed that change, so every @functional Behat scenario in the Stepup repos began failing at the first browser step with: Connection timeout: Empty read; connection dead? (WebSocket\TimeoutException) Adding the flag restores the CDP connection for dmore/chrome-mink-driver while staying on the latest image. --- stepup/docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/stepup/docker-compose.yml b/stepup/docker-compose.yml index 9f09d5f..da3d5e9 100644 --- a/stepup/docker-compose.yml +++ b/stepup/docker-compose.yml @@ -70,7 +70,7 @@ services: ports: - "9222:9222" environment: - CHROME_CLI: "--remote-debugging-port=9222 --window-size=1920,1080 --ignore-certificate-errors --ignore-ssl-errors" + CHROME_CLI: "--remote-debugging-port=9222 --remote-allow-origins=* --window-size=1920,1080 --ignore-certificate-errors --ignore-ssl-errors" volumes: - "/tmp/chromedata/:/data" networks: