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
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.
I am trying to access a git repository on a remote server that is on the other side of a private-2-private VPN connection using HTTPS protocol. We have no permission due to Firewall rules, therefore I want/need to use a SOCKS5 proxy.
The proxy is established like (names hidden for privacy):
ssh -N -D 8003 firstname.lastname@example.org
git configuration for proxy looks like:
My "git remote" configuration looks like
zzz https://atc.remote.net/bitbucket/scm/yyy/xxx.git (fetch)
zzz https://atc.remote.net/bitbucket/scm/yyy/xxx.git (push)
Now, the following works OK:
git fetch zzz
git push zzz
So, no problems with the proxy. But when I try
git clone https://atc.remote.net/bitbucket/scm/yyy/xxx.git
It either complains that it cannot resolve "atc.remote.net" or - after adding host and IP to /etc/hosts - it times out after a minute or so. This seems to suggest, that the clone command does not work with the proxy. Am I doing something stupid here ? Btw - the git client is version 2.31.1 on OpenSuse Tubmbleweed Linux.
Typical case of "make yourself a fool on the Internet and find the answer 5 minutes later". OK, it took a night, but still...
Solution: put the git proxy settings in the "--global" section, not on the "--local". Then "clone" will work like a charm. Thinking about it for a moment it is logical. When I "clone", there is no local git config to look at. I had put them into "--local" in order to be flexible when using several remote repositories. DOH...
Anyway, I believe the best way (for me) is for the "clone" case to specify the proxy on the command line. Something like:
git -c "http.proxy=socks5h://127.0.0.1:8003" clone https://atc.remote.net/bitbucket/scm/yyy/xxx.git
Another insight - one does not need "https.proxy".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.