Ssh Times Out While Connecting via Ipv6 But Works with Ipv4

SSH times out while connecting via ipv6 but works with ipv4

The symptom suggests that after the reinstall there's a different ssh config; check /etc/ssh/ssh_config for AddressFamily set to any; you could set to inet there or privately in ~/.ssh/config

Possible reasons for timeout when trying to access EC2 instance

Did you set an appropriate security group for the instance? I.e. one that allows access from your network to port 22 on the instance. (By default all traffic is disallowed.)

Update: Ok, not a security group issue. But does the problem persist if you launch up another instance from the same AMI and try to access that? Maybe this particular EC2 instance just randomly failed somehow – it is only matter of time that something like that happens. (Recommended reading: Architecting for the Cloud: Best Practices (PDF), a paper by Jinesh Varia who is a web services evangelist at Amazon. See especially the section titled "Design for failure and nothing will fail".)

Can't push/pull to bitbucket via SSH using IPv6

Updated after lots of help from Bitbucket support:

After much more research, the problem appears to be on my router's end (Linksys E3200) and is somehow related to IPv6. I have no trouble accessing IPv6-only sites, and everything works fine with github (this is because github is IPv4 only). However, there is something being filtered out that SSH needs to work properly. If I jack directly into my modem and run ssh -Tvv bitbucket it authenticates properly over IPv6.

In order to work around the problem (while I shop for a new router), I am forcing connections to bitbucket to only use IPv4 by adding AddressFamily inet to my ~/.ssh/config file (thanks to: https://stackoverflow.com/a/35113901/7735643). So the updated entry for bitbucket now reads:

Host bitbucket
     HostName bitbucket.org
     User git
     IdentityFile ~/.ssh/id_rsa_bitbucket
     AddressFamily inet

Gitlab SSH giving connection timeout error after taking some time

Seems to be a problem with CloudFlare

Gitlab SSH is not working for many users across Pakistan. Users in cities such as Karachi, Lahore, Islamabad and Multan have reported that they can not pull, push, clone git repositories over SSH.
The issue seems to be with CloudFlare as traffic from Pakistan is re-routed and does not reach the destination.
Using HTTPS instead of SSH or accessing through a VPN works.
The issue has been experienced at least since Friday (Sept 18).
Interestingly, Fiberlink users in Karachi can access Gitlab through SSH. PTCL, Zong, StormFiber ain’t working.

https://forum.gitlab.com/t/gitlab-pull-push-issue/42889

---

Related Topics