I have created a public repository on bit bucket website. I can run the clone command from outside the office network (LAN).
But it is not working inside the office network. I am suspecting it is to do with firewall or proxy settings. I can access the URL from browser window (IE9/Chrome).
Please help in fixing this problem. Thanks.
Command:
hg clone https://bitbucket.org/gbsandeep/test2
abort: error: getaddrinfo failed
PS: I went through other posts but it did not help.
Sounds like you might need to tell Mercurial what your proxy settings are. First hit for "mercurial proxy":
http://www.markhneedham.com/blog/2009/05/13/mercurial-pulling-from-behind-a-proxy/
If you need to figure out what settings to use, you should probably look at what your IE settings are, e.g. by going to the Internet Properties | Connections | LAN Settings dialog.
If you find yourself on this page because you've hit a getaddr error when using the hg-git plugin with a username, it is likely that you've hit the Fails with username in URL (getaddreinfo failed) bug.
Thus:
$ hg clone https://foo#stash/
abort: error: getaddrinfo failed
$ hg clone https://stash/
http authorization required for http://stash.....
realm: Atlassian Stash
user: ...
(Doesn't solve the original user's issue, but can be a cause of the same symptoms).
Just remove the http_proxy environment variable. (worked for me, after of 5 hours of headache).
Pls check whether you can access the repository directly first. e.g from web browser
For me, the solution was to set http_proxy env var.
In PyCharm mercurial clone dialog that was resolved by enabling the corporate vpn and setting up automatically detecting the proxy in Win 10. However, the PyCharm throwed some new exception like this:
6:03 PM Clone failed
Clone from your url here failed.
** Unknown exception encountered with possibly-broken third-party extension hg4ideapromptextension
** which supports versions unknown of Mercurial.
** Please disable hg4ideapromptextension and try your action again.
** If that fixes the bug please report it to the extension author.
** Python 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:53:40) [MSC v.1500 64 bit (AMD64)]
** Mercurial Distributed SCM (version 4.7.1)
** Extensions loaded: strip, mq, hg4ideapromptextension
Traceback (most recent call last):
File "hg", line 41, in
Related
I made a repository by VisualSVN in Windows Server 2012 R2.
After made the repository, I checkout the repository on Windows using TortoiseSVN and it worked.
However, when I checkout Mac mini device, an error occured.
svn checkout https://win-h3asdfasdf/svn/asdfasdf --username asdfasdf --password asdfasdf
svn: E170013: Unable to connecto to a repository at URL 'https://win-h3asdfasdf/svn/asdfasdf'
svn: E670008: nodename nor servname provided, or not known
Please let me know how can I fix it.
Guess, you already don't need an answer, but I faced the same error and got the solution. So I'll share it anyway:
The error says that the URL is wrong, and you probably get this link when you click on the "Checkout" button, so to avoid this error you should write the full name of the address like you get this link when you click on the button:
https://win-h3asdfasdf/svn/asdfasdf
, then you should add to it its full name:
https://win-h3asdfasdf.organization.com/svn/asdfasdf
During checkout:
svn.exe checkout https://IPv4:40443/svn/project
An error occurs:
svn: E720006: Error running context: Nieprawidłowe dojście.
It's in polish language and it could be translated as (I hope):
...context: the handle is invalid
Is this error related with network connection or any Windows IO restriction?
I'm working on Windows 7, which is very restricted by administrator. So here everything could be blocked or limited.
The same checkout from "normal" computer works great. So where to search for problem? Disk? Network settings?
I've gone through almost everything related to installing sbt on Window on stackoverflow (there are quite a few people having the same problem with me). However, the answer seems unclear/unreproducible on my machine.
Here is what I did:
Download sbt-0.13.13 on this site
Install it successfully and set the PATH
Try sbt version to see if it is installed successfully. Error
returned (as at the end of this post)
A few things we should know:
I already have JDK
I don't use Proxy on my computer (tested with netsh winhttp show
proxy)
Someone said it is because sbt doesn't support ASCII character - but
the solution wasn't clear
problems summary
WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
local: tried
C:\Users\buidu\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy.xml
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
C:\Users\buidu\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jansi.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
UNRESOLVED DEPENDENCIES
org.fusesource.jansi#jansi;1.11: not found
Server access Error: Permission denied: connect url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Server access Error: Permission denied: connect url=https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Server access Error: Permission denied: connect url=https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
Server access Error: Permission denied: connect url=https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
You could try to configure the use of IPV4 (not IPV6), as described in the accepted answer for this question:
Error while importing sbt project , Server Access error, unresolved dependencies
setx _JAVA_OPTIONS -Djava.net.preferIPv4Stack=true
I was struggling with the same for a week. The only thing, that helped, was to uninstall sbt from the default location (c:\Program Files(x86)\sbt) and reinstall it to some location without spaces (I've installed it to d:\sbt).
Did you try taking a look in your sbt repositories file (likely to be c:\users\.sbt\repositories, and specifying http:// instead of https:// ?
When attempting to push / pull over ssh, git is failing with the following error:
"C:\Program Files\Git\bin\git.exe" push -u --recurse-submodules=check -progress "testremote" project:project
Using username "git-receive-pack 'ec2-user".
FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Done
The remote "testremote" is setup as "ssh://ec2-user#sweeb.net:gittest.git" and I'm using an existing keypair that I have used with PuTTY before without issue.
Pageant is running, with my key loaded.
I think the issue is the line "Using username "git-receive-pack 'ec2-user"." - I assumed git's commands were breaking on windows thanks to the space in "Program Files" so I've tried to surround everything with double quotes, but that doesn't seem to be working. Has anyone seen anything like this before?
Windows vars:
GIT_SSH=C:\PuTTY\plink.exe
PATH=[...];"C:\Program Files\Git\cmd";"C:\Program Files\Git\libexec\git-core\";"C:\Program Files\Git\bin\"
This was solved by removing "ssh://", that's implicit in Git Extensions apparently.
I made my own git server on a centos distribution.
I can contact the server via git protocol at my home. But when I try to access via https at office I obtain:
Cloning into /Users/vito/Documents/... error:
error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112) while
accessing https://gitolite#myserverxyz.com/vitorepo.git/info/refs
fatal: HTTP request failed
Where is the problem? On my server or on my office-mac?
I got the exact same response from curl when trying to connect with an ubuntu instance running openssl 1.0.0e. I successfully resolved the problem by adding the -ssl3 flag to the curl command.
It seems that it's a compatibility problem between older version of OpenSSL (0.9.8) acting as a client and recent OpenSSL version (1.0.0) acting as a server with some specific options used by Curl on client side and Apache on server side.
It's probably due to some recent security fix in OpenSSL (probably the one against protocol downgrade attacks).
Try upgrading the OpenSSL library version on the client side to 1.0.0.
See:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3395520&group_id=976
In case anyone has this issue with XMLRPC.
Daniel's answer (forcing SSL version 3) solved the issue for me. just specify XMLRPC_SSLVERSION_SSLv3 in the clientXmlTransport_curl options (C++).
The problem began when we upgraded our server to OpenSSL version 1.0.1-4ubuntu5.5 and the clients were still running 0.9.8o-5ubuntu1.7.
I believe this is a host-name matching issue on the server. Error 1112 is SSL_R_TLSV1_UNRECOGNIZED_NAME, and comes from an SNI name mismatch (info on SNI). I was having the same issue in curl.
For me, the work around was to make sure the name I used on the client matched one of the ServerName or ServerAlias configurations on the server. Of course, these commands are for an apache server; I don't know what you need to do for a git server. But I suspect the server names you're using from home and work are different, and the home name is the cannonical name the git server is using (and therefore SNI is working).
The 'real' fix will probably take a client change in git to allow a way to ignore the name-mismatch warning (the way your browser already does).
Not sure if I had exactly the same problem, but the error message was the same. It only seemed to be happening on the ubuntu box I set up a git server on, for some reason the centos box with a git server set up on it was fine.
I only just solved it after 3 or 4 days. It turns out to be because git's underlying Curl library has a broken Keep-alive implementation (I ended up dumping HTTP traffic and verifying the behaviour by hand).
In a nutshell Curl (at least the version used inside every Git implementation I could find, including command line git and eclipse's EGit) doesn't seem to correctly interpret the Connection response header, or more correctly doesn't seem to correctly interpret the absence of it.
To fix the problem you need to configure the SSL virtual host inside the apache that is serving your GIT repository with an extra directive specifically for git. Add these lines just before the </VirtualHost>.
BrowserMatch "git" nokeepalive ssl-unclean-shutdown
You unfortunately can't tell apache to just downgrade to HTTP/1.0 (would be cleaner) because Curl can't handle that, but you can just tell it to force a Connection:close on every request which Curl does know how to handle.
In a misleading coincidence, if you try to test Curl directly without this change it will seem to work, because it makes a single request and then aborts. Only by getting curl to execute two requests on the same keep-alive connection over ssl will this problem become apparent.
I had the same error. The root cause seems to be incompatibility of client/server openssl versions.
I've upgraded my server with apt-get upgrade openssl and upgraded my windows git installation.
The combination of windows git client
git version 1.9.4.msysgit.0, which contains openssl version:
OpenSSL 0.9.8e 23 Feb 2007
And server with openssl version:
OpenSSL 1.0.1c 10 May 2012
seems to work fine together.