Try something like this:

listeners=CLIENT://:9090 <http://my.public.dns.name:9090/>,PLAINTEXT://:9092
advertised.listeners=CLIENT://my.public.dns.name:9090,PLAINTEXT://:9092

This will tell the listener to listen on your local ip addresses but to
advertise the DNS name.

Jakub

On Tue, Nov 7, 2017 at 11:04 PM, Thomas Stringer <trstrin...@gmail.com>
wrote:

> I can't seem to get a listeners and advertised.listeners configuration for
> server properties figured out so I can connect remotely with my producer
> and consumers.
>
> If I set it like this...
>
> listeners=CLIENT://:9090,PLAINTEXT://:9092
> advertised.listeners=CLIENT://:9090,PLAINTEXT://:9092
>
> From my external client I get a NoBrokersAvailable error. If I try this...
>
> listeners=CLIENT://0.0.0.0:9090,PLAINTEXT://:9092
> advertised.listeners=CLIENT://0.0.0.0:9090,PLAINTEXT://:9092
>
> I get an error that it can't listen on the meta-address 0.0.0.0.
>
> This is currently being hosted with a public interface, but if I try to set
> this:
>
> listeners=CLIENT://my.public.dns.name:9090,PLAINTEXT://:9092
> advertised.listeners=CLIENT://my.public.dns.name:9090,PLAINTEXT://:9092
>
> Then I get an error that it can't bind to the requested address. This is
> sitting behind some networking infrastructure, as it's obvious ip addr only
> shows my private IP address.
>
> How would I get around this to setup a listener so an external/public
> producer/consumer could connect to this broker?
>
> Thank you in advance!
>

Reply via email to