CODEWITHSUNDEEP
gitsshatlassian-sourcetree
Fer García
Fer García

Reputation: 970

Git through SSH using port 443 in Windows with SourceTree client

I'm trying to connect to a BitBucket Git account using SSH at work. The network admin has blocked the 22 port (used by default for SSH) so I'm trying to connect using port 443 (the https port).

The problem is, where do I configure that in my Atlassian SourceTree client? If I try to connect to bitbucket.org:443 (in a Git bash terminal window) by using:

ssh -v [email protected] -p 443

The program establishes a connection, but now my problem is to configure that port in the Git client (I don't see any port configuration setting in the Options dialog inside SourceTree).

Thanks in advance for any help.

Edit - In Linux there's a .ssh/config file where one could edit the host configuration (including the connection port), but AFAIK my Windows client don't uses that config file because it establishes SSH connection using the PuTTY agent.

Upvotes: 0

Views: 5138

Answers (2)

Fer García
Fer García

Reputation: 970

After some research it seems that BitBucket no longer allows SSH on 443 port (official info in this link). So I'm stuck (for now) with https for my in-work connections.

Anyway, one could solve my "original problem" by changing the way SourceTree connects using SSH (from Plink to OpenSSH, see picture below). That way the program would use the ~/.ssh configuration and key files to establish a connection (as in Linux) and that config file could use a different port (see this link for a further explanation on this).

SourceTree's SSH Client Configuration

Upvotes: 2

Lucas
Lucas

Reputation: 14949

Ok, so this would be a hack, but, SourceTree uses plink. It has its own copy that it keeps in C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\plink.exe. You could rename that file to C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\actualplink.exe and create a batch file called C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\plink.bat. In that file you could

C:\Program Files (x86)\Atlassian\SourceTree\tools\putty\actualplink.exe -P 443 %*

Note, this is not tested, and depends on how SourceTree actually executes plink, but it I think it just might do the trick.

Upvotes: 0

Related Questions