Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

SSH over HTTPS connection failure debugging

Luca Maurelli
Luca Maurelli May 6, 2024

I'm trying to setup SSH over HTTPS. I'm on Windows, using OpenSSH trough Git. I have already created the keys and set the configuration for the alternative ssh server from the guide. I tried testing the connection with the command:

ssh -Tvvv git@bitbucket.org

But there is a connection error. I need help debugging it, due the fact that every source of information related to the error referes to the fact that "you tried SSH over an HTTPS server" which is what I'm suppoing to do to bypass the 22 port and make use of 443 thanks to atlassian. Here the log:

$ ssh -Tvvv git@bitbucket.org
OpenSSH_9.6p1, OpenSSL 3.2.1 30 Jan 2024
debug1: Reading configuration data /c/Users/maurell/.ssh/config
debug1: /c/Users/maurell/.ssh/config line 1: Applying options for *
debug1: /c/Users/maurell/.ssh/config line 23: Applying options for bitbucket.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/c/Users/maurell/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/c/Users/maurell/.ssh/known_hosts2'
debug2: resolving "altssh.bitbucket.org" port 443
debug3: resolve_host: lookup altssh.bitbucket.org:443
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to altssh.bitbucket.org [104.192.142.46] port 443.
debug3: set_sock_tos: set socket 4 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /c/Users/maurell/.ssh/bitbucket_work type 3
debug1: identity file /c/Users/maurell/.ssh/bitbucket_work-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.6
debug1: kex_exchange_identification: banner line 0: <HEAD><TITLE>Invalid HTTP Request</TITLE></HEAD>
debug1: kex_exchange_identification: banner line 1: <BODY BGCOLOR="white" FGCOLOR="black"><H1>Invalid HTTP Request</H1><HR>
debug1: kex_exchange_identification: banner line 2: <FONT FACE="Helvetica,Arial"><B>
debug1: kex_exchange_identification: banner line 3: Description: Bad request syntax</B></FONT>
debug1: kex_exchange_identification: banner line 4: <HR>
debug1: kex_exchange_identification: banner line 5: <!-- default "Invalid HTTP Request" response (400) -->
debug1: kex_exchange_identification: banner line 6: </BODY>
kex_exchange_identification: banner line contains invalid characters
banner exchange: Connection to 104.192.142.46 port 443: invalid format

The key information is "kex_exchange_identification: banner line contains invalid characters"

 

Answer
Watch
Like Be the first to like this
157 views

1 answer

1 vote
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 6, 2024

Hi Luca,

If your SSH key is properly configured - can you try performing a clone as outlined in our guide and let me know what the output is?

git clone ssh://git@altssh.bitbucket.org:443/<WorkspaceID>/<repo_slug>/

 

Cheers!

- Ben (Bitbucket Cloud Support)

View More Comments
Luca Maurelli
Luca Maurelli May 9, 2024

Running it inside the git bash terminal from Windows:


$ git clone ssh://git@altssh.bitbucket.org:443/<WorkspaceID>/<repo_slug>/
Cloning into '<repo_slug>'...
banner exchange: Connection to xxx.xxx.xxx.xxx port 443: invalid format
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Like
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 9, 2024

Hi Luca,

Sorry - just to clarify, did you replace the <workspaceID> and <repo_slug> placeholder values with your actual WorkspaceID and RepositorySlug (without <> characters)?

I should have clarified that the placeholders should have been replaced earlier, my apologies. I've just tested cloning on my repository using this command and it was successful - as long as your SSH key has been correctly configured you should be able to perform the clone without issues.

Cheers!

- Ben (Bitbucket Cloud Support)

Like
Luca Maurelli
Luca Maurelli May 9, 2024

Yes, I have replaced both workspaceID and repo_slug placeholder.

Like
Ben
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 9, 2024

Hi @Luca Maurelli 

I can see that you are a member of a Premium workspace and therefore this entitles you to private, 1:1 support with our Atlassian support team.

I have raised a ticket on your behalf in my timezone (GMT+10) for further assistance, please check your email to discuss this further and let me know what timezone you are in so that I may hand it over to the relevant team if you operate outside of my working hours.

Cheers!

- Ben (Bitbucket Cloud Support)

Like
Luca Maurelli
Luca Maurelli May 12, 2024

Thank you Ben, I have just replied back through email

Like
Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

    See all events