Users are able to clone using SSH without any issues, but attempts to clone using HTTP result in a 'Error: fatal: Authentication failed'
I'm not sure if a previous colleague may have been attempting to set up HTTPS but failed, and has corrupted a configuration file - however I'm not sure where to start
Where I usually start for tracking down these types of issues is to see if there's something perhaps on a reverse proxy between you and Bitbucket that could be causing some kind of interference - as well as checking the debug/trace logs from the git client performing the clone.
For the proxy piece, I recommend going through our steps on bypassing the reverse proxy and testing a clone that way. And then for checking the debug logs on both Bitbucket/the git client you could do something akin to the following:
Enabling Debug logging & Generating a Support Zip in Bitbucket
Enabling Git trace logging
With those two resources, the server logs and the git client logs, you should be able to analyze their contents to hopefully discern the reason for these users failing authentication. If I had to guess, though, there's possibly some kind of global/cached git credentials on the git client for these users that are automatically authenticating with the incorrect set of credentials. You should be able to see these auth failures in the audit logs on your instance though.
Hope this helps!
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events