Workaround for users who cannot use port 22 / SSH (e.g. SSH over HTTPS)

[akosyakov]

We are now rolling out SSH Gateway to all users:

• [code-desktop] Switch all SaaS VS Code Desktop users to SSH Gateway #12155

However, some users are reporting that they cannot use SSH because of firewall or ISP issues, e.g.

For me, this is currently my biggest blocking point as my ISP sometimes will block SSH (port 22) and it appears that they are putting in place a deep packet inspection method and will detect the SSH traffic even if I redirect to different ports.

Not to be confused with the following issue to find a solution for Self Installed users who have access to port 22:

• Allow configuration of connect via SSH port (e.g. port 22) #10645

For some users (e.g. SaaS) workarounds such as changing the port will not work as they do not have access to the Gitpod installation as in Self-Hosted.

Relates to:

• Some Open SSH and RSA key versions are not compatible with Gitpod SSH Gateway #12287
• Allow configuration of connect via SSH port (e.g. port 22) #10645

Original description

#7412 enables us to SSH directly into Gitpod workspace using standard SSH port. It is a standard practice to block this port in firewalls. In order to enable users to work it around we should allow to SSH over HTTPS as well.

@iQQBot mentioned that it is hard since ws-proxy already handles https port, but @csweichel i think knows a trick how to multiplex it?

Front conversations

[iQQBot]

Add another ip, and provider another domain like ssh.ws-eu26.gitpod.io
Only special users or automated programs need it

[iQQBot]

Another option is that we analyze the protocol characteristics to determine which subroutine will handle

[stale]

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.