Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BBE6D200B6B for ; Thu, 25 Aug 2016 12:15:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BA72D160A94; Thu, 25 Aug 2016 10:15:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0C35C160A93 for ; Thu, 25 Aug 2016 12:15:30 +0200 (CEST) Received: (qmail 16673 invoked by uid 500); 25 Aug 2016 10:15:30 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 16658 invoked by uid 99); 25 Aug 2016 10:15:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2016 10:15:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 44A38C0317 for ; Thu, 25 Aug 2016 10:15:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.553 X-Spam-Level: X-Spam-Status: No, score=0.553 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id JvMemsBxGISS for ; Thu, 25 Aug 2016 10:15:28 +0000 (UTC) Received: from BAY004-OMC3S20.hotmail.com (bay004-omc3s20.hotmail.com [65.54.190.158]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id CA7305F30C for ; Thu, 25 Aug 2016 10:15:27 +0000 (UTC) Received: from BAY174-W27 ([65.54.190.189]) by BAY004-OMC3S20.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 25 Aug 2016 03:15:21 -0700 X-TMN: [+325jhvv63BeXU0zipOk08BOnZrVsQwI] X-Originating-Email: [csharpdeveloper@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_e506c0ff-5b2e-48b9-859d-0d8a192b16b2_" From: Joey Samonte To: "dev@couchdb.apache.org" Subject: RE: Can clustering be setup between nodes that only accept SSL connections? Date: Thu, 25 Aug 2016 10:15:21 +0000 Importance: Normal In-Reply-To: <4239B8C7-ED3F-4A27-A56E-539ED3FD2C6D@apache.org> References: ,<4239B8C7-ED3F-4A27-A56E-539ED3FD2C6D@apache.org> MIME-Version: 1.0 X-OriginalArrivalTime: 25 Aug 2016 10:15:21.0936 (UTC) FILETIME=[96975500:01D1FEB9] archived-at: Thu, 25 Aug 2016 10:15:31 -0000 --_e506c0ff-5b2e-48b9-859d-0d8a192b16b2_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We are currently using nginx sir as reverse proxy in front of CouchDB =20 > From: rnewson@apache.org > Subject: Re: Can clustering be setup between nodes that only accept SSL c= onnections? > Date: Thu=2C 25 Aug 2016 11:07:29 +0100 > To: dev@couchdb.apache.org >=20 > Yes=2C couchdb can be configured that way but my recommendation is to put= something like haproxy in front instead. The native ssl support in Erlang = has a buggy history in my experience=2C though I believe 18.x is working qu= ite nicely. Further=2C with couchdb 2.0=2C you'll want a round-robin loss b= alancer in front of them to fully enjoy the clustered fault tolerance.=20 >=20 > For < 2.0=2C you just need to configure the httpsd daemon and comment out= the httpsd one. For 2.0=2C I'll have to research a little as I'm not sure = the chttpd service is as rainy disabled.=20 >=20 > Sent from my iPhone >=20 > > On 24 Aug 2016=2C at 21:08=2C Joey Samonte wrote: > >=20 > > Good day=2C > >=20 > > SSL is a must for us to secure our data. Can the CouchDB nodes in the c= luster only allow https=2C for example=2C on port 6984? > > =20 >=20 = --_e506c0ff-5b2e-48b9-859d-0d8a192b16b2_--