Authentication OK but OAuth/App Password don't work to clone (This is not a valid source path/URL)

[Jeffrey Gage]

I am using SourceTree 3.4.19.0 with a Bitbucket Cloud setup (bitbucket.org).

I am getting the following error when I try to clone.

This is what else I have tried and see. Everything for my account validates on installation. It logs me in to Bitbucket through Sourcetree. When I get to the main screen (remote tab) I can see every repo under our company. When I edit user to see the credentials, I have "Authentication OK"

Everything looks perfect until I try to clone. Then I get "This is not a valid source path / URL" and the expanded error message above.

I know everything is set up right server side, as none of my coworkers have this problem, and my old computer does not have this problem, using OAuth with that popup that refreshes the key for you.

I have also tried changing to basic authorization with an App password according to a zillion answers online. It technically works and says "Authentication OK" and will still not clone. Please do not recommend this app password solution to me, it works fine with OAuth on other computers and with this one.

I have also

1. Restarted my computer

2. Restarted SourceTree

3. Uninstalled and reinstalled source tree

4. Deleted all the bitbucket credentials in Microsoft Credential Manager

5. Poked around in every credential setting in SourceTree (Authentication OK)

6. Verified that the settings are the same and work on my old setup (same aside from version 3.4.15.0, I am currently afraid to update old system because of this)

7. Updated Sourcetree to the latest version, currently 3.4.19.0

8. Copy the clone command directly from bitbucket in case something weird happened

9. Tried cloning multiple repos in case it was just the one

10. Made sure my BitBucket permissions are correct. (I am admin with project access, works on old machine, and it is also the same account)

Maybe there's a problem with being logged on to two different computers at once but I wouldn't see why.

Additional info (which works fine on old setup), I also have downloaded git and tortoise git for some legacy systems I use. That should not interfere.

Thanks for the help.

[Jeffrey Gage · Accepted solution]

Ok, I have found an answer! 

I found this in the menu.

My system installation of git worked when I switched from "Embedded" to "System".

Then, I clicked "Update Embedded" and then switched back to embedded, and after that, when I tried to clone, there was a pop up that I had handled incorrectly the first time.

Oops that was dumb. There was a popup that asked how you want to manage credentials. I had incorrectly clicked "no manager" instead of "manager".

So SourceTree was fine, just git itself couldn't provide credentials since there was no credential manager. Hope this helps somebody at some point!