Heya Joel,

have you considered using a dedicated HTTP proxy in front of CouchDB to do the 
SSL handling for you?

It might be easier :)

Best
Jan
--
Professional Support for Apache CouchDB:
http://www.neighbourhood.ie/couchdb-support/

> On 19 Mar 2015, at 16:30, [email protected] wrote:
> 
> 
> Hello all,
> 
> We are really struggling with applying SSL to our CouchDB database.  We are 
> running CouchDB 1.6.1 on a Windows 7 machine.  We
> have tried to implement the solution suggested here 
> http://wiki.apache.org/couchdb/How_to_enable_SSL on multiple Windows 7
> machines with no luck.  One of my co-workers even tried on his home Linux 
> machine (not sure which distribution) and could not
> get it working.
> 
> I am confident that the certificates are good.   Our local.ini file has been 
> configured as suggested in the link previously
> mentioned.  I have restarted the CouchDB service after each configuration 
> change.  Still no luck.
> 
> Here are snippets from the local:ini file
> 
> [daemons]
> httpsd = {couch_httpd, start_link, [https]}
> 
> [ssl]
> cert_file = c:/Program\ Files\ (x86)/Apache\ Software\ 
> Foundation/CouchDB/etc/mycert.pem
> key_file = c:/Program\ Files\ (x86)/Apache\ Software\ 
> Foundation/CouchDB/etc/privkey.pem
> 
> We repeatedly receive the following error when I run "curl -k -v 
> https://127.0.0.1:6984/"; : curl: (35) schannel: failed to
> receive handshake, SSL/TLS connection failed
> 
> Has anyone else experienced this problem and found a solution?
> 
> TIA,
> 
> Joel Brewster
> 
> 
> This e-mail and any files transmitted with it are confidential and are solely 
> for the use of the addressee.  It may contain material that is legally 
> privileged, proprietary or subject to copyright belonging to Mutual of Omaha 
> Insurance Company and its affiliates, and it may be subject to protection 
> under federal or state law.  If you are not the intended recipient, you are 
> notified that any use of this material is strictly prohibited.  If you 
> received this transmission in error, please contact the sender immediately by 
> replying to this e-mail and delete the material from your system.  Mutual of 
> Omaha Insurance Company may archive e-mails, which may be accessed by 
> authorized persons and may be produced to other parties, including public 
> authorities, in compliance with applicable laws.


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to