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

Opening port does not work #14818

Closed
MichaelVoelkel opened this issue Nov 21, 2022 · 8 comments
Closed

Opening port does not work #14818

MichaelVoelkel opened this issue Nov 21, 2022 · 8 comments
Labels
feature: ports meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team

Comments

@MichaelVoelkel
Copy link

Objective

Hi,

I want to use VNC, however, I cannot use the container that Gitpod provides because I have my own custom image.

Now, that works in essence fine. I have VNC running on 5900 and my local netcat also tells me that this is working fine.

However, the exposed port seems to be seen ONLY as https... this makes no sense, I want to have the port open but not via https clearly, the protocol IS VNC.

How can I accomplish this? It seems, it's not possible. But then again, you have some guides that tell that VNC works (I don't see how because they would need to tunnel via https?!)

@axonasif
Copy link
Member

@axonasif axonasif added feature: ports team: workspace Issue belongs to the Workspace team labels Nov 21, 2022
@axonasif
Copy link
Member

axonasif commented Nov 21, 2022

And about http ports on the web version, this is relevant:

@MichaelVoelkel
Copy link
Author

Ok, thanks, got it!
So I will have locally something that tunnels VNC via https and expose that. Not perfect, but ok

@gtsiolis gtsiolis changed the title Feedback Issue: Opening port does not work Opening port does not work Nov 21, 2022
@stale
Copy link

stale bot commented Feb 19, 2023

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Feb 19, 2023
@stale stale bot closed this as completed Apr 2, 2023
@github-project-automation github-project-automation bot moved this to Awaiting Deployment in 🌌 Workspace Team Apr 2, 2023
@braughtg
Copy link

braughtg commented Dec 10, 2023

@MichaelVoelkel

Ok, thanks, got it! So I will have locally something that tunnels VNC via https and expose that. Not perfect, but ok

Were you able to get this to work? If so, any tips or pointers? I'm struggling with the same issue now. Thanks!

@axonasif
Copy link
Member

axonasif commented Dec 12, 2023

Hi @braughtg, a very simple way is to just open your workspace in VSCode Desktop for auto port-forwarding and then connect to localhost:5900 using a VNC client.

Relevant links:

Although, may I ask, why not just use the noVNC web client?

@braughtg
Copy link

braughtg commented Dec 12, 2023

@axonasif

Although, may I ask, why not just use the noVNC web client?

We are connecting to an full GUI desktop environment and the copy/paste between the host machine and the noVNC client in the browser requires the use of the "clipboard" tool in the noVNC client, which is inconvenient. Using a full VNC client makes the copy/paste behavior between the host and the remote machines seamless.

I have seen that there are issues and a PR open in noVNC to address this issue, but they have been open and unresolved for quite some time:

I have developed a spike for another project to illustrate how this can work. In case it is helpful to anyone else, it is here:

@axonasif
Copy link
Member

@braughtg makes sense, thanks for sharing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: ports meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team
Projects
No open projects
Status: Awaiting Deployment
Development

No branches or pull requests

4 participants