• February 6, 2023

Sourcetree Received Http Code 407 From Proxy After Connect

Sourcetree Proxy Configuration - HTTP 407 Error - Atlassian ...

Sourcetree Proxy Configuration – HTTP 407 Error – Atlassian …

I am attempting to configure Sourcetree from behind my proxy. I am using v 2. 5. 0I am getting:Command: git -c emonicprefix=false -c core. quotepath=false ls-remote <>Output:Error: fatal: unable to access ‘<>’: Received HTTP code 407 from proxy after CONNECTNote, I have configured the proxy settings in Options > Network. I have also entered the username and password. I am using the system GIT. I can run the clone successfully from the command line when I set the proxy via: git config –global <>:<>@<>:9090I also believe that Sourcetree is not setting the username/password correctly, as when I run git config –global –get get:Note, the username and password details are not you advise how I should configure my proxy from Sourcetree? Thanks
git returns http error 407 from proxy after CONNECT - Stack ...

git returns http error 407 from proxy after CONNECT – Stack …

I have a problem while connecting to github from my PC, using git. System Win 7.
I have connection through proxy, so i specified it in git config files (both in general git folder, and in git repo folder). To do this i entered next line to my git bush:
$ git config –global :@: The way it works on other programms (ex: maven) it looks like that:
– my login to our corp system
-my password to corporat system – 10. 65. 64. 77 – 3128
But when i try to push or to clone my repo, i receive
fatal: unable to access ‘‘ Received HTTP code 407 from proxy after CONNECT
I try already to enter not just my username but domainusername, changed my password in case there are problems with code language tables. And i even entered wrong password. Error stayed the same.
When i entered in ” and tried to push repo, i received:
fatal: unable to access ‘‘: Failed connect to; No error
Just don’t know what to try.
asked Jul 23 ’14 at 9:45
2
What worked for me is something similar to what rohitmohta is proposing; in regular DOS command prompt (not on git bash):
first
git config –global username:[email protected]:proxiPort
and in some cases also
then
git config –global lVerify false
(I confirm it’s necessary: if set to true getting “SSL certificate problem: unable to get local issuer certificate” error)
in my case, no need of defining all_proxy variable
and finally
git clone
answered Apr 23 ’15 at 8:49
5
Maybe you are already using the system proxy setting – in this case unset all git proxies will work:
git config –global –unset
Matt21. 9k14 gold badges102 silver badges156 bronze badges
answered Feb 10 ’16 at 11:36
rekinyzrekinyz6, 0692 gold badges25 silver badges28 bronze badges
7
I had to setup all 4 things in. gitconfig with:
git config –global user:[email protected]:port
Only then the cloning was successful.
answered Dec 14 ’15 at 1:03
3
I had faced similar issue, behind corporate firewall. Did the following, and able to clone repository using git shell from my system running Windows 7 SP1.
Set ‘all_proxy’ environment variable for your user. Required by curl.
export all_proxy=DOMAIN
Set ‘_proxy’ environment variable for your user. Required by curl.
export _proxy=DOMAIN
I am not sure if this has any impact. But I did this and it worked:
git config –global lverify false
Use for cloning
Note-1: Do not use. Using that can give the below error. It can be resolved by using.
error: RPC failed; result=56, HTTP code = 301
Note-2: Avoid having @ in your password. Can use $ though.
answered Sep 23 ’14 at 10:59
rohitmohtarohitmohta85111 silver badges19 bronze badges
4
I had the same problem in a Windows environment.
I just resolved with NTLM-APS (a Windows NT authentication proxy server)
Configure your NTML proxy and set Git to it:
git config –global :@localhost: answered Sep 15 ’14 at 17:31
pineipinei1, 7411 gold badge20 silver badges24 bronze badges
Had the 407 error from Android Studio. Tried adding the proxy, but nothing happened. Found out that it was related to company certificate, so I exported the one from my browser and added it to Git.
Export From Web Browser
Internet Options > Content > Certificates > Export (Follow wizard, I chose format “Base 64 encoded X. 509())
In Git Bash
git config –global lCAInfo c:UtilitiesCertificatesmy_certificate
The following page was useful
To add the proxy, like the other threads I used
git config –global
answered Nov 16 ’16 at 13:06
beaumondobeaumondo4, 4577 gold badges26 silver badges39 bronze badges
1
I was facing the same issue, so firstly i checked my npm file what i have set, i checked it with this command:-
npm config get proxy
and i find out i have set wrong proxy and i set my desire proxy as follow:
npm config set proxy
npm config set -proxy
After that it works to me
answered Dec 1 ’16 at 14:50
I had the same problem too, and tried to solve it by setting explicitly the oxyAuthMethod to basic.
After running a pcap trace between my server and the proxy, i noticed that the ”
HTTP CONNECT” request sent to the proxy during a git clone still not have a “Proxy-Authorization” header set to basic. This was due to my git version “1. 8. 3. 1” that do not support oxyAuthMethod.
After installing a newest git version (2. 16. 6), using rpm packages foud here “, setting oxyAuthMethod to basic had finally an effect on git behavior and then my git clone was successful.
I hope this helps
answered Apr 22 ’20 at 15:24
FYI for everyone’s information
This would have been an appropriate solution to resolve the following error
Received HTTP code 407 from proxy after CONNECT
So the following commands should be necessary
git config –global oxyAuthMethod ‘basic’
git config –global user:[email protected]:port
Which would generate the following config
$ cat ~/. gitconfig
[]
proxy = user:[email protected]:port
proxyAuthMethod = basic
answered Jul 13 ’20 at 1:46
I think you should focus your efforts after you get to this point:
This means that you have not properly authenticated with the proxy. Can you double check the password you provide in this step is correct?
git config –global :@: answered Nov 17 ’14 at 11:37
SlakSlak5338 silver badges12 bronze badges
Your password seems to be incorrect. Recheck your credentials.
Kevin Katzke2, 9853 gold badges31 silver badges43 bronze badges
answered Sep 8 ’16 at 8:11
0
I had the similar issue and I resolved with below steps:
** Add proxy details in git**
answered Jun 29 ’17 at 17:00
I had same problem in my organization.
After many attempts, I came to the following solution:
I applied to the system administrator to change the proxy authentication type from Kerberos to NTLM. I’m not sure if it was mandatory (I’m an ignoramus in this matter), but my application was approved.
After that I add Git setting
git config –global oxyauthmethod ntlm
Only after that I was able to clone my repository
answered May 10 ’18 at 11:00
Removing “@” from password worked for me
and in anyways never keep @ in your password
it will give you issue with maven and further installation
answered Aug 13 ’20 at 12:01
CodieeCodiee2, 6852 gold badges14 silver badges17 bronze badges
This issue occured a few days ago with my Bitbucket repositories. I was able to fix it by setting the remote url to rather than.
I also tried setting proxies in the command line and git config but this didn’t work.
$ git pull
fatal: unable to access ”: Received HTTP code 407 from proxy after CONNECT
Note that we are using:
$ git remote -v
origin (fetch)
origin (push)
Replace url with url:
$ git remote set-url origin
Username for ”: username
Password for ”:
remote: Counting objects: 43, done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 43 (delta 31), reused 0 (delta 0)
Unpacking objects: 100% (43/43), done.
From a41eb87.. ead1a92 master -> origin/master
First, rewinding head to replay your work on top of it…
Fast-forwarded master to ead1a920caf60dd11e4d1a021157d3b9854a9374.
d
answered Oct 30 ’15 at 0:12
I experienced this error due to my corporate network using one proxy while on premise, and a second (completely different) proxy when VPN’d from the outside. I was originally configured for the on-premise proxy, received the error, and then had to update my config to use the alternate, off-prem, proxy when working elsewhere.
answered Aug 3 ’17 at 19:03
ShawnShawn1, 8192 gold badges20 silver badges36 bronze badges
This config works in my setup:
proxy =
[] proxy =
sslVerify = false
[credential]
helper = wincred
answered Nov 26 ’19 at 11:42
meolmeol87910 silver badges7 bronze badges
Have the same problem while using sourcetree
Reason was Maybe switching the System Proxy from on to off while sourcetree was open.
For some reason this was written into the config file of a project.
This can be easily deleted over sourcetree by “Settings” -> “Edit configuration file”.
Just delete it out there under
answered Dec 17 ’19 at 8:21
I encountered the same issue when using Git Bash. When I did the same thing in Command Prompt it worked perfectly.
answered Feb 11 ’20 at 13:57
I tried all of the solutions but none of them worked. Then I saw my. gitconfig file. It had multiple repeated entries and some of them were not correct(As I had tried multiple solutions). Finally I removed all the redundant and non needed settings and just kept the four settings mentioned by Sairam Kukadala, in his answer above, and Voila! it worked.
answered Jun 4 at 18:21
I saw this error when working on a corporate machine on Windows 10 that was not using a proxy.
From the Start menu, I had to open Settings > Network & Internet > Proxy and disable “Automatically detect settings”. After doing this, GitHub was immediately able to clone the desired repo.
This may not help anyone else, but it worked for me when nothing else did.
answered Sep 28 at 16:21
Not the answer you’re looking for? Browse other questions tagged git github proxy or ask your own question.
Can't Clone Git Respository in SourceTree: Failed to connect ...

Can’t Clone Git Respository in SourceTree: Failed to connect …

Skip to content
While attempting to clone a Git based repository in Stash via the SourceTree client, I received the following error:
fatal: unable to access ‘[email protected]:443/’: Failed connect to; No error
No error obviously doesn’t give many clues, however this post suggested something to do with proxy settings.
My web browsers were configured to use an internal web proxy via an automatic configuration script and I could successfully navigate to the repository via a web browser. My SourceTree client appeared to be configured correctly since it was set to use the same proxy settings:
The aforementioned post suggested that it was actually the Git command line tools which also need to be configured to use a proxy and the handy checkbox Add proxy server configuration to Git / Mercurial does that for you.
I configured that setting and lo and behold could then clone the repository.

Frequently Asked Questions about sourcetree received http code 407 from proxy after connect

Leave a Reply

Your email address will not be published. Required fields are marked *