Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic. Some of the high-level capabilities and objectives of Apache NiFi include:

Web-based user interface

Seamless experience between design, control, feedback, and monitoring

Highly configurable

Loss tolerant vs guaranteed delivery

Low latency vs high throughput

Dynamic prioritization

Flow can be modified at runtime

Back pressure

Data Provenance

Track dataflow from beginning to end

Designed for extension

Build your own processors and more

Enables rapid development and effective testing

Secure

SSL, SSH, HTTPS, encrypted content, etc...

Multi-tenant authorization and internal authorization/policy management

 

http://nifi.apache.org/

 

Let me know if you find any issues with the install.  It's fairly straight forward. 

Hi. I have this on the log:

 

2021-12-21 06:47:39,742 INFO [main] o.e.jetty.server.handler.ContextHandler Started o.e.j.w.WebAppContext@6fc1a8f6{nifi-error,/,file:///opt/nifi/nifi-current/work/jetty/nifi-web-error-1.15.1.war/webapp/,AVAILABLE}{./work/nar/extensions/nifi-server-nar-1.15.1.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-error-1.15.1.war}

 

And it's not open the UI... ☹️

On 12/21/2021 at 3:01 AM, EDalcin said:

Hi. I have this on the log:

 

2021-12-21 06:47:39,742 INFO [main] o.e.jetty.server.handler.ContextHandler Started o.e.j.w.WebAppContext@6fc1a8f6{nifi-error,/,file:///opt/nifi/nifi-current/work/jetty/nifi-web-error-1.15.1.war/webapp/,AVAILABLE}{./work/nar/extensions/nifi-server-nar-1.15.1.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-error-1.15.1.war}

 

And it's not open the UI... ☹️

 

Hey Ed, et al.

 

Were you able to get this to work, or another docker?  I too am not getting a UI.

I was able to get the WebUI working after manually creating a variable named "NIFI_WEB_HTTP_PORT" and setting it the same as "Web Interface HTTP Port"*.

 

* I had to assign a different port for those because the default port was in use, so I first had to remove "Web Interface HTTP Port" and readd it in order to change to container's port value too.

 

Also the appdata config doesn't work, probably due to some changes after new versions of NIFI and I couldn't figure out how to solve that...

On 5/21/2023 at 6:22 AM, UNOPARATOR said:

I was able to get the WebUI working after manually creating a variable named "NIFI_WEB_HTTP_PORT" and setting it the same as "Web Interface HTTP Port"*.

 

* I had to assign a different port for those because the default port was in use, so I first had to remove "Web Interface HTTP Port" and readd it in order to change to container's port value too.

 

Also the appdata config doesn't work, probably due to some changes after new versions of NIFI and I couldn't figure out how to solve that...

To clarify, NIFI_WEB_HTTP_PORT needs to be the same as the container port for "Web Interface Port", which is 8080 by default. I had some issues with this until I realized that. I also made it a port initially instead of a variable because I'm an idiot, or was tired, or both. So if you create the variable NIFI_WEB_HTTP_PORT and give it the value of 8080 you should be good, regardless of whether or not you need to change the host port for "Web Interface Port" if 8080 is already being used for the host.

As for the config, it should be /opt/nifi/nifi-current but that causes issues with some files not being created. Still working on that one.

I tried to install NIFI but the GUI is not coming up, I have set the variable NIFI_WEB_HTTP_PORT and are using the default 8080 port but nothing works for me, is there anything I can do? the container is started.

I have the same problem. Despite adding the variable NIFI_WEB_HTTP_PORT with the same port as in the config, I cannot access the web interface. However, the logs actually look good. I don't see any errors or anything unusual when starting the container or trying to access it.

The problem lies within the docker image of the latest Apache NiFi 2.x versions, even though you set the NIFI_WEB_HTTP_PORT port and not the NIFI_WEB_HTTPS_PORT, NIFI_WEB_HTTPS_PORT gets assigned which results an error indicating you cannot use both HTTP and HTTPS at the same time. And even when you try to just use HTTPS the "Invalid SNI" error occurs since v2.x HTTPS without a valid SSL certificate gives this error. I tried to use Swag to create a certificate and use that but I couldn't succeed.

Edited March 25, 20251 yr by UNOPARATOR

I got it the nifi GUI to work:

I installed it and it wouldn't load the GUI, so I added the NIFI_WEB_HTTP_PORT to the config in the Edit screen for the docker in Unraid, it still wouldn't work.

Based on the post from UNOPARATOR about the Invalid SNI, I switched the version to nifi:1.28.1 and let it download and run, then I could get the https on 8443 to load, but it was now the Invalid SNI 400 error.

I don't have any files in my appdata/nifi/ dir either.

I put the version in Unraid back to nifi:latest and restarted it, now the https gui loads but it doesn't have a default user/pass set up, so I had to go into the console and run the bin/nifi.sh set-single-user-credentials user pass and restart from Unraid, now I can log in and use nifi.

My guess is it's missing files, or maybe the docker coming as apache/nifi and not nifi:latest makes a difference?

EDIT: I noticed in the processors in the GUI it was all 1.28.1, same for the about, even though I had changed it back to latest. When I restarted the container the https gui gave the Invalid SNI error. I switched it back to 1.28.1 and restarted and can access the GUI, but my user/password was removed. The log does also show it generating and user/pass which does work to log in.

Edited July 11, 2025Jul 11 by nothus