Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

NiFi installation on remote unix server

avatar
Explorer

I have installed NiFi and MiNiFi on a remote unix server. When I run the command: tail -f nifi-app.log
I get all repositories: content_repository, database_repository, flowfile_repository, provenance_repository for NiFi.
quamd I run the same command for MiNiFi: tail -f minifi-app.log, get three repositories: content_repository, flowfile_repository, provenance_repository.

 the installation was successful. I run the command: http://ip:8080. I can't get the NiFi interface, I'm told that this page is not accessible.
I do the same thing for MiNiFi and I don't get  interface.
this page is not accessible. i need help

 

 

1 ACCEPTED SOLUTION

avatar
Super Mentor

@Justee 
So with NiFi, there is a UI, but you need to make sure there is a route to the host (where you are laughing your browser) and target:

<hostname/IP>:<port>

 If your NiFi in startup is binding to private network interface or only the loopback IP address, you would most likely be unable to reach those IPs from your client machine on a public network.

From your client machine, can you ping that "<hostname/IP>"?

Does the server where your NiFi is running have multiple network interfaces for perhaps a public and a private network?  Did you try changing the IP that NiFi binds to in nifi.properties file:

nifi.web.http.host=


Did you try to tell your NiFi to bind to multiple network interfaces in the nifi.properties file if they exist in that server?  For example:

nifi.web.http.network.interface.eth0=eth0
nifi.web.http.network.interface.eth1=eth1

Your servers network interfaces may be different then above example.

If you found this solution helpful, please take a moment to login in and click accept on all solutions that helped you.
Thanks,

Matt

View solution in original post

3 REPLIES 3

avatar
Super Mentor

@Justee 

MiNiFi has not web interface like NiFi has.  MiNiFi is meant to be lightweight and simply execute dataflows you build in NiFi.

When you run "tail -F nifi-app.log" immediately after startup (./nifi.sh start) of the NiFi, you will see the NiFi process starting up.  The NiFi web interface will not be accessible until you see these log lines output to that nifi-app.log file:

2021-05-03 13:23:17,031 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
2021-05-03 13:23:17,031 INFO [main] org.apache.nifi.web.server.JettyServer https://<hostname/IP>:<port>/nifi


Until you see these lines you will not be able to load the interface.  You should also verify that the URL you are trying to use maps to one from the list and you are using the correct port.

Looking at your attachments, I see it looks like your NiFi bound to your loopback address 127.0.0.1 which would only be reachable via a browser running on that same host and to 10.0.2.15.  You would need to make sure that the host where you have your browser is able to reach this IP (can you ping it?).

Hope this helps,

Matt

avatar
Explorer

Hi@MattWho,Thanks for the explanation of MiNiFi. When I execute the command (./nifi.sh start) and then the command (tail -f nifi-app.log) , I get these two lines in the output.

2021-05-03 20:30:07,021 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
2021-05-03 20:30:07,021 INFO [main] org.apache.nifi.web.server.JettyServer https://<hostname/IP>:<port>/nifi

when I launch http://ip:8080. the message is: This site is inaccessible.

avatar
Super Mentor

@Justee 
So with NiFi, there is a UI, but you need to make sure there is a route to the host (where you are laughing your browser) and target:

<hostname/IP>:<port>

 If your NiFi in startup is binding to private network interface or only the loopback IP address, you would most likely be unable to reach those IPs from your client machine on a public network.

From your client machine, can you ping that "<hostname/IP>"?

Does the server where your NiFi is running have multiple network interfaces for perhaps a public and a private network?  Did you try changing the IP that NiFi binds to in nifi.properties file:

nifi.web.http.host=


Did you try to tell your NiFi to bind to multiple network interfaces in the nifi.properties file if they exist in that server?  For example:

nifi.web.http.network.interface.eth0=eth0
nifi.web.http.network.interface.eth1=eth1

Your servers network interfaces may be different then above example.

If you found this solution helpful, please take a moment to login in and click accept on all solutions that helped you.
Thanks,

Matt