Starting manual session on selenoid-ui fails after restricting access to selenoid ui. about selenoid-ui

[vania-pooh]

@soumyathampi you just don't have this browser version in browsers.json.

[soumyathampi]

THis works fine with curl command:
curl -H'Content-Type: application/json' http://x.x.x.x:4444/wd/hub/session -d'{
"capabilities": {
"alwaysMatch": {
"browserName": "chrome",
"browserVersion": "110.0",
"selenoid:options": {
"name": "Session started using curl command...",
"sessionTimeout": "1m"
}
}
}
}'
Only manual session fails to start.

This issue happens only from ggr manual ui, after we added authentication. It was working fine before.
From selenoid instances also the browsers are launched successfully.

[vania-pooh]

@soumyathampi when using Ggr you may be redirected to the host where you don't have this version.

[soumyathampi]

If I disable the authentication, session works fine.

This is how I have enabled the authentication:
selenoid-ui:
image: "docker-release.getgotools.net/aerokube/selenoid-ui:latest-release"
network_mode: bridge
links:
- ggr-ui
- ggr
ports:
- "8080:8080"
volumes:
- "$PWD:/etc/grid-router:ro"
command: -status-uri http://ggr-ui:8888 -webdriver-uri http://ggr:4444 -timeout 15s -users /etc/grid-router/users.htpasswd

I have 2 instances connected to this ggr, both works fine. The issue comes from ggr-ui only with authentication.

Getting this error on my console while starting the session:
POST http://10.1.121.94:8080/wd/hub/session 404 (Not Found)
VM12:24 Can't start session manually e {message: 'ajax error 404', name: 'AjaxError', xhr: XMLHttpRequest, request: {…}, status: 404, …}

[vania-pooh]

@soumyathampi then make sure you are not using aerokube/ggr-ui:latest as it's broken.

[soumyathampi]

Which version should we use?

[vania-pooh]

@soumyathampi e.g. aerokube/ggr-ui:1.1.2 or aerokube/ggr-ui:latest-release.

[soumyathampi]

I am already using ggr-ui:latest-release, hardcoding to 1.1.2 also didn't fix this issue

[vania-pooh]

@soumyathampi check logs of all these containers.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.