"ssl required" while trying to push to https-repository
Andreas Piening
andreas.piening at rrz.uni-hamburg.de
Thu Sep 4 09:09:02 CDT 2008
Hi behlma,
tryed everything I know of, but no solution yet, sorry. If I get
anything that may help to fix or solve this problem, I'll post it to
the list.
Please can you tell me, if you use a self-signed SSL-certificate, too?
Thank you in advance,
Andreas
Am 04.09.2008 um 11:20 schrieb behlma:
>
> Hi Andreas,
> I'm having the very same problem (using Nginx instead of Apache,
> though).
> Have you found a solution yet?
>
> Furthermore, I'm running Debian Etch, with Mercurial 1.0.1.
>
>
> Andreas Piening wrote:
>>
>> Hi Benoit,
>>
>> I have removed the http-host, but it has not been accessed while I
>> was
>> trying to push: I have checked this in the access-log.
>> However, it doesn't do a change to my error.
>>
>> I'm new to mercurial and this is my first setup, but following the
>> setup-guide I have no reason for this mysterious error to occur.
>> I have no idea what could force mercurial not to use https, while the
>> web-directory is accessable with the same URL.
>>
>> Is there anything known about problems with self-signed SSL-
>> certificates with mercurial?
>>
>> Thank you in advance,
>>
>> Andreas Piening
>>
>> Am 28.08.2008 um 20:51 schrieb Benoit Boissinot:
>>
>>> On Thu, Aug 28, 2008 at 8:37 PM, Andreas Piening
>>> <andreas.piening at rrz.uni-hamburg.de> wrote:
>>>> Hi Benoit, hi mercurial list,
>>>>
>>>> I have changed the line to the value you suggested, and I get "ssl
>>>> required
>>>> (found: http)". This is very strange, since the https should be
>>>> extracted
>>>> from my default-push-url which starts with https.
>>>> Anyways, the extraction of the https from the url is not the only
>>>> problem. I
>>>> hard-coded the proto to https but then I get the stack-trace.
>>>>
>>>
>>> It's probably some apache configuration problem then :/
>>>
>>> In your first mail you said:
>>>> Since I want allways want use https for clone/pull AND push, I
>>>> created
>>>> a http-vhost which just redirects to this https-one. But I use
>>>> https
>>>> directly in my tests.
>>>
>>> Maybe it's related, try not to create any http vhost (maybe what I'm
>>> saying
>>> doesn't make sense, then ignore it :)
>>>
>>> regards,
>>>
>>> Benoit
>>
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial
>>
>>
>
> --
> View this message in context: http://www.nabble.com/%22ssl-required%22-while-trying-to-push-to-https-repository-tp19123064p19304703.html
> Sent from the Mercurial mailing list archive at Nabble.com.
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
More information about the Mercurial
mailing list