We are using/testing BitBucket Server and have it working fine with SourceTree on two separate computers. Unfortunately, clicking on the "Remote" button opens up a dead link. Even though I have it set up correctly in Repository Settings:
When clicking on the Remote button (top right of Sourcetree), I get this:
I am having the same issue, with generic host set, clicking the remote button sends me to https://ba-bit.web.boeing.com/bahd/linter-setup which is a 404 link and if I set it to my bitbucket server account, clicking the button just sends me to https://www.google.com/. The correct link/ what I wish it would send me to would be https://ba-bit.web.boeing.com/projects/BAHD/repos/linter-setup/browse
I am on Sourcetree version 18.104.22.168 and bitbucket v6.6.3
Any ideas on how to fix this?
@Brandon Valley Is your account options having the right settings? Not sure if this could be the problem.
FWIW I am on Sourcetree version 3.4.5 and bitbucket v7.7.1 but also "Git repository for enterprise teams powered by Atlassian Bitbucket" so the later may affect the behavior. For my personal account host is set to what would be ba-bit.web.boeing.com for you. I use HTTPS protocol which match my account setting. Other people here use SSH but I don't know their account settings.
After a bit of playing around, I think I have found a consistent way of makeing repos cloned with https work, but not ssh, if I set the remote to look like this:
it will give the red exclamation mark on the remote button but it will work, but this does not work if the origin is ssh.
Any idea how to make the remote button work with ssh origins?
As mentioned earlier my fix was to change away from Generic Account to Personal Account. But I have one repository that works with the Generic Account, there the difference to you screen dump is:
Host Type = Bitbucket Server
Host Root URL = https://<our domain>
Username = <my initials>
<our domain> correspond to: ba-bit.web.boeing.com
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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