Docker容器中Couchbase Server连接Elasticsearch认证失败问题

Let's tackle this authentication problem step by step—since you've confirmed both services are on the same Docker network, we can narrow our focus to credential configurations, plugin setup, and permission checks.

1. Verify Your Elasticsearch Configuration is Correct #

First, double-check that you've added the right Couchbase auth settings in your elasticsearch.yml file, and that the file is being properly loaded by the ES container.

For Elasticsearch 5.6.4 (matching your sebp/elk:564 image), the required config entries are:

couchbase.username: your-couchbase-admin-or-service-user
couchbase.password: your-couchbase-user-password

If your Couchbase cluster has SSL enabled, you'll also need these additional lines:

couchbase.ssl.enabled: true
couchbase.ssl.keystore.path: /path/to/your/keystore.jks
couchbase.ssl.keystore.password: your-keystore-password

Critical Check for Docker Environment #

The sebp/elk image stores Elasticsearch configs in /etc/elasticsearch/elasticsearch.yml—make sure your Dockerfile is modifying this exact file, not a different path. You can verify this by exec'ing into the ES container and checking the config:

docker exec -it <your-es-container-name> cat /etc/elasticsearch/elasticsearch.yml

Ensure the couchbase.username and couchbase.password lines are present and correctly spelled.

2. Confirm the Couchbase Transport Plugin is Installed & Version-Matched #

Your Dockerfile snippet cuts off, so I want to make sure you've installed the correct Couchbase plugin for Elasticsearch 5.6.4. The plugin version must exactly match your Elasticsearch version to avoid compatibility issues.

Add this step to your Dockerfile to install the plugin:

RUN bin/elasticsearch-plugin install com.couchbase.client:couchbase-elasticsearch-connector:5.6.4

After building the image, verify the plugin is loaded by checking ES logs or running:

docker exec -it <your-es-container-name> bin/elasticsearch-plugin list

3. Validate Couchbase User Permissions #

Even if your credentials are correct, the Couchbase user might not have the necessary permissions for Elasticsearch to access the data. Log into your Couchbase web console (via http://<couchbase-container-ip>:8091) and:

• Go to Security > Users
• Select the user you're using for ES integration
• Ensure they have at least these roles:
  • Data Reader (for every bucket you want to sync with Elasticsearch)
  • Cluster Monitor (required for the plugin to fetch cluster metadata)
    If you're using advanced features like XDCR to push data to ES, add the XDCR Admin role as well.

4. Test Credentials Directly from the ES Container #

To rule out any Docker-specific credential issues, test your Couchbase credentials directly from the Elasticsearch container using curl:

docker exec -it <your-es-container-name> curl -u couchbase-username:couchbase-password http://<couchbase-service-name>:8091/pools

Replace <couchbase-service-name> with the name of your Couchbase service in docker-compose.yml. If this returns a valid JSON response about the Couchbase cluster, your credentials are working—if not, you'll get an authentication error that points to the root issue.

5. Check Elasticsearch Logs for Specific Errors #

If all the above checks pass, dig into the Elasticsearch logs to get precise error details:

docker logs <your-es-container-name>

Look for lines containing "authentication failed", "invalid credentials", or "permission denied"—these will tell you exactly where the breakdown is (e.g., wrong password, missing permissions, plugin misconfiguration).

内容的提问来源于stack exchange，提问作者Niloofar Gheibi