jredmond Atlassian Team

Have you read the linked post?

I answered elsewhere, but both GCM and SHA-256 (note: not just "SHA", needs to be either "SHA256" or "SHA384") are specific to TLSv1.2. I've also updated the blog post to mention that.

It looks like you're using a curl version that does not include the TLS version string (that was introduced in curl version 7.40.0, which was released in January 2015). Since you're able to connect to other sites using TLSv1.2, though, and since your output lists both GCM and SHA-256 (both of which are unsupported in older…

You should be OK. Curl 7.29.0 supports TLSv1.2, and NSS 3.34 provides plenty of modern algorithms. The "GCM_SHA256" part of your cipher list also suggests TLSv1.2, since both of those algorithms are not supported in previous versions of TLS. That said, your curl version is pretty old there - 7.29.0 was released in February…

Why do you need it back? The command listed there is `git clone` and then the repository URL. The source view also has a "Clone" button in the upper-right, which contains that command in full.

Curl added the TLS version output in version 7.40.0 (released January 2015). Curl versions since 7.29.0 (released February 2013) should be able to manage TLSv1.2, but that will also rely on the underlying SSL library (OpenSSL, LibreSSL, GnuTLS, etc.) that was linked into the curl binaries. I can see from your `curl…

What version of curl and libcurl? (You should be able to find both with `curl --version`.)

Yes - from the Pull Requests screen, there's an option at the top that lets you select "Open", "Merged", or "Declined".

Can you provide any more detail?

Does `ssh-add -L` list your key?

Try this from the command line: $ ssh -T -i /path/to/private_key git@bitbucket.org logged in as (username associated with that key). You can use git or hg to connect to Bitbucket. Shell access is disabled.

The error messages listed here - "empty reply", "stream not closed cleanly", and "connection closed by remote host" - all suggest that something in the network between your system and Bitbucket is preventing traffic. Are you using a proxy of some kind?

If you run `ssh -T git@bitbucket.org`, does it list your username?

You can fork the boilerplate repository.

The "security key" mentioned here is a physical device (as mentioned in the screenshot), not an app on your phone. If you have the option to add a security key then you've already set up multifactor authentication successfully using Authy (or some other app).

Does it say anything else?

What type of device is it?

What type of device is it? As the screenshot says, we currently only support hardware keys that use the FIDO U2F standard.

Either the relevant SSH key isn't associated with a user on your Bitbucket Server instance, or it's not immediately available to the SSH agent on your local system. There isn't enough detail here to really tell which is the case, but you can collect some useful information with these commands: # ssh-add -L #…

Trello already disallows TLSv1.0, but TLSv1.1 will be deprecated as well.

It affects all HTTPS traffic on any Atlassian-hosted product. Your Bitbucket Server instance won't be directly affected, but its link to Jira Cloud uses HTTPS and will therefore be affected by this change.

That's there for CI/CD systems to connect. It isn't going away any time soon.

Access keys are read-only, by design. If you want to be able to write then you need to add the key to your account.

"Connection refused" implies that a firewall or proxy or other process is preventing your client from reaching Bitbucket in the first place. It's possible that there's something in WSL doing that, or something in Windows itself doing that. I can't really help with the specific details of Windows or WSL networking, but try…

Are you sure you have the right address? The message in the title refers to "bitbuckeR.org" instead of "bitbuckeT.org" (emphasis mine).

Take the key out of the repository and add it to your account.

I see two things in the screenshot which may contribute: 1. You're giving Netbeans an SSH URL, but a username and password. Bitbucket SSH does not work with username and password. 2. You're giving Netbeans a Mercurial repository URL, but Netbeans is expecting Git.

repository access denied. access via a deployment key is read-only. You've added the key to the repository. Take it out of there and add it to your account.

You can add the key to any individual account, but first you must remove it from any repositories where you've added it.

1. Take the key out of that repository, or those repositories. 2. Add it to your Bitbucket account instead.