jredmond Atlassian Team

I have the same questions for you - are the messages making it to your mail server?

Can you confirm that the messages are getting to your mail server? Are they being filtered as spam, or delivered to a folder other than the inbox, or otherwise not going where you were expecting to see them?

You need to contact Bitbucket Support.

You first need to remove the access key from any repository where it is installed. Once that is done, add the key to your user account (as displayed in the first image above).

First, change "Bitbucket Server" to "Atlassian account". If your repos are at bitbucket.org then you are not using Bitbucket Server (bitbucket.org is Bitbucket Cloud). Bitbucket Server is self-hosted and has a URL other than bitbucket.org. Once you've changed from "Bitbucket Server" to "Atlassian account" then you should…

The Bitbucket Server screen is incorrect if you're using Bitbucket Cloud, so you'll need to click "Back" and choose the Atlassian account type instead.

Don't use the "Bitbucket Server" type - bitbucket.org is Bitbucket Cloud, which uses Atlassian Account.

Is there a reason you can't use SSH?

Webhooks are just the notification mechanism. What are you trying to have your system do once it's notified - just a `git pull`?

You can make the repository private - only the people with read access will be able to see that private repositories even exist.

Are you providing a username in the prompt?

Pipelines are meant to be non-interactive, so it won't give you a prompt. You'll need either to use SSH keys for authentication, or provide the relevant password as an environment variable.

TortoiseGit is not asking about the host server's git executable - it's asking about the git executable on the client system where you're installing TortoiseGit.

DSA keys list themselves as "ssh-dss", so that isn't the issue here. However, the key length may be incompatible - Bitbucket limits DSA keys to 1024 bits, and will reject other sizes. (RSA keys can be 2048 bits or more; ECDSA keys can be 256, 384, or 521 bits; and Ed25519 keys are always 256 bits.)

It looks like you have a typo - it (probably) should be "origin", not "orign". That said, you can see whether Bitbucket is having trouble at status.bitbucket.org .

What's the destination server's URL? (The filesystem path is only relevant on that server.)

Two easy ways to do this: 1. Set up a webhook listener on the production server that will pull new code; set up a webhook on Bitbucket that will notify the listener. (Documentation: https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html ) 2. Deploy with Bitbucket Pipelines. As a bonus, this will also let…

DigiCert uses intermediate keys to sign CSRs, and they'll usually send the corrrsponding intermediate certificate(s) back with the new cert. Did you receive that, either on its own or in a bundle with your certificate?

That is a strange request, and unfortunately it isn't really one that's easy to fulfill. Bitbucket Cloud changes all the time, in multiple ways and for all users on the platform. This is part of the nature of cloud-based services. That said, the "compliance" feature in the repo admin panel restricts a lot of the variations…

You've tagged this with "bitbucket-cloud" and "cloud", so I'm going to assume that you're using Bitbucket Cloud (bitbucket.org) instead of Bitbucket Server (the on-premise version, which has a different URL). If that is correct, and all your repos are stored on bitbucket.org, then it should be enough to tell them that you…

It isn't precisely that you need sudo; you need the development libraries for cURL, but if you don't have sudo access to the box then you can't install curl-devel or libcurl4-openssl-dev or whatever the package is for that system. If you can't install the right libraries, then you won't be able to clone or push or pull…

It's "bad request": https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400 Something about the webhook is invalid, as far as the receiving server is concerned. It could be syntax, or it could be missing some expected content, or it could be that the listener does not accept POSTs, or it could be something else.…

Yes - that's a fork. https://confluence.atlassian.com/bitbucket/forking-a-repository-221449527.html

The "Host" line (not HostName, just Host) needs to match the remote URL, otherwise the SSH client won't use that stanza. You'll either need to adjust your remote URLs to be that value ("user-Bitbucket:owner/repo.git") or change ~/.ssh/config to have "Host bitbucket.org" instead of what it has now.

Sierra or High Sierra? This is a remarkably common problem that users of those two specific revisions of macOS have, due to changes in the OS's handling of SSH identities. I suspect that most of the "related content" linked here is this exact issue. Go to the Terminal and run `ssh-add -l` - your key should be listed there.…

Bitbucket Cloud or Bitbucket Server?

Are you asking a question about Firefox? This is a site for community support for Atlassian products, such as Bitbucket and Jira, so we won't be able to help much there. If your question is about Bitbucket (etc.), though, then could you please explain what the problem is?

You can search in repos. In BB Cloud, click the magnifying glass icon to the left; in BB Server, use the search box at the top.

If you have the private key associated with the public key that you're trying to add, run this: ssh -i /path/to/key -T git@bitbucket.org It should respond with something like this: logged in as [whichever user is already using that key]. You can use git or hg to connect to Bitbucket. Shell access is disabled.

Are you using Bitbucket Server or Bitbucket Cloud? This API is just for BB Server; there is no corresponding endpoint for BB Cloud.