Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[🐛 Bug]: 4.28 does not start noVNC sessions correctly #15131

Closed
parholmdahl opened this issue Jan 22, 2025 · 3 comments · Fixed by #15132
Closed

[🐛 Bug]: 4.28 does not start noVNC sessions correctly #15131

parholmdahl opened this issue Jan 22, 2025 · 3 comments · Fixed by #15132

Comments

@parholmdahl
Copy link

parholmdahl commented Jan 22, 2025

What happened?

No NoVNC session can be viewed from GUI in version 4.28 of hub.

Resulting in console error:

Image

How can we reproduce the issue?

1. Upgrade Grid and nodes to 4.28
2. Run a session that takes some time, so that you can look into the session
3. Go to selenium hub GUI and session page. 
4. Click on the camera icon.

Observe that the whole page get's white, and an error in the console log appears.

Relevant log output

Uncaught TypeError: dh.default is not a constructor at x (LiveView:tsx:63:20) at LiveView.ts:77:5

Operating System

MacOS

Selenium version

4.28.0

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

Latest Chrome and Safari

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

Latest Chromedriver

Are you using Selenium Grid?

Yes. 4.28

Copy link

@parholmdahl, 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!

@vcc-ehemdal
Copy link

We're experiencing the same issue.

A minimal docker-compose.yml that demonstrates the issue:

services:
  chrome:
    image: selenium/node-chrome:132.0
    shm_size: 2gb
    depends_on:
      - selenium-hub
    environment:
      - SE_EVENT_BUS_HOST=selenium-hub
      - SE_EVENT_BUS_PUBLISH_PORT=4442
      - SE_EVENT_BUS_SUBSCRIBE_PORT=4443
    entrypoint: bash -c 'SE_OPTS="--host $$HOSTNAME" /opt/bin/entry_point.sh'

  selenium-hub:
    image: selenium/hub:4.28
    ports:
      - "4442:4442"
      - "4443:4443"
      - "4444:4444"

A minimal Python example just to get a session rolling:

import time
from selenium import webdriver

def main():
    print("Starting the remote session")
    driver = webdriver.Remote("http://localhost:4444/wd/hub", options=webdriver.ChromeOptions())
    print("Navigating")
    driver.get("https://www.google.com")
    print("Sleeping for 60 seconds")
    try:
        time.sleep(60)
    except KeyboardInterrupt:
        pass
    print("Closing the browser")
    driver.quit()


if __name__ == "__main__":
    main()

@ddavid-almeida
Copy link

Same problem here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants