Thank you Ryan for your answer, I think is before the host password (is
since weeks I had this problem so I will try from my office) with my home
network it works fine with the host password. But it's a good question
because! is the authentification the message talks about, is from the proxy
or the host? I think the message is clear it says "could not authenticate to
proxy server". Also I inform you that when I do not specify the proxy id and
password in subversion servers config file svn hangs and when I specify it
it will not hang but immediately displays the error message below.
thank you, rachid
On Sat, Jun 11, 2011 at 12:59 AM, Ryan Schmidt <
> On Jun 10, 2011, at 12:27, rachid ayad wrote:
> > Dear Subversion experts, I have really a proxy/firewall problem using svn
> to download a package I use it for research. I am listing here the error
> message after using svn to download the software from the site here below:
> > ***********
> > svn: OPTIONS of
> > 'https://ekpbelle2.physik.uni-karlsruhe.de:/trunk/tools': Could not
> > create SSL connection through proxy server: Could not authenticate to
> > proxy server: ignored Kerberos challenge, ignored NTLM challenge,
> > GSSAPI authentication error: Unspecified GSS failure. Minor code may
> > provide more information: No credentials cache found
> > (https://ekpbelle2.physik.uni-karlsruhe.de)
> > *************
> > My institute is using proxy on port 8080 and I was in contact with the
> administrator but he did not solve the problem. I set the proxy and password
> on the subversion servers config file: /etc/subversion/servers but is still
> does not work. The administrator removed all firewalls on a port (3690) so I
> > svn co https://ekpbelle2.physik.uni-karlsruhe.de:3690/trunk/tools
> > and it did not work
> I'm afraid I don't know the answer to your question, I just want to point
> out that 3690 is the default port for svnserve, so that's applicable when a
> repository is served using the svn:// protocol, which this repository is
> not: it's served with the https:// protocol, which means it by default
> uses port 443. You cannot simply pick a different port number to communicate
> with a server with, unless that server is configured to respond with the
> correct protocol on that port; this server does not appear to be configured
> to respond at all on port 3690, which is not a surprise.
> When I try "svn ls https://ekpbelle2.physik.uni-karlsruhe.de/trunk/tools"
> I first get asked if I want to accept the SSL certificate, and when I accept
> it temporarily, I'm then prompted for my username and password; when I fail
> that because I don't have one, I get "svn: OPTIONS of '
> https://ekpbelle2.physik.uni-karlsruhe.de/trunk/tools': authorization
> failed: Could not authenticate to server: rejected Basic challenge (
> https://ekpbelle2.physik.uni-karlsruhe.de)". You are presumably entering a
> valid username and password before receiving the error you mentioned above?
> Or does it show that before even asking you for a username and password?
Received on 2011-06-11 00:41:58 CEST