gitpod-io / gitpod-io/gitpod

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

Open
#7,452 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

aspect: desktop IDE component: ws-proxy feature: ssh meta: never-stale team: IDE
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

We are now rolling out SSH Gateway to all users:

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:

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:

Original description

https://github.com/gitpod-io/gitpod/pull/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 logo Front conversations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the SSH Gateway rollout in issue 12155 and the related issues 12287 and 10645. The issue also points to ws-proxy as the relevant entry point; done means users blocked from SSH port 22 can connect to Gitpod workspaces over HTTPS without self-hosted port configuration.

Written by the indexing model from the issue text.

Assessment

Domain
backend, cloud, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.