-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: VNC viewer issue in Kubernetes with nginx ingress extra / in wss URL #2075
[🐛 Bug]: VNC viewer issue in Kubernetes with nginx ingress extra / in wss URL #2075
Comments
@amardeep2006, 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! |
Additional Troubleshooting : I tried following combinations Selenium grid Chart version 0.26.3 with Selenium-Server 4.15.0 : The NoVNC works fine without issues. Selenium grid Chart version 0.26.3 with Selenium-Server 4.16.1 : The NoVNC have issues and appends extra slash in url. |
I think the issue roots come from here this pull request was merged into trunk and delivered exactly in 4,16 |
I can confirm the issue comes from the chart itself, due to change #2073,
Also, upstream needs a fix to handle trailing slash, so users no longer have to worry about the slash. |
A workaround I think will help you continue with
|
I tried this workaround but unfortunately it did not seem to work. Still seeing extra / . |
More values need to be updated in background. Hence I have done the patch in chart 0.26.4 |
I am amazed by your work @VietND96 . I tested with 0.26.4 and issue is fixed. Really appreciate. |
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?
I upgraded to latest helm chart version 0.26.3 and NoVNC sessions have stopped working.
The selenium test cases and UI works fine without issues. Only problem is with VNC sessions. I am not using any subpaths.
I am using https setup (automatic with sectigo tls) .
I see blank screen if I click on the video icon to see session.
Clue : Interestingly I see one extra forward slash (/) in wss url before session. In browser console logs.
I have double checked INGRESS_DOMAIN env variable does not contain this extra slash.
wss://abc.com//session/d5b0aa9f497f46d9f4d6d27bdb82a08c/se/vnc
Here is my value file.
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
websock.js:231 WebSocket connection to 'wss://abc.com//session/d5b0aa9f497f46d9f4d6d27bdb82a08c/se/vnc' failed: Error during WebSocket handshake: Unexpected response code: 502
Operating System
Kubernetes
Docker Selenium version (image tag)
4.16.1
Selenium Grid chart version (chart version)
0.26.3
The text was updated successfully, but these errors were encountered: