From **12 November 2026**, Bitbucket Cloud only accepts Git over SSH on `ssh.bitbucket.org`. Connections to `bitbucket.org` over SSH will fail. HTTPS connections are not affected.

## What DeployHQ handles for you

You don't need to change your repository settings in DeployHQ. Repositories connected with a URL such as `git@bitbucket.org:workspace/repository.git` keep working: DeployHQ sends those SSH connections to `ssh.bitbucket.org` automatically. This covers:

- fetching your repository and running deployments
- Git submodules hosted on Bitbucket
- build pipeline commands that fetch private dependencies from Bitbucket over SSH (for example Composer packages or npm Git dependencies)

Bitbucket's host keys are not changing; `ssh.bitbucket.org` uses the same keys as `bitbucket.org`.

### Known hosts for build commands

If you've added Bitbucket to your project's known hosts for build commands, keep the entry for **`bitbucket.org`**: DeployHQ checks the key under that name. If you only have an entry for `ssh.bitbucket.org`, add the same key for `bitbucket.org` as well.

## What you may need to change yourself

DeployHQ can only redirect connections it makes itself. Update anything else that connects to `git@bitbucket.org` over SSH before 12 November:

- **Your own servers** that pull from Bitbucket directly, for example a `git pull` in an SSH command or a cron job. Change the remote to `git@ssh.bitbucket.org:workspace/repository.git`, or add this to the server's `~/.ssh/config`:

```
Host bitbucket.org
    HostName ssh.bitbucket.org
    HostKeyAlias bitbucket.org
```

- **Other CI tools or scripts** outside DeployHQ that use Bitbucket over SSH.

### Custom Action servers

[Custom Action](Article: #723) servers run your commands in the Docker image you choose. If those commands fetch from Bitbucket over SSH with Git (for example `git clone`, Composer or npm Git dependencies, or submodules), DeployHQ sends those connections to `ssh.bitbucket.org` too. This works with any Git version, and host keys you've pinned for `bitbucket.org` in the image keep working.

It doesn't apply in these cases, so update the URLs to `ssh.bitbucket.org` yourself:

- **Your image sets its own SSH command for Git**, through `GIT_SSH`, `GIT_SSH_COMMAND` or the `core.sshCommand` setting.
- **Your commands run `ssh` directly**, rather than through Git.

If you change URLs to `ssh.bitbucket.org` and your image pins Bitbucket's host keys, add the same keys for `ssh.bitbucket.org`, for example `ssh-keyscan ssh.bitbucket.org >> ~/.ssh/known_hosts`. Don't turn off host key checking to work around a "Host key verification failed" error.

## Further reading

- [Atlassian's announcement](https://community.atlassian.com/forums/discussion/3234032/upcoming-change-to-bitbucket-cloud-ssh-access-move-from-bitbucket-org-to-ssh-bitbucket-org)
- [Unable to access Bitbucket repository - Error 403](Article: #599)