Heads-up for Bitbucket users: your git push may start failing soon 🔔

RuwanSudheera — Tue, 10 Nov 2026 02:52:15 +0000

Starting November 12, 2026, Bitbucket Cloud is moving SSH traffic from bitbucket.org to ssh.bitbucket.org.

If your remotes look like git@bitbucket.org:workspace/repo.git, update them now to avoid connection problems.

Here's how I fixed it 👇

Option 1: Update a single repo
git remote set-url origin git@ssh.bitbucket.org:/.git

Option 2: Fix every repo on your machine at once
Add this to ~/.ssh/config:

Host bitbucket.org
HostName ssh.bitbucket.org
User git

Your existing remotes keep working, so you don't have to change each repo.

A few things worth knowing:

🔑 The first time you connect, SSH asks you to trust a new host key. Check the fingerprint against Bitbucket's official docs before typing "yes".

🪟 Windows users: open PowerShell and run this one command:

Add-Content -Path "$env:USERPROFILE.ssh\config" -Value "Host bitbucket.orgn HostName ssh.bitbucket.orgn User git" -Encoding ascii

(Use -Encoding ascii. Without it, PowerShell may save the file in a format SSH can't read.)

⚙️ Check your CI/CD pipelines, deployment servers and Docker builds that clone over SSH. They need the same update.

✅ HTTPS remotes aren't affected.

Share this with your team before the 12th so nobody is surprised by a failed push.

DEV Community: RuwanSudheera