; enable SSL support by uncommenting the following line and supply the PEM's below.
If you want, share your modified local.ini file so we can find what could be missing (take care of hiding the secrets).
; Uncomment next line to trigger basic-auth popup on unauthorized requests.
Tell us if that was the problem. We’ll be looking forward to receiving your reply.
I've been having the exact same problems described in this thread, and I'm really glad I found it because it's been driving me crazy. Following the suggestion to add bind_address under [httpd] has made my "Connection Refused" error go away. I can also now see 0.0.0.0 listen for 6984, whereas previously it was only 127.0.0.1. Thank you!
I had this same issue. Would be great if you could update the docs to reflect the configuration.
However, we should mention it in the section How To Enable SSL (For HTTPS) On CouchDB too. I will notify you as soon as we update this piece of the documentation.
so, the instructions should read that the line needs to be ADDED instead of changed.
FYI - just making the change to the bind address under [chttpd] does allow outside access, just not https access. Adding the line to [httpd] does allow outside https access as specified, thanks for the clarification!
If you leave port=5984 on [httpd] then mochiweb crashes with eaddrinuse. I guess it's try to setup 2 web servers? Commenting out the port=5984 on httpd fixes that.
eacces usually means that you are lacking permission for something, is it possible that you've changed permission on a directory or file?
Looks like you can't run below port 1024 without some sort of special permissions, so port 443 won't work out of the box without something like haproxy.
I will checkout your solution, thanks!
One more thing - looks like you can run LetsEncrypt using their "standalone" option which sets up a temporary web server for the purposes of confirmation.
the standalone option looks interesting... do you know how to then forward port 443 to CouchDB?
I did not run on 443, I only wanted to do that because of letsencrypt / certbot, but the standalone option solved it for me.
I haven't tried any of these so YMMV.
We just updated the documentation adding a NOTE in the section How To Enable SSL (For HTTPS) On CouchDB and including both [chttpd] and [httpd] in the How to connect to CouchDB from a different Machine section. I hope this new format is less confusing for everyone. Thanks for you feedback.
I think it's a mistake to recommend using Erlang's SSL in your documentation. CouchDB basically doesn't work over SSL unless you use HAProxy. I managed to "get it working" but I'm running into a host of subtle errors very similar to @madpink.
Basically, my opinion is that CouchDB permissions are broken when using Erlang's SSL and Futon is more or less corrupted, and you will run into a variety of weird, frustrating bugs.
I'd suggest you either remove that option, or put a strong warning that it has problems, and instead, point people to an HAProxy based solution for SSL.
We highly appreciate your feedback, and will have it mind in our next sprints in order to get it re-checked and fixed if it was necessary.
We are glad to head that!