couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sinan Gabel <sinan.ga...@gmail.com>
Subject Re: CouchDB crashing with SSL
Date Thu, 28 Apr 2016 12:51:01 GMT
Sounds good, else place e.g. Nginx with SSL in front of CouchDB.

Best,
Sinan

On 28 April 2016 at 15:05, Raja <rajasaur@gmail.com> wrote:

> Upgrading to Erlang 18 solved this issue. I can successfully connect from
> my browsers as well as Couchbase Lite.
>
> On Wed, Apr 27, 2016 at 11:28 PM, Raja <rajasaur@gmail.com> wrote:
>
> > Hi
> >
> > We recently enabled SSL on CouchDB 1.6.1. Suddenly, it seems to be
> > throwing errors in the log when viewing even the main url on Futon. The
> > errors are shown in
> > https://gist.github.com/rajasaur/747ca711810c22e7780b3288c659f216
> >
> > 1. This was working till last week (http also works perfectly now).
> > 2. Doing a curl seems to make it work:
> >
> > curl -XGET  https://user:password@server:6984
> >
> > returns
> {"couchdb":"Welcome","uuid":"de859c6bd13c708e759abc283f67f3c4","version":"1.6.1","vendor":{"version":"1.6.1","name":"The
> > Apache Software Foundation"}}
> >
> > but hitting https://<server>:6984 on the browser throws the above
> > mentioned stack trace. Why would it fail using a browser but not with
> curl.
> > Doing a verbose with Curl indicated that it was negotiating using TLS 1.2
> > connection. I tried to force using --tlsv1.0, --tlsv1.1 and --tlsv1.2 to
> > curl to see if I can simulate the browser failure but it worked fine in
> all
> > cases.
> >
> > 3. Setup local.ini to have tls_version = [ 'tlsv1.2' ], but same result.
> >
> >
> > Browsing some of the older discussions suggests a upgrade of Erl (we use
> > Erlang OTP/R16B03-1). Is there anything else I should be looking before
> > going the upgrade route?
> >
> >
> > Thanks a lot for the help
> >
> > Raja
> >
>
>
>
> --
> Raja
> rajasaur at gmail.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message