jredmond Atlassian Team

Does your Jenkins system permit inbound requests from Bitbucket's IPs?

Why did you black out the Bitbucket IP?

The message says it's a timeout - that system is unable to connect to bitbucket.org. Can you get to Bitbucket through a browser there? Is there a proxy you need to configure?

That URL just provides a list of repositories. You need to click on the repo itself (or the repos themselves) to get a link that Sourcetree and GitHub can both understand.

Can you provide any more information here?

What version of TortoiseHg?

Bitbucket Pipelines is only available on Bitbucket Cloud.

Are you able to get to the repo in a browser?

"handshake_failure" suggests that you're unable to connect over HTTPS due to the recent TLS version changes on Bitbucket (https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01). Eclipse relies on its Java runtime to handle those connections, so you'll either need to update Java, switch to SSH for your repos, or…

No, the key has not changed, so that fingerprint is invalid. Are you connecting through a proxy?

bitbucket.org is Bitbucket Cloud - there's no external version number there like there is for Bitbucket Server. Your SSL/TLS library appears to be outdated, though you don't mention here what you're using or which version. curl --version should mention it, though.

What operating system, client, and client version are you using?

You're using a no-longer-supported version of TLS to connect to Bitbucket. (As of 1 December we do not support HTTPS connections using TLS 1.0 or TLS 1.1; we announced this in https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01 which was all over Bitbucket.) What client are you using, and what version?

Does that one repository use HTTPS, and all the others use SSH?

It'll be $5 per user per month at the premium level, or $2 per user per month at the standard level. ($25 is the mimimum monthly charge for premium; for standard, the minimum monthly charge is $10.) Either plan lets you have more than five users.

The free plan is limited to 5 users. There is no such limit on the other two plans - as long as you pay the $2 or $5 per user per month, then you can have as many users as you like. I'll talk to the team that maintains that page; we might be able to find better phrasing for it.

No, the IP that you get when you attempt to connect to bitbucket.org.

You wouldn't see "invalid username or password" if you were unable to connect due to TLS issues. What client are you using?

Where do you see this? Can you attach a screenshot?

You're attempting to connect with an old version of TLS. As of December 1, we've discontinued support for TLSv1.0 and TLSv1.1: https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01

What IP do you get for bitbucket.org?

Have you looked at https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01 ?

You should read the blog post that we've been telling you to read: https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01 And then you should update your client libraries.

Do you have an entry in /etc/hosts for bitbucket.org? That IP (104.192.143.3) has not been valid in several months.

This is because of https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01 . What operating system and client are you trying to use?

Your git ls-remote output mentions an RSA key and AES128-CBC-SHA, but your openssl s_client output mentions ECDSA and AES128-GCM-SHA256 (and TLSv1.2). It looks like something in git or in cURL is linked to a different library version, or it's been configured to specify a cipher suite, or possibly both. (OpenSSL appears to…

There's an "open raw" option in the source view for each file in the repo: That will give you the raw file, without the additional HTML content you'd see in a browser. You can see an example of it at https://bitbucket.org/mirror/linux/raw/master/Makefile or…

That's a great suggestion, but I think it might be a bit too late to make that change for this particular maintenance event (which happens in just a few hours). I'll add it to the guidelines for anything similar in the future, though.

We're showing it to everybody. It's overkill in some cases, but we wanted to be sure people checked all of their systems (including, but not limited to, their other workstations; their CI/CD systems; and their Jira Server instances).

You might, if your git/hg client uses HTTPS to communicate with Bitbucket. Have you tried the diagnostics from the blog post? Microsoft has also published a patch for Windows 7 SP1 (available through Windows Update) which enables newer versions of…