Bitbucket Cloud and Data Center · Git remotes · Tested November 2, 2026

Bitbucket Git remote URLs: Cloud and Data Center

A Bitbucket repository can sit in a git remote in many shapes: HTTPS or SSH, Cloud or Data Center, with or without .git, with a user name, in another letter case. Most of them work for git. Which ones do, what each part means, and where tools go wrong, tested with git ls-remote on public repositories, signed out.

Bitbucket Cloud, every form tested

On November 2, 2026, on a public repository in Atlassian's workspace:

• https://bitbucket.org/{workspace}/{repository}.git: works. This is the HTTPS form Bitbucket hands out (the clone link in its REST API).
• Without .git, or with a slash at the end: works.
• Another letter case (https://bitbucket.org/Atlassian/Atlassian-Event.git): works, for git and for the REST API. The web page redirects to the workspace in lower case.
• A user name in front (https://{user}@bitbucket.org/…): works. The name only tells git whose credentials to send; for a public repository none were asked for.
• The web address of a page in the repository, such as …/{repository}/src/master/ or …/{repository}/pull-requests/: works too. Bitbucket Cloud reads only the first two parts of the path.
• UUIDs in place of the names, braces encoded (https://bitbucket.org/%7B{workspace UUID}%7D/%7B{repository UUID}%7D.git): works.
• www.bitbucket.org or http://: works, after a redirect to https://bitbucket.org that git reports as warning: redirecting to ….

A repository that does not exist does not say "not found" to someone signed out. Git asks for a user name, as it does for a private repository (fatal: could not read Username for 'https://bitbucket.org' when prompts are off). With credentials, the same mistake gives "You may not have access to this repository or it no longer exists in this workspace".

Over SSH, the clone link the REST API gave on November 2 was git@ssh.bitbucket.org:{workspace}/{repository}.git, on Bitbucket's new SSH host. The older git@bitbucket.org:{workspace}/{repository}.git fails during brownouts from November 12, 2026 and stops for good on December 10 (Bitbucket SSH moves to ssh.bitbucket.org). On networks that block port 22, ssh://git@altssh.bitbucket.org:443/{workspace}/{repository}.git goes over port 443. SSH needs a key, so these forms were not tested signed out.

Bitbucket Data Center, every form tested

The same day, on a public repository of a Bitbucket Data Center 9.4 server:

• https://{server}/scm/{project}/{repository}.git: works. This is the form the server hands out, with the project key in lower case (/scm/faas/… for the project FAAS).
• The key in upper case, the repository in another case, without .git, or with a slash at the end: works. The REST API also took the key and the repository in any case.
• Without /scm/ (https://{server}/{project}/{repository}.git): fails, with unable to update url base from redirection.
• The web address (https://{server}/projects/{PROJECT}/repos/{repository}/browse): fails, unlike on Cloud. Git answers not valid: is this a git repository?, and repository … not found without /browse.
• A repository that does not exist: git asks for a user name, as on Cloud.

Two shapes depend on the server. When its base URL has a path, such as https://example.com/bitbucket, every clone URL starts with it: https://example.com/bitbucket/scm/{project}/{repository}.git. A personal repository has ~{user} in place of the project: https://{server}/scm/~{user}/{repository}.git.

Over SSH the server hands out ssh://git@{server}:7999/{project}/{repository}.git. 7999 is Bitbucket's default SSH port. An administrator can choose another, and the link then shows that port.

Switching a remote

1. See what the remote is now: git remote -v.
2. Copy the new URL from the repository's Clone button, or write it from the lists above.
3. Set it: git remote set-url origin {new URL}, then git fetch.

Nothing on the server changes. Your credential helper stores sign-ins per address, so the first fetch from a new address may ask you to sign in once (Git Credential Manager and Bitbucket).

Where tools go wrong

• The new SSH host. Tools that know Bitbucket Cloud by bitbucket.org in the remote do not know ssh.bitbucket.org. In October 2026, after people switched their remotes, reports were filed against GitLens (Copy Remote File Url said "No auto-detected or configured remote providers found"), gitlinker.nvim (links with ssh. in them), T3 Code (a checkout not matched to its pull requests) and npm's hosted-git-info, whose bitbucket: shorthand still uses the old host for SSH. On November 2 all four were still open. Until a tool catches up, an HTTPS remote is the form it already knows.
• Letter case on Data Center. The server hands out the project key in lower case, while its web pages and REST API write it in upper case. A tool that compares the two letter for letter will not match them.
• Data Center SSH on another port. ssh://git@{server}:2222/… looks like any Git server. A tool cannot tell it is Bitbucket unless it is given the server's address.

Bitbucket pull requests in IntelliJ IDEA

Pull Request Inbox for Bitbucket, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, reads the workspace or project and the repository from your git remote. On Cloud it reads the HTTPS and SSH forms Bitbucket hands out, ssh.bitbucket.org included (from version 1.0.53), and altssh.bitbucket.org. On Data Center it reads /scm/ HTTPS remotes of any server and SSH remotes on port 7999; for SSH on another port, add the server in Settings | Tools | Pull Request Inbox for Bitbucket. Names are matched without regard to letter case. It then lists the pull requests that wait for your review in an IDE tool window. The review inbox is free; creating, approving and merging pull requests are Pro (US$1.50 a month, with a 30-day trial).

Get it on JetBrains Marketplace

Bitbucket is a trademark of Atlassian; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by Atlassian or JetBrains.

More: Bitbucket SSH moves to ssh.bitbucket.org · Bitbucket pull requests from the command line · "You may not have access to this repository" · 日本語