Skip to content
RU

Port 5984: Apache CouchDB

Key idea:

Port 5984 (TCP) is the standard for Apache CouchDB. Apache CouchDB — NoSQL document database with multi-master replication. Port 5984 — HTTP API (REST). Usage: offline-first (PouchDB syncs), distributed mobile apps. 6984 — HTT

Below: what uses this port, security considerations, online check, FAQ.

Check your host & ports →

What is on this port

Apache CouchDB

Apache CouchDB — NoSQL document database with multi-master replication. Port 5984 — HTTP API (REST). Usage: offline-first (PouchDB syncs), distributed mobile apps. 6984 — HTTPS alternative.

Security considerations

CouchDB before 3.x was "admin party mode" (no auth). In 2026 it requires an admin on first start. Always HTTPS + non-default port if public.

Check this port online

Check port online →

Enterno.io Ping + Port checker tests TCP reachability of any port from our server in Moscow.

Understanding Apache CouchDB and Port 5984

Port 5984 is the designated TCP port for Apache CouchDB, a NoSQL database designed for ease of use and scalability. CouchDB utilizes a RESTful HTTP API, which allows users to interact with the database seamlessly over the web. This port is crucial for operations such as data retrieval, storage, and synchronization.

Apache CouchDB is particularly known for its multi-master replication capabilities, enabling distributed databases to work together without the need for a central server. This feature is particularly beneficial for applications that require high availability and fault tolerance.

When deploying CouchDB, it’s essential to configure the database server to listen on port 5984. This is typically done in the configuration file, where you can set the bind_address to listen on all interfaces or a specific IP address. For example:

  • bind_address = 0.0.0.0 to allow access from any IP.
  • bind_address = 127.0.0.1 to restrict access to local connections only.

In summary, understanding how to utilize port 5984 effectively is crucial for developers and system administrators working with Apache CouchDB.

Security Considerations for Port 5984

Securing port 5984 is vital due to the sensitive nature of the data stored in CouchDB. By default, CouchDB does not enforce authentication, which can expose your database to unauthorized access. Here are several security measures you should implement:

  • Enable Authentication: Use the CouchDB built-in security features to enforce user authentication. This can be accomplished by setting up admins and readers in the database's security object.
  • Use HTTPS: Configure CouchDB to use SSL/TLS to encrypt data in transit. This prevents eavesdropping and man-in-the-middle attacks. You can set up HTTPS by modifying the httpd section in the CouchDB configuration file:
    • [httpd]
    • enable_ssl = true
    • ssl_cert_file = /path/to/your/cert.pem
    • ssl_key_file = /path/to/your/key.pem
  • Firewall Configuration: Use firewall rules to restrict access to port 5984 only from trusted IP addresses. This can significantly reduce the attack surface.
  • Regular Updates: Keep your CouchDB installation up to date to protect against known vulnerabilities.

By implementing these security measures, you can help protect your CouchDB instance and the data it holds while utilizing port 5984 efficiently.

Practical Examples for Using Port 5984 with CouchDB

Working with Apache CouchDB over port 5984 involves various operations that can be performed using simple HTTP requests. Below are some practical examples that showcase how to interact with CouchDB using command-line tools like curl.

1. Creating a Database:

To create a new database named my_database, you would execute the following command:

curl -X PUT http://localhost:5984/my_database

2. Storing a Document:

To add a JSON document to your database, use the following command:

curl -X POST http://localhost:5984/my_database -d '{"name":"example","type":"demo"}' -H 'Content-Type: application/json'

3. Retrieving a Document:

To fetch a document by its ID, you'll need to know the document's unique identifier:

curl -X GET http://localhost:5984/my_database/example_id

4. Updating a Document:

To update an existing document, you must include the document's revision number:

curl -X PUT http://localhost:5984/my_database/example_id -d '{"_id":"example_id","_rev":"1-abc","name":"updated_example"}' -H 'Content-Type: application/json'

5. Deleting a Document:

To delete a document, you must specify the document ID and its revision:

curl -X DELETE http://localhost:5984/my_database/example_id?rev=1-abc

These examples provide a foundational understanding of how to interact with Apache CouchDB through port 5984. Mastering these commands will enable you to efficiently manage your NoSQL database.

Learn more

Sources

Frequently Asked Questions

Is port 5984 open by default?

No, modern cloud providers (AWS, Google Cloud, Yandex) close all incoming ports by default. You must explicitly allow port 5984 in a Security Group or firewall.

How to check if my port 5984 is reachable?

Use Enterno Ping + Port Checker. Or in shell: nc -vz example.com 5984 or telnet example.com 5984.

Is port 5984 safe to expose?

Depends on the service. Apache CouchDB should never be exposed publicly without authentication + TLS. See our 2026 exposure research.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.