How to Fix Connection Refused Error in Kafka

The connection refused error in Kafka usually happens because the Kafka broker is not reachable at the specified address or port. To fix it, ensure the broker is running, the listeners and advertised.listeners settings are correct, and the client connects to the right host and port.

Why This Happens

This error occurs when your Kafka client tries to connect to a broker but cannot reach it. Common reasons include the Kafka broker not running, incorrect broker address or port, or network/firewall blocking the connection.

properties

bootstrap.servers=localhost:9092

Output

org.apache.kafka.common.errors.TimeoutException: Failed to update metadata after 60000 ms.

The Fix

Check that the Kafka broker is running and listening on the correct port. Verify listeners and advertised.listeners in server.properties match the address clients use. For example, if clients connect remotely, advertised.listeners must use the broker's reachable IP or hostname.

properties

listeners=PLAINTEXT://0.0.0.0:9092
advertised.listeners=PLAINTEXT://your.broker.ip:9092

Output

Kafka broker starts successfully and clients connect without errors.

Prevention

Always configure advertised.listeners to the broker's reachable address. Use tools like telnet or nc to test connectivity before running clients. Keep firewall rules open for Kafka ports and monitor broker status regularly.

Related Errors

TimeoutException: Happens if the broker is slow or unreachable.
Authentication errors: Occur if security settings are incorrect.
Quick fixes include verifying broker status, network, and client configs.

Key Takeaways

Ensure Kafka broker is running and reachable at the configured address and port.

Set advertised.listeners to the broker's accessible hostname or IP for clients.

Check network and firewall settings to allow Kafka traffic on port 9092.

Test connectivity with simple network tools before starting clients.

Monitor broker logs for connection issues and fix configuration promptly.