@Artem Anokhin No matter which host URL(s) you use in the configuration of an Remote Process Group (RPG). the RPG will ned up retrieving site-to-site (S2S) details that include all the currently connected nodes in the target cluster. - Included in those S2S details are things like: 1. Hostname of each node - defined by "nifi.remote.input.host= " configured on each node. 2. If "Raw" transport protocol is supported - defined by this property "nifi.remote.input.socket.port=" being set. 3. if "HTTP" transport protocol is supported - defined by this property "nifi.remote.input.http.enabled=" being set to true or false 4. If S2S connection is secure - defined by "nifi.remote.input.secure=" being set to true or false - There is no way to create "node groups" that would only be returned to a source NiFi during the retrieve S2S details phase of communications. - Thank you, Matt ... View more

@Jason Sphar The GetTCP processor is designed to send data to a target TCP port. It sounds like you are trying to recieve data via TCP port in to NiFi? - If that is the case, you want to be using a ListenTCP processor instead that will bind to the tcp port you will be sending your data to. - Thanks, Matt ... View more

@Brandon Spratt You are absolutely correct that older versions of NiFi allowed user to configure both the "nifi.web.http.port" and "nifi.web.https.port" properties in NiFi at the same time. NiFi would at that time then allow any user to access the NiFi UI via the unsecured http URL or via the HTTPS secured URL. - The need client auth property never had anything to do with user access to NiFi. That property was specific to node to node communications only. False simply meant that nodes acting as clients talking securely to other nodes (acting as server) did not need to verify trust of the server's presented certificate in the TLS/SSL handshake. - Allowing user to access a secured NiFi via a http configured URL presents a huge security risk, so that capability was removed. Once NiFi is secured by enabling https, even if http is still configured access will be blocked to the http URL(s). - Can you elaborate on the use case for allowing users to anonymously access a secured NiFi? This opens a security hole where any client (user or other system) can get access to the data passing through that NiFi. - As a work-around you could generate a user certificate that gives all access to every NiFi policy and make that certificate freely available to all your users. - Thank you, Matt - If you find an answer the best addresses your initial question, please take a moment to login to the forum and click the "Accept" link below that provided answer. ... View more

@Rahul Kumar - Where are you getting the nar or jar for this custom influxdb processor from? - Once you have this custom processor nar/jar file, you will want to create a custom lib directory to place it in and then configure your nifi to read that additional custom lib folder location. This is done by adding a new key/value pair to the nifi,properties configuration file: nifi.nar.library.directory.custom-lib=/<path to custom lib dir>/custom-lib - A restart of NiFi will be required before NiFi will load any newly added custom libraries. At that point the new processor shoudl be available to add to the canvas just as you add any other processor. - Thank you, Matt ... View more