Viet Nguyen Duc

@kisuro, can you check the latest image tag `4.23.1`, I suspect that CLI options can be conflicted between SE_OPTS and corresponding env vars, and it is fixed

How about if you try this config for the triggers as below? ```yaml triggers: - type: selenium-grid metadata: browserName: chrome sessionBrowserName: chrome unsafeSsl: 'true' url: 'http://selenium-hub-ci:4444/graphql' ```

Via logs, I saw a few messages that looks confused ```bash firefox-1 | 2024-04-29T13:36:39.008880005Z 2024-04-29 13:36:39,008 INFO exited: browserleftoverscleanup (exit status 0; not expected) firefox-1 | 2024-04-29T13:36:40.233644881Z 2024-04-29 13:36:40,233 INFO...

@Amanyadav12345, have you deployed on K8s or docker compose?

I close this ticket since there is no input further

In your logs, there was something relates to http_res 404 on the session request on alert > 13:47:35.105 [docker-java-stream-1267231176] INFO o.x.t.d.i.j.XWikiDockerExtension - STDOUT: 13:47:35.104 WARN [SeleniumSpanExporter$1.lambda$export$3] - {"traceId": "3d1719d01dbae017914382adaa829dc6","eventTime": 1713440855104671966,"eventName":...

Below is a simple test I wrote to run on non-docker env. It passed on driver.Chrome(). However, didn't pass on Firefox (even FF

@diemol, what do you think on this case?

@ofirdassa9, can you read through https://github.com/SeleniumHQ/docker-selenium/issues/2133 For the right fix, we want help investigation and fixing the Scaler at the upstream KEDA project - https://github.com/kedacore/keda/blob/main/pkg/scalers/selenium_grid_scaler.go

@andrii-rymar, you describe about kind of this issue, right? Something like, with default strategy, given that Queue has 6 requests coming, 6 Node pods will be up. There are 6...