如何让Azure虚拟机上的Apache Kafka同时支持本地localhost/127.0.0.1与域名访问

Hey there! Let's break down why you can't connect to your Kafka broker using localhost:9092 or 127.0.0.1:9092 directly on the Azure VM, even though external connections work fine. Here are the key fixes to try:

1. Check Local Firewall Rules on the Azure VM #

Your Kafka listener is set to PLAINTEXT://0.0.0.0:9092, which means it should listen on all network interfaces—including the loopback (localhost). But local firewall rules (like ufw on Ubuntu or firewalld on RHEL/CentOS) might be blocking loopback traffic to port 9092.

• Verify if the port is reachable locally:

  nc -zv localhost 9092
  # Or use telnet if nc isn't installed:
  telnet localhost 9092
  

• If the connection is rejected, allow loopback traffic to port 9092:
  For Ubuntu/Debian (ufw):

  sudo ufw allow from 127.0.0.1 to any port 9092
  sudo ufw reload
  

  For RHEL/CentOS (firewalld):

  sudo firewall-cmd --add-rich-rule='rule family="ipv4" source address="127.0.0.1" port port="9092" protocol="tcp" accept' --permanent
  sudo firewall-cmd --reload
  

2. Update Kafka's advertised.listeners to Include Local Addresses #

Right now, your advertised.listeners only points to my.domain:9092. When you connect from the VM using localhost, the Kafka broker will return this advertised address to your client, and the client will try to switch to my.domain:9092 instead of staying on localhost. If your VM's local DNS doesn't resolve my.domain to 127.0.0.1, this will fail.

Fix this by adding local loopback addresses to advertised.listeners in your server.properties file:

advertised.listeners=PLAINTEXT://my.domain:9092,PLAINTEXT://localhost:9092,PLAINTEXT://127.0.0.1:9092

After updating, restart the Kafka broker for changes to take effect:

# Adjust the path to your Kafka bin directory as needed
./kafka-server-stop.sh
./kafka-server-start.sh -daemon ../config/server.properties

3. Map my.domain to Loopback in the VM's Hosts File #

If you prefer not to modify Kafka's listener config, you can force the VM to resolve my.domain to 127.0.0.1 locally. Edit the /etc/hosts file (with sudo privileges) and add this line:

127.0.0.1 my.domain

This way, when your local client receives the advertised my.domain:9092 address, it will resolve it to the loopback interface and connect successfully.

4. Verify Kafka is Actually Listening on All Interfaces #

Double-check that Kafka is listening on 0.0.0.0:9092 (all interfaces) with this command:

netstat -tulpn | grep 9092

You should see a line like tcp6 0 0 :::9092 :::* LISTEN <kafka-pid>/java—the :::9092 (for IPv6) or 0.0.0.0:9092 (IPv4) confirms it's listening on all interfaces.

Try these steps one by one, and you should be able to connect to Kafka via localhost:9092 or 127.0.0.1:9092 on the Azure VM.

内容的提问来源于stack exchange，提问作者vishal dharankar