Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Need resolution for error: kex_exchange_identification: Connection closed by remote host

Edited

Hi,

Getting below error while accessing the Bitbucket through GitBash and/or IntelliJ IDE

Using Macbook as our personal system.


kex_exchange_identification: Connection closed by remote host
Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

 

 

 

3 answers

1 accepted

1 vote
Answer accepted

Thank you for helping out for this issue. Connected with the our Firewall team for the same and found out that the new tool ZScaler blocks 443 port as well unlike WSS. So they suggested to connect with git using HTTPS instead of SSH.

After making the necessary changes, it started working. 

 

Best regards,

Penchal

0 votes
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 12, 2022

Hi @Penchal Modhepalli

Welcome to the community.

The error message usually indicates that there's some network disconnection in between.

Would it be possible for you to confirm if you're consistently experiencing the issue?

If not, could you possibly connect to a different ISP/Network connection and see if it works there?

Let me know how it goes.

Regards,
Mark C

Hi Mark,

 

Thanks for your reply. We will check and let you know the status as earliest as possible.

 

Best regards,

Penchal

Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 13, 2022

Sure and let me know how it goes.

Regards,
Mark C

hi @Mark C @Penchal Modhepalli 

any update on this, I also facing this issue

```
kex_exchange_identification: read: Connection reset by peer

fatal: Could not read from remote repository.

 

Please make sure you have the correct access rights

and the repository exists.
```

FYI, I use home internet so I'm not behind any firewall and I can do pull/push on gitlab

some debug:
```

ssh -Tv git@bitbucket.org

OpenSSH_8.1p1, LibreSSL 2.7.3

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 47: Applying options for *

debug1: Connecting to bitbucket.org port 22.

debug1: Connection established.

debug1: identity file /Users/artiko.wibowo/.ssh/id_rsa type 0

debug1: identity file /Users/artiko.wibowo/.ssh/id_rsa-cert type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_dsa type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_dsa-cert type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_ecdsa type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_ecdsa-cert type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_ed25519 type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_ed25519-cert type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_xmss type -1

debug1: identity file /Users/artiko.wibowo/.ssh/id_xmss-cert type -1

debug1: Local version string SSH-2.0-OpenSSH_8.1

kex_exchange_identification: read: Connection reset by peer


```

please help me

solved, I follow this answer on stack overflow

edit your ~/.ssh/config

 

```

Host bitbucket.org
    AddKeysToAgent yes
    HostName altssh.bitbucket.org
    IdentityFile ~/.ssh/id_rsa
    UseKeychain yes
    Port 443

```

Like # people like this

Hi Artiko Wibowo, I assume your Indonesian? I got the same problem when tethering from my phone's Telkomsel 4G network. but the issue went away after I connect to a VPN. I can push just fine now.

So weird. These a*holes are probably doing something weird with our internet.

Like # people like this

i'm indonesian, i'm using Telkomsel 4G network and got same issue. i try @artikow solution its work for me thank you for him

Like # people like this

ohh god, i never thinking find some answer that just related for indonesian,  and WTF, its work, this fucking telkom, always suck, 

hope they dont find us here.

Like # people like this

This happened to me today with By.U connection, fixed with @artikow and some changes in line 5, 

UseKeychain yes  -> IgnoreUnknown UseKeychain

Like # people like this

same issue using telkomsel orbit. thanks @artikow its work!

Like Muhammad Yusuf likes this

Same issue using all Telkom Product.
Thank's @artikow it's work!

yupe, same issue with telkomsel product (halo and by.u). thank you for the solution.

Ayub
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jul 01, 2023

oh didn't know this, using VPN works for me too.

 

I am using the red provider as well :(

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events