[🐛 Bug]: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure

[Nerwen18]

What happened?

Hello everyone, I'm setting up a git regression pipeline to run, but some of the tests aren't running as expected.
Locally the tests passed, I even improved the running time. But it seems on pipeline, there are some tests which fail in the early stages.
The error received:

Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.

I updated to the latest Selenide version, using Java 21, Chrome version 133.0.6943.142.
Can someone give me a hint what to check next? Thanks a lot for any advice!

How can we reproduce the issue?

.gitlab-ci.yml 

image: docker.mamdev.server.lan/internal/mamido/ci-runner:latest
stages:
  - QA
  - LIVE

Regression_Job:
  stage: QA
  script:
    - mvn clean test -Dmaven.test.redirectTestOutputToFile=false -Dselenide.browser=chrome -Dselenide.remote=http://selenium:4444/wd/hub -Dtest="tests/**" -Dspring.profiles.active=qa
  after_script:
    - mvn allure:report
    - export UPLOAD_TARGET=blob-temporary-local/mamdev/${CI_PROJECT_PATH}/${CI_PIPELINE_ID}/webcent/Regression_Job/
    - zip -r test.zip target/site/allure-maven-plugin
    - jf rt upload --build-name=$CI_PROJECT_PATH --build-number=$CI_PIPELINE_ID test.zip ${UPLOAD_TARGET}
    - echo "https://repo.svc.mamdev.server.lan/artifactory/${UPLOAD_TARGET}/test.zip!/target/site/allure-maven-plugin/index.html"
  services:
    - name: selenium/standalone-chrome:latest
      alias: selenium

Relevant log output

org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. 
Host info: host: 'runner-mzqaevgd-project-8939-concurrent-0', ip: '192.168.122.2'
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:563)
	at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:245)
	at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:174)
	at com.codeborne.selenide.webdriver.RemoteDriverFactory.create(RemoteDriverFactory.java:22)
	at com.codeborne.selenide.webdriver.WebDriverFactory.createWebDriverInstance(WebDriverFactory.java:102)
	at com.codeborne.selenide.webdriver.WebDriverFactory.createWebDriver(WebDriverFactory.java:59)
	at com.codeborne.selenide.drivercommands.CreateDriverCommand.lambda$createDriver$0(CreateDriverCommand.java:68)
	at com.codeborne.selenide.logevents.SelenideLogger.wrap(SelenideLogger.java:128)
	at com.codeborne.selenide.logevents.SelenideLogger.get(SelenideLogger.java:106)
	at com.codeborne.selenide.drivercommands.CreateDriverCommand.createDriver(CreateDriverCommand.java:44)
	at com.codeborne.selenide.WebDriverThreadLocalContainer.createDriver(WebDriverThreadLocalContainer.java:181)
	at com.codeborne.selenide.WebDriverThreadLocalContainer.createDriver(WebDriverThreadLocalContainer.java:177)
	at com.codeborne.selenide.WebDriverThreadLocalContainer.createAndRegisterDriver(WebDriverThreadLocalContainer.java:164)
	at com.codeborne.selenide.WebDriverThreadLocalContainer.getAndCheckWebDriver(WebDriverThreadLocalContainer.java:130)
	at com.codeborne.selenide.WebDriverRunner.getAndCheckWebDriver(WebDriverRunner.java:99)
	at com.unitedinternet.buizsol.webcent.tests.cashback.leda.LeDaUploadsTests.setUp(LeDaUploadsTests.java:49)
        ...
Caused by: org.openqa.selenium.TimeoutException: java.util.concurrent.TimeoutException
Build info: version: '4.28.1', revision: '73f5ad48a2'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '6.1.0-31-amd64', java.version: '21.0.6'
Driver info: driver.version: RemoteWebDriver
	at org.openqa.selenium.remote.http.jdk.JdkHttpClient.execute(JdkHttpClient.java:424)
	at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:89)
	at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:75)
	at org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:61)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:187)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:545)
	... 111 more
Caused by: java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2920)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

Operating System

Linux

Selenium version

Selenide 7.7.2

What are the browser(s) and version(s) where you see this issue?

Chrome 133.0.6943.142

What are the browser driver(s) and version(s) where you see this issue?

Selenide uses the latest browser driver

Are you using Selenium Grid?

No response

[github-actions]

@Nerwen18, 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]

We need more information about this issue in order to troubleshoot.

Please turn on logging and re-run your code. Information on how to adjust logs for your language can be found in our
Troubleshooting documentation.

[github-actions]

This issue was closed because we did not receive any additional information after 14 days.