You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I expose port 5900 the link provided is not recognized by my realvnc viewer. I know that I could work around this using ssh tunneling to forward the port to my localhost but it would be nice if there was a way for naive users to simply connect their viewer to a url.
Describe the behaviour you'd like
On port 5900 a link that is interpretable by a vnc client that is not browser based i.e. other than no-vnc
Describe alternatives you've considered
Port forwarding through an ssh tunnel but this requires some knowledge on the part of the user.
Additional context
This is a great utility. We have a docker-in-docker desktop that runs on gitpod and works well with novnc on port 6080 but we can't connect to port 5900 (it is forwarded but realvnc does not recognize the url)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
When I expose port 5900 the link provided is not recognized by my realvnc viewer. I know that I could work around this using ssh tunneling to forward the port to my localhost but it would be nice if there was a way for naive users to simply connect their viewer to a url.
Describe the behaviour you'd like
On port 5900 a link that is interpretable by a vnc client that is not browser based i.e. other than no-vnc
Describe alternatives you've considered
Port forwarding through an ssh tunnel but this requires some knowledge on the part of the user.
Additional context
This is a great utility. We have a docker-in-docker desktop that runs on gitpod and works well with novnc on port 6080 but we can't connect to port 5900 (it is forwarded but realvnc does not recognize the url)
The text was updated successfully, but these errors were encountered: