@xpelive Just want to make sure a couple configurations. 1. The port you are using in the URL (8180) is the "nifi.web.http.port=" and not the "nifi.remote.input.socket.port=" port configured in your nifi.properties file. 2. When you start your NiFi instance, you will see a line output in the nifi-app.log when startup is complete that says the NiFi Ui is available at the following URLs: Is "localhost:8180" listed in one of those URLs? If not, you need to use one of the URLs listed in your Remote Process Group. It might be that localhost is bound to a different NIC on your server than what NiFi is listening on. 3. If you have or will ever have more than 1 NiFi node in a NiFi cluster, using "localhost" is not going to work. Your NiFi nodes should be configured to use the actual hostnames fo the server on which the service is running. That hostname should be configured in both these properties: --- nifi.remote.input.host= --- nifi.web.http.host= 4. Since your NiFi is not secured, make sure that your nifi.properties file is not configured to be secure: nifi.remote.input.secure=false. Null exceptions are particularly difficult to diagnose because a null basically means there was no error handling coded to handle to particular exception. Thus we need o look at all angles of the configuration to see where the issue may reside.
... View more
