Configuring remote access for couchdb

By default, CouchDb is configured to be access only from a local port, i.e: you can connect to a couchdb instance as long as it is on the same host. Also, it is necessary that the HTTP request be made using the loopback IP address (127.0.0.1).

In case you want to be able to access a couchdb instance from an external machine, you need to make some changes to the couchdb configuration. Note that you would need to have superuser access in order to make changes to these files. Usually couchdb will have two configuration (ini) files in /etc/couchdb depending on your installation. Both these files (default.ini and local.ini) can be used to enable remote hosts to access couchdb. The configuration required for this is:

[httpd]
port = 5984
bind_address = 0.0.0.0

By default the configuration would be:

[httpd]
port = 5984
bind_address = 127.0.0.1


This means that the Http server is bound only to the loopback IP address, which is why we change it to 0.0.0.0 to make it bind to any IP address. If you don't need that, instead you want to allow it on a specific IP address only, you can do that too.

Whilst doing this, you must also understand the purpose of these two files. Default.ini is meant to contain all system wide settings that would want to have, while local.ini is to be used to override the system defaults.

Lastly, you need to stop and start your couchdb service after you make any changes to these ini files.
Location: Tharamani, Tharamani

Comments

  1. Unknown16 December 2015 at 06:31

    Still unable to connect. Can you help?

    ReplyDelete
    Replies
    1. Ausmarton Fernandes22 March 2016 at 23:58

      Sorry for the late response. I haven't been around here for a while now. If it helps, this post is 4 years old, and couchdb might have changed since then. But, it would help if you give some more details as to what happens when you try to connect.
      Thanks.

      Delete
    2. Unknown23 March 2016 at 08:08

      Okay, I had done it some way. But thanks for the response. May I ask you if I have any more doubt or challenges?

      Delete
  2. Saheel Rock15 October 2016 at 19:42

    Hi Guys,
    Am having the issue to make it remote access. Please help

    ReplyDelete
  3. Unknown17 December 2016 at 13:42

    If you are using an AWS EC2 instance then you have to add port 5984

    ReplyDelete
  4. Unknown1 February 2017 at 20:18

    This is not working in my case.Any help for this. I have changed the bind_address in both the files to 0.0.0.0 but nothing happens. I am using an aws ec2 instance on which couchdb is installed. My email-id is mitultyagi45@gmail.com. Help!

    ReplyDelete
  5. Unknown2 February 2017 at 08:12

    Hey it is done. Thanks for the post.Great one!.

    ReplyDelete
  6. Unknown24 September 2017 at 11:02

    hello..
    How can I change this "bind_address" from my command line?
    something like
    "curl -X GET http://yahav:****@10.9.11.118:5984/_utils/#_config/main_config/chttpd"

    ReplyDelete

Post a Comment

Popular posts from this blog

Errors while trying to monitor Asterisk through Nagios

Today, I was trying to configure nagios to monitor an asterisk setup. I installed the nagios-plugins-check_sip plugin available for CentOS. I also had check_asterisk downloaded from here just to try out both. Now, check_asterisk and check_sip are perl scipts which can be used to monitor an asterisk setup. When run through the command line, they seem to work fine, i.e: given that asterisk or any other sip server is listening and your command is correct, you should get output similar to this: ;SIP/2.0 200 OK, 0.000585 seconds response time, cnt=1 Although, that's exactly what I got, it didn't work the same way through nagios, I was getting the following as the output from the plugin. (Service check did not exit properly) After enabling debug info for nagios, I found this in the logs, HOST: remotehost, SERVICE: Asterisk, CHECK TYPE: Active, OPTIONS: 1, SCHEDULED: Yes, RESCHEDULE: Yes, EXITED OK: No, RETURN CODE: 3, OUTPUT: **ePN failed to compile /usr/lib64/nagios/plugins/chec...
Read more

Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3

I had a setup of tomcat running on port 8080 and Apache proxying for tomcat on port 80. If I tried to access webapps directly from tomcat on port 8080,. they were accessible, while on port 80, I would get the followig error: Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 following fix worked: adding retry=1 acquire=3000 timeout=600 Keepalive=On after the Proxy directive in the http configuration.
Read more