jredmond Atlassian Team

Did you add your public SSH key to your Bitbucket account?

What do you get if you use this command instead? GIT_CURL_VERBOSE=1 git push -u origin v2.3 (Feel free to strip out passwords or other secrets, but please do not remove the Bitbucket IP address that it shows.)

They're just Docker images - you should be able to create your own with standard Docker tools. Docker has some documentation at https://docs.docker.com/get-started/ to learn how to create images. There is some more detailed, Pipelines-specific, documentation…

DNS is the best approach. If your upstream DNS isn't serving the right IPs then you need to contact them, or try a different DNS provider. If you manage a local DNS cache then it may be worthwhile to update it with the new information - at least while the main IP set is blocked.

That IP is one of the ones being blocked in Russia. Unfortunately, while we can return different DNS results based on IP geolocation, we also have to rely on your ISP and nameservers to give you the "correct" result. As a temporary fix, does 18.234.32.156 work for you for bitbucket.org?

You can use the same deployment key on multiple different repositories. If you'd prefer to keep separate keys for each, though, then you'll need to use the ssh config file to set separate aliases for each: Host bitbucket-repoA Host bitbucket.org IdentityFile /path/to/first/key Host bitbucket-repoB Host bitbucket.org…

1. Remove the deployment key from whatever repository you've added it to. 2. Add that key to your own account, as instructed in the linked documentation.

Unfortunately, Tim's solution is for Bitbucket Server. For Bitbucket Cloud, however, you can use branch permissions to prevent users from deleting the branch in question.

Can you provide any more details about the server, its operating system, or what you're attempting to do with it?

The term "Bitbucket Server" (with the capital S) refers to the on-premise product by that name. You are attempting to connect to Bitbucket Cloud, which is not the same thing. Go back from that screen and select Bitbucket Cloud instead of Bitbucket Server.

What exactly does the error message say?

Can you give any more information? This just says "there is a problem" without describing the problem.

Are you asking about Bitbucket Cloud or Bitbucket Server?

How are you getting the code from Bitbucket to the App Store?

Are you asking about Bitbucket Cloud or Bitbucket Server?

You added the key to the repo, but it needs to be on your account. Remove it from the repository first, and then add it to your account under Bitbucket settings > SSH keys.

That URL is valid for cloning, pushing, or pulling with SSH. If you need the HTTPS URL for the Web version, it's https://bitbucket.org/manuelatexier/monprojetblog - and if you need the HTTPS URL for cloning/pushing/pulling then just add .git to the end.

If both are enabled then both are required.

Are you restricting traffic with an ACL? (Also, if you've hardcoded that IP someplace then you need to change it very very soon.)

You're attempting to connect via HTTPS. Change the URL in your test: git ls-remote myacct@bitbucket.org:myacct/project

Include [skip ci] or [ci skip] in the commit message. (There's a bit more detail in the FAQ.)

If you're still having this problem, please check your firewall or proxy settings - as we kept telling people through blog posts, tweets, a site banner, painfully-colored CLI messages, and other means, our IPs are changing. (We've now shifted DNS to entirely new addresses, so the old 104.192.143.x addresses will be going…

Please remove those IPs. They are being shut down soon.

Authors can always approve their own pull requests, but the author's approval doesn't count towards any minimum approval requirement. (For example, if my pull request requires two approvals, then I can still click "Approve" - but my approval won't count as one of those two required approvals.) As for preventing merges…

Are you behind a firewall? Does it need to be updated?

This should be resolved - we've added a third subnet, which is not blocked in Russia as I type this. Russian users should now get a new set of IPs from DNS. https://blog.bitbucket.org/2018/08/06/update-ip-migration/ has a bit more detail. Please note that some ISPs may cache the old IPs for a little while longer, and that…

Are you able to connect to https://bitbucket.org now? https://18.205.93.1 will not work because the bitbucket.org certificate (the certificate served at that address) does not explicitly list that IP address as a valid alternate hostname. This is intentional, and rather common for TLS certificates, as it means that the…

Your DNS server should now pick up a new, not-currently-blocked, set of IPs. Please remove the 104.192.143.1 entry from your hosts file.

Please do not ever share your private key. That makes it useless. If you're setting up an SSH key in Pipelines to push or pull code from elsewhere, then please use the built-in SSH key generator there.

The Russian block should be resolved now. If you've added that specific IP to your hosts file then you should remove it.