Thanks for that suggestion, but I’d rather not add extra components if I don’t need them. I was assuming that since you can specify the host’s address in about 5 or 6 places in the config file that this was to allow the use of different addresses for different purposes?
On Thu, 7 Nov 2019 at 19:36, Endre Kovács <[email protected]> wrote: > Hi, > > Have you considered putting a proxy in front, for UI / external access > and then let the nodes bind to their internal addresses? > > > https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration > < > https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration > > > > Best regards, > Endre > > > > On 7 Nov 2019, at 03:49, Phil H <[email protected]> wrote: > > > > Hi there, > > > > We have two addresses on each of our NiFi cluster hosts. One is > externally > > facing, which we use to access the UI, and connect to receiving > processors > > from the wider network. We are trying to configure NiFi to use the > internal > > network for its cluster traffic. However if I use the internal address > IPs > > in the nifi.cluster.node.address and nifi.remote.input.host properties, I > > end up getting two entries for each host in the cluster (both showing the > > external address) and only one of them will be online and connected. The > > other shows as disconnected. > > > > What am I missing here? > > > > Regards, > > Phil > >
