Source Tree Windows - Can't login to Bitbucket - HTTPS Error

[Linda Kruse]

Hi,

I tried to hook up a friend to our bitbucket account and install him Source Tree on Windows 8,

to manage the repository.

Installing worked fine. When I'm running the installation guide, I get the following massive error message, that something went wrong.

If I skip the installation guide, and try to clone a git repository, I get the same message but I can locate it somewhere in the area of HTTPS request error.

Has anybody an idea what the problem could be.

We tried the correct username + passwort combination.

It works on bitbucket.org.

It's connected to the internet.

Thanks for your help.

Best,
Linda

[Simon Riedel · Accepted solution]

Dear Linda,

shame on me. I have deleted one char from password and retried-> failed again.

But have not recognized the still existing § character in the pw. Removed it, now it works!

Problem solved, it was about a special character in password.

Thanks.

[Linda Kruse]

Hey Simon,

have you tried a password as simple as "password", to make sure it is not the problem,

with on of the special chars?

You can then of course use a save password afterwards.

Cheers,
Linda

[Simon Riedel]

I have the exactly same issue, password is ok with special characters.

No chance to reveal the whole text of the error message:

• The window is larger than my monitors heigth
• The window is smaller than text, so some parts are cropped
• The window is fixed in size, can not be resized
• Right click to see source not possible

Any further Ideas?

[Linda Kruse]

Hey Seth,

thanks for your answer. As I'm usually on a Mac I don't know where logs are on Windows.

Anyways, the problems could be solved by using a different password.

Apparently the old password used special characters, which destroyed the login process command.

Stupid!

So, different password, all good.

Cheers,

Linda

[Linda Kruse]

Hey Seth,

thanks for your answer. As I'm usually on a Mac I don't know where logs are on Windows.

Anyways, the problems could be solved by using a different password.

Apparently the old password used special characters, which destroyed the login process command.

Stupid!

So, different password, all good.

Cheers,

Linda

[Seth]

Unfortunately, the HTML being dumped into that window is so long that we can't actually see the error message, because it is off the bottom of the screen.

I can't recall or find the location of SourceTree logs, but if you can find and post those, it would be helpful.