Yes, Bitbucket has changed its SSH endpoints, and this change is operationally critical for anyone using SSH to interact with Bitbucket repositories. Failing to update your configurations will result in authentication failures, breaking pushes, pulls, and deployments.

Why It Matters

SSH endpoints are the addresses your Git client uses to connect to Bitbucket. If they change and your local or automated systems aren't updated, you'll encounter errors such as Permission denied (publickey) or Connection closed by remote host, and CI/CD pipelines will fail abruptly.

What Bitbucket Changed

Bitbucket has phased out the old SSH endpoint domains in favor of new ones:

• ·Old domain: bitbucket.org
• ·New domain: altssh.bitbucket.org (or ssh.bitbucket.org in some cases)

The old endpoint is now deprecated, and all new SSH connections must use the new endpoint. While existing connections might have worked temporarily via redirects, the old endpoint is no longer supported.

Who Needs to Know

This change impacts:

1. ·Every developer with cloned Bitbucket repos over SSH
2. ·DevOps/SRE teams managing CI/CD agents (e.g., Jenkins, GitHub Actions)
3. ·System administrators overseeing deployment scripts or automation
4. ·Teams using Docker containers with embedded SSH Git operations
5. ·Anyone using ~/.ssh/config with explicit Host entries for Bitbucket

Immediate Actions to Take

1. ·

   Update remote URLs in existing repositories: bash git remote set-url origin ssh://git@altssh.bitbucket.org:443/<workspace>/<repo>.git

   Or for standard SSH port: bash git remote set-url origin git@altssh.bitbucket.org:<workspace>/<repo>.git

2. ·

   Update CI/CD configurations — check every pipeline, build script, and deployment tool.

3. ·

   Update SSH configs — if you use ~/.ssh/config:

   Host bitbucket.org HostName altssh.bitbucket.org User git Port 443

   Or Port 22 if not using 443

4. ·

   Regenerate or verify SSH keys — ensure your public key is still added in Bitbucket settings under Personal settings > SSH keys.

5. ·

   Refresh known‑hosts — remove the old entry and add the new one: bash

   Remove old entry

   ssh-keygen -R bitbucket.org

   Add new key

   ssh -T git@altssh.bitbucket.org

Common Pitfalls

• ·Only updating the hostname, not the known‑hosts entry — SSH still trusts the old RSA key, which no longer matches.
• ·CI agents using a cached known_hosts file — Docker images or VM snapshots retain the old fingerprint.
• ·Hard‑coded URLs in scripts — Search for bitbucket.org across the codebase and replace with altssh.bitbucket.org.

Proactive Monitoring

Service providers like Bitbucket periodically update infrastructure for security or performance reasons. These changes are non-negotiable for users. Subscribe to Atlassian’s status blog or announcements to stay informed. If you’re in a team, designate someone to track these updates — the operational cost of missing one far outweighs the minimal effort of staying informed.

By following the steps above, you’ll avoid downtime, keep your security posture clean, and maintain productivity.