Unable to access Bitbucket repository - Error 403

You may see one of these errors when DeployHQ connects to your Bitbucket repository over HTTPS:

To make a call, you need to use an app password. fatal: unable to access 'https://bitbucket.org/username/repo/': The requested URL returned error: 403

fatal: unable to access 'https://bitbucket.org/username/repo/': The requested URL returned error: 410

Why this happens

Bitbucket no longer accepts your account password or an app password for Git over HTTPS. App passwords stopped working on 28 July 2026. If your project was set up with one, Bitbucket now refuses the connection.

How to fix it

You can either switch to an API token, or connect over SSH instead.

Option 1: use a Bitbucket API token

1. In Bitbucket, create an API token with the read:repository:bitbucket scope. Copy the token straight away, because Bitbucket only shows it once.
2. In DeployHQ, open your project and go to Repository, then Change Repository, and update the details manually.
3. Keep the HTTPS repository URL. Enter your Bitbucket username (as shown on your Bitbucket Settings page, case-sensitive) as the username, and the API token as the password.
4. Save, then run a deployment to confirm it connects.

API tokens expire on the date you choose when you create them. Create a new token and update it in DeployHQ before then, or deployments will start failing again.

Option 2: connect over SSH

Change the repository URL to the SSH format (git@bitbucket.org:workspace/repository.git) and add your project's public key to the repository. See Updating the connected repository in an existing project and Uploading your public key to Bitbucket manually.