Hi @randhirpanda,
We have been able to reproduce this issue you are reporting. We are not sure why it is happening yet, but we believe it could be related to the Erlang version, so a fix on our side would involve upgrading this component.
However, since the Erlang update could take some time and require changes on your side, we recommend you follow two possible options:
- Disable HTTPS temporarily, if you want to use Chrome in Nginx.
- Use a front-end server, such as Apache or Nginx, acting as a proxy server to CouchDB. We have added some instructions for this below.
If you want to use a proxy server, we have created a small guide for you in order to use HTTPS via Apache:
- Disable HTTPS on CouchDB, and restart CouchDB servers.
- Install LAMP stack from https://bitnami.com/stack/lamp/installer. You don't need to select any component as we are only interested in Apache. Also, the port numbers are not relevant because we're going to change the SSL port to CouchDB's port (6984, note that this port must be available for the installer). Run the installer with the option "
--apache_server_ssl_port 6984".
- In order to disable MySQL and PHP FPM, just rename the
ctl.sh file in INSTALLDIR/mysql to ctl.sh.disabled.
- Open the following file in your text editor: "
INSTALLDIR/apache2/conf/bitnami/bitnami.conf".
-
Modify the file as explained below:
Right after the line:
<VirtualHost _default_:6984>
Add the following lines:
ProxyPass / http://localhost:5984/
ProxyPassReverse / http://localhost:5984/
Restart Apache: "INSTALLDIR/ctlscript.sh restart"
The certificates must be configured in the same bitnami.conf file we mentioned above. After applying that configuration, I was able to get CouchDB working via HTTPS on Chrome.
We will look into the CouchDB issue, however, the fix for the CouchDB stack can take some time, so we recommend you apply any of the options we mentioned above (preferently using Apache as a proxy server).
Please let us know if you have any questions, or if you found any issues.
Best regards,
Marcos
