You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are in the process of getting a local 2019 DevOps server in place. The DevOps server is located behind our companies VPN. We've setup a SSL certificate against a named version of that server and have updated our local HOSTS file on Windows 10 to point the IP address to that named URL.
When attempting to "Add an account..." within SourceTree, we get the following errors:
When attempting to bypass this entirely by just going to "Clone", I also get similar errors:
But when I access this with the IP address instead of the <site url>, I can clone the repository. Unfortunately, in doing so, I am not authenticated.
All signs seem to point to the fact that Sourcetree is not using the Windows 10 HOSTS file. Is there any way to force this lookup between IP and named URL? We do not have an internal DNS server. I need to be able to have Sourcetree see the named URL and resolve to the internal IP.
For what its worth. the powershell command of
git clone https://<site url>/<company>/<project>/_git/<repo>
works just fine and pulls whole repo down.
I would really prefer to use SourceTree as our GIT GUI but will have to move on if I cannot get this to properly pull down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.