jredmond Atlassian Team

We don't currently block specific IPs, but it's possible that something in between you and the Bitbucket servers is misbehaving. Could you please email support@bitbucket.org and include a traceroute?

You're looking at documentation for the self-hosted version of Bitbucket (known as Bitbucket Server). At the moment, there's no option for a default merge strategy in Bitbucket Cloud (bitbucket.org). Have a look…

Hi Scott, You're right that the "decline" option kills pull requests forever. Bitbucket automatically updates open pull requests with new commits, though, so if the reviewers leave the pull request open through several commits then the pull request will show all net changes. With that in mind, I'd suggest a slightly…

You don't mention it here, but I'm going to guess that you're talking about a git repo. That Stack Overflow answer is talking about a Mercurial repository, and Mercurial is the only one of the two systems that has the "strip" function. For git, you'll need to remove the bad commit(s) locally, then force-push your revised…

Our Support team can take care of this; just open a ticket with the details.

Administrators should have a "Branch permissions" item in the repo settings where you can specify all of this. It sounds like you'd just need to set permissions on "master" and "develop" so that only the administrator group (or a list of individual admins) is permitted to push or merge to those branches. Any branch not…

That's still not the right IP - it should be 131.103.20.174.You'll need to talk to your network team to see if they'll permit the traffic. Otherwise, you may be able to connect using HTTPS.

That isn't Bitbucket's IP. Is there something on your network restricting outbound SSH connections? What happens when you try this command instead? ssh -Tvvv -p 443 git@altssh.bitbucket.org

We changed the signature algorithm on our primary SSL certificate on 8 May: Bitbucket’s SSL certificate is changing for SHA-2 The link you posted does look like a good explanation; the newer certificate uses SHA256 for message digest, but some older OpenSSL versions may not support that algorithm. What version of OpenSSL…

That is the correct fingerprint, in both cases, for the RSA key we use for SSH. You can confirm this at https://confluence.atlassian.com/bitbucket/use-the-ssh-protocol-with-bitbucket-cloud-221449711.html#UsetheSSHprotocolwithBitbucketCloud-KnownhostorBitbucket'spublickeyfingerprints

Bitbucket Cloud's primary storage is located in the United States of America. All repositories are kept there.

You can name multiple reviewers in a pull request without any special configuration.

That document is for Bitbucket Server, which is the self-hosted version. You've tagged this for Bitbucket Cloud, which is bitbucket.org. Are you looking in the right set of documentation?

Our current datacenters are in Virginia and California.

Bitbucket Cloud calls it "main branch", since new Mercurial repos have "default" instead of "master".

Bitbucket is not hosted in Australia; it's hosted entirely in the U.S.

With Apache as the front-end, you could also have JIRA proxied to 127.0.0.101:8080, Confluence to 127.0.0.102:8080, and so on. The Tomcat containers would need to be configured to listen on those local IPs, but that'd isolate the bare container from the routable network.

I don't want to say we'll never support self-signed certificates, but it isn't very likely - especially now that Let's Encrypt is getting under way.

We do not currently support self-signed certificates for webhooks.

Sorry, the output looked like you'd specified "ssh -vT geekery@bitbucket.org".Either way, though, the key works fine here - otherwise you wouldn't get the "Authentication succeeded (publickey)" message. Are you getting a specific error from Composer?

The key worked fine here, but you don't need to specify your Bitbucket username in SSH connection attempts. Instead, use "git" as the username when connecting to a Git repo over SSH, and use "hg" as the username for Mercurial repos.

Definitely check that you've added the key to your Bitbucket account, as Daniel suggested. You should also check "ssh-add -l" and confirm that the agent is running and knows your key.

Looks like a problem either with your SSH agent (not running or doesn't know that key) or with your Bitbucket account config (if you don't have that key associated with your account). Which OS, and what do you get for "ssh -T git@bitbucket.org"?

Have you uploaded your public key? https://confluence.atlassian.com/pages/viewpage.action?pageId=302811860

We don't have any mechanisms for users to update their own newsfeed manually - the newsfeed is meant to show a user's or repo's most recent events, even if it's been a long time since those events happened. You can update the newsfeed by doing new things, though.

Did you specify that one group in the "limit pushes" field?