[🐛 Bug]: noVNC session not showing anything #2154
Comments
|
@kristaps-aksjonovs, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
|
I saw |
|
@VietND96 The VNC part doesn't have issues, there seems to be issue with connection with ARM image. |
|
This might not be an ARM alone issue, I'm having the same issue with a m6i.metal instance in AWS, for me the noVNC was working just up to the 1.14 after that all the versions of the selenium grid have had issues. |
|
In this case, can you open Dev Tool (press F12), tab Console to see any error logs of noVNC there? |
|
I don't get any messages on console Sometimes the noVNC connects after 5 minutes, other times it doesn't matter how long the connection is requested, it never connects. |
|
Encountered the same problem on Mac m3 |
|
Encountering this same issue with version 122 standalone chrome/edge/firefox and with node-docker 4.18.1 and hub 4.18.1
This is what I see on the Console tab and the Network tab |
|
@VietND96 Any idea when this will be addressed? |
Take latest version for possible fixes could have #2154 Signed-off-by: Viet Nguyen Duc <[email protected]>
|
In the release 4.19.0-20240328, I updated noVNC to download the latest source on their main branch instead of the version v1.4.0 (since Jan 2023) to get new updates from their side. |
|
@VietND96 |
|
I've made a fix where I'm fairly sure that is related to this. Just to be certain, can you try running with services:
selenium:
...
ulimits:
nofile:
soft: 65536
hard: 65536 |
This did not work. Below is my compose and the screenshot of Console version: "3"
services:
selenium-hub:
image: selenium/hub:4.18.1
container_name: selenium-hub
ports:
- "4442:4442"
- "4443:4443"
- "4444:4444"
ulimits:
nofile:
soft: 65536
hard: 65536
node-docker:
image: selenium/node-docker:4.18.1
volumes:
- /share/pqafiles/assets:/opt/selenium/assets
- /share/pqafiles/config/toml_server1.toml:/opt/bin/config.toml
- /var/run/docker.sock:/var/run/docker.sock
depends_on:
- selenium-hub
environment:
- SE_EVENT_BUS_HOST=selenium-hub
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- SE_VNC_NO_PASSWORD=1
- SE_OPTS=--session-timeout 297 --enable-managed-downloads true
|
|
@mikejohnstonPremierinc I have only used the standalone images myself and am not knowledgeable how that plays with the individual instances. Can you apply the additional config to |
Added to node-docker. Still did not work |
|
I'm also still having the same issue, I enabled logs to see what is going on but on the grid I have nothing other than this I also tried adding the ulimit but it didn't work either, although it did help with responsiveness on getting a new session The network I created was done with this command On the console tab I do get something new, screenshot: and for the network tab I still get the same thing, the VNC connection is stuck in changing the protocols (HTTP 101) screenshot: |
|
@VietND96 would you mind reopening? The attached PR should not have closed this. |
|
I think will let reporter verify and reopen it if they have the same experience in the latest image tag |
|
I checked with provided version and didn't had any issues. |
|
I just tested and the fixes appear to work for me, I upgraded my stacks and everything is fine. If it helps this is the docker compose that worked for me. The only note that I have is that I'm running this on x86_64, so not sure if it will work on Apple's M class processors |
|
I apologize. It actually IS fixed for me now with version 4.20. I have deleted my posts above about it not being fixed in 4.20. |
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
After starting the standalone or hub docker container and trying to debug using noVNC it shows nothing.
With Chrome Version 108, it was working as usual, but with versions 120, 121, and 122 it seems not to work anymore when trying to inspect the session.
Command used to start Selenium Grid with Docker (or Kubernetes)
docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-chrome:4.18.1-20240224Relevant log output
Operating System
macOS Sonoma 14.2.1 (23C71) Apple M3
Docker Selenium version (image tag)
4.18.1-20240224
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: