Our documentation should be improved here, I agree. I made the local.ini file at least a bit clearer a while ago:
https://github.com/apache/couchdb/blob/master/rel/overlay/etc/local.ini#L29-L32 but I don't know if that change made it into 2.0 or post-2.0. NOTE: You should be doing *everything* in CouchDB 2.0 through the clustered port (default: 5984) unless *explicitly* instructed to do otherwise in the documentation. We do not guarantee that all functionality is supported by the node-local (5986) port - there have been bugs reported that we will not be fixing. We will most likely be removing the node-local port in CouchDB 3.0. I wrote and released a utility, couchup, that helps migrate 1.x databases to 2.x. It will be included in 2.1, but you can get your hands on it early here: https://github.com/apache/couchdb/blob/master/rel/overlay/bin/couchup Click on "raw" and save it, then run it. python 2.7 or 3.x and the python-requests library are required to use couchup. Hope this helps, Joan Touzet ----- Original Message ----- From: "Doug Snyder" <webcoach...@gmail.com> To: user@couchdb.apache.org, "Joan Touzet" <woh...@apache.org> Sent: Thursday, 22 June, 2017 8:51:18 PM Subject: Re: Connection Refused Errors connecting to CouchDB 2.0 Noel, that seemed to do the trick for me. For the community maybe this should be clarified because the docs are contradictory as far as I can tell. As far as I can see there is absolutely no documentation for chttpd. There's a section called: CouchDB HTTP Server ere's a at http://docs.couchdb.org/en/2.0.0/config/http.html and it explicity says that [httpd] should be configured for exactly what I was trying to do: bind_address Defines the IP address by which CouchDB will be accessible: [httpd] bind_address = 127.0.0.1 To let CouchDB listen any available IP address, just set up 0.0.0.0 value: [httpd] bind_address = 0.0.0.0 But,is an seemingly ominous contradiction, the comments in the .ini file comments: ; NOTE that this only configures the "backend" node-local port, not the ; "frontend" clustered port. You probably don't want to change anything in ; this section. I don't understand the reference to the "frontend" clustered port because I just came from CouchDB 1.6.1 and don't understand and am not using clustering yet. But the docs seem to say that [httpd] bind_address SHOULD be configured for a simple unclustered server or maybe a clustered one too. The local.ini comments for [chttpd] mention the Mochiweb HTTP server and I don't know what that is or if I'm using it and I can't tell if that reference only describes on of the lines called server_options Again nothing about chttpd is explained in the docs. On Thu, Jun 22, 2017 at 8:16 PM, Doug Snyder < webcoach...@gmail.com > wrote: Its on a production server. I'm getting logs of people from China and Russia trying to hack into my ssh. Is that a good idea to do even for a minute? On Thu, Jun 22, 2017 at 3:11 AM, Joan Touzet < woh...@apache.org > wrote: Hi Doug, have you tried completely disabling firewalld and seeing if it works? -Joan ----- Original Message ----- From: "Doug Snyder" < webcoach...@gmail.com > To: user@couchdb.apache.org Sent: Wednesday, 21 June, 2017 10:50:09 PM Subject: Re: Connection Refused Errors connecting to CouchDB 2.0 I've been waiting over a week to get any reply, with no success. I'm trying to get a basic server up. Can anybody help me with what should be a pretty simple problem?
