Silver ⭐️⭐️⭐️

Solved

Nifi 2.7.2 Start Problem

13 replies
5076 views
Translate All

I have installed and started Nifi.sh, it started and failed in next few seconds.

nifi.properties

# We recommend configuring HTTPS instead. The administrators guide provides instructions on how to do this.
nifi.web.http.host=localhost
nifi.web.http.port=8080
nifi.web.http.network.interface.default=
#############################################
#nifi.web.https.host=localhost
#nifi.web.https.port=8443
nifi.web.https.network.interface.default=
nifi.web.https.application.protocols=h2 http/1.1
nifi.web.jetty.working.directory=./work/jetty
nifi.web.jetty.threads=200
nifi.web.max.header.size=16 KB
nifi.web.proxy.context.path=
nifi.web.proxy.host=
nifi.web.max.content.size=
nifi.web.max.requests.per.second=30000

error.log
2025-12-31 14:03:57,387 INFO [main] org.apache.nifi.bootstrap.Command Application Process [9606] started
2025-12-31 14:03:57,388 INFO [main] org.apache.nifi.bootstrap.Command Bootstrap Process Running
2025-12-31 14:04:57,392 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process not found
2025-12-31 14:04:57,392 WARN [StartBootstrapCommand] o.a.n.b.command.StartBootstrapCommand Application monitoring failed with status [STOPPED]
File Descriptors: 262144
2025-12-31 14:03:57,315 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [AvailableLocalPorts] validation failed: Local Ports [28231] less than recommended [55000] according to [/proc/sys/net/ipv4/ip_local_port_range]
2025-12-31 14:03:57,316 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [Swappiness] validation failed: Swappiness [30] more than recommended [0] according to [/proc/sys/vm/swappiness]
2025-12-31 14:03:57,316 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [SocketTimedWaitDuration] validation failed: TCP Socket Wait [120 seconds] more than recommended [1 seconds] according to [/proc/sys/net/netfilter/nf_conntrack_tcp_timeout_time_wait]

nifi can't start with Java17 but Java21

Today after reconfigure the xml with username and password in login-identity-providers.xml

[root@c21adbvo000000n bin]# ./nifi.sh start

JAVA_HOME=/usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64
NIFI_HOME=/opt/nifi-2.7.2

[root@c21adbvo000000n bin]# ps -ef|grep nifi
root 32194 1 0 15:53 pts/1 00:00:00 /bin/sh ./nifi.sh start
root 32196 32194 19 15:53 pts/1 00:00:01 /usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64/bin/java -cp /opt/nifi-2.7.2/conf:/opt/nifi-2.7.2/lib/bootstrap/* -Xmx48m -Dlogback.statusListenerClass=ch.qos.logback.core.status.NopStatusListener -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi-2.7.2/logs -Dorg.apache.nifi.bootstrap.config.file=/opt/nifi-2.7.2/conf/bootstrap.conf org.apache.nifi.bootstrap.BootstrapProcess start
root 32220 32196 42 15:53 pts/1 00:00:02 /usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64/bin/java --class-path /opt/nifi-2.7.2/lib/nifi-server-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-api-2.5.0.jar:/opt/nifi-2.7.2/lib/slf4j-api-2.0.17.jar:/opt/nifi-2.7.2/lib/logback-core-1.5.22.jar:/opt/nifi-2.7.2/lib/jul-to-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-per-process-group-logging-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-property-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/logback-classic-1.5.22.jar:/opt/nifi-2.7.2/lib/log4j-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-properties-2.7.2.jar:/opt/nifi-2.7.2/lib/jcl-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-nar-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-stateless-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-python-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-runtime-2.7.2.jar:/opt/nifi-2.7.2/conf -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi-2.7.2/logs -Dnifi.properties.file.path=/opt/nifi-2.7.2/conf/nifi.properties -Dorg.apache.nifi.management.server.address=127.0.0.1:52020 -Xms1g -Xmx1g -Dsun.net.http.allowRestrictedHeaders=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dcurator-log-only-first-connection-issue-as-error-level=true -Djava.awt.headless=true -Djavax.security.auth.useSubjectCredsOnly=true org.apache.nifi.NiFi
root 32249 30550 0 15:53 pts/1 00:00:00 grep --color=auto nifi

Nifi started and failed in the next seconds

[root@c21adbvo000000n bin]# ./nifi.sh start

JAVA_HOME=/usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64
NIFI_HOME=/opt/nifi-2.7.2

[root@c21adbvo000000n bin]# ps -ef|grep nifi
root 32194 1 0 15:53 pts/1 00:00:00 /bin/sh ./nifi.sh start
root 32196 32194 19 15:53 pts/1 00:00:01 /usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64/bin/java -cp /opt/nifi-2.7.2/conf:/opt/nifi-2.7.2/lib/bootstrap/* -Xmx48m -Dlogback.statusListenerClass=ch.qos.logback.core.status.NopStatusListener -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi-2.7.2/logs -Dorg.apache.nifi.bootstrap.config.file=/opt/nifi-2.7.2/conf/bootstrap.conf org.apache.nifi.bootstrap.BootstrapProcess start
root 32220 32196 42 15:53 pts/1 00:00:02 /usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64/bin/java --class-path /opt/nifi-2.7.2/lib/nifi-server-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-api-2.5.0.jar:/opt/nifi-2.7.2/lib/slf4j-api-2.0.17.jar:/opt/nifi-2.7.2/lib/logback-core-1.5.22.jar:/opt/nifi-2.7.2/lib/jul-to-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-per-process-group-logging-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-property-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/logback-classic-1.5.22.jar:/opt/nifi-2.7.2/lib/log4j-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-properties-2.7.2.jar:/opt/nifi-2.7.2/lib/jcl-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-nar-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-stateless-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-python-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-runtime-2.7.2.jar:/opt/nifi-2.7.2/conf -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi-2.7.2/logs -Dnifi.properties.file.path=/opt/nifi-2.7.2/conf/nifi.properties -Dorg.apache.nifi.management.server.address=127.0.0.1:52020 -Xms1g -Xmx1g -Dsun.net.http.allowRestrictedHeaders=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dcurator-log-only-first-connection-issue-as-error-level=true -Djava.awt.headless=true -Djavax.security.auth.useSubjectCredsOnly=true org.apache.nifi.NiFi
root 32249 30550 0 15:53 pts/1 00:00:00 grep --color=auto nifi

nifi-app.log:Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowController' defined in class path resource [org/apache/nifi/framework/configuration/FlowControllerConfiguration.class]: Failed to instantiate [org.apache.nifi.controller.FlowController]: Factory method 'flowController' threw exception with message: Remote input HTTPS is enabled but nifi.web.https.port is not specified.
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:657)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:489)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1375)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1205)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:569)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:373)

I am using http port 8080 not https. Beside the nifi start and failed in 2 seconds, should I turn the https port?

Any pointers would be appreciated

BN

Apache NiFi

MattWhoAnswer

Titanium ⭐️⭐️⭐️

@PepeVo

"When I set the ip address (not localhost) on nifi.web.https.hosts and connect it with error "the proxy server is refusing connections". Do I need to set the nifi.web.proxy.host to ipaddress too?"

This because the IP does not exist in a SAN in your certificate. The first step here is create a proper clientAuth certificate that includes the SAN entries and EKUs.

Apache NiFI out-of-the-box would have created a proper format keystore certificate.

The CN value in the certificate is typically the hostname of the server it is being used on. I've seen multiple different value snippets in what has been shared by you.

That hostname you are trying to use in the NiFi URL must exist as a SAN entry in the certificate. (This is not a NiFi specific requirement, this is enforced by the JDK)

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

vafs

Gold ⭐️⭐️⭐️

Hello @PepeVo,

Thanks for being part of our community.

On NiFi 2 the HTTPS is expected, that is the reason why the service does not start:

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flowController' defined in class path resource [org/apache/nifi/framework/configuration/FlowControllerConfiguration.class]: Failed to instantiate [org.apache.nifi.controller.FlowController]: Factory method 'flowController' threw exception with message: Remote input HTTPS is enabled but nifi.web.https.port is not specified.

If you do not want to use HTTPS, you should disable the secure input port with this setting:
nifi.remote.input.secure=false
The default is true, so it always asks for HTTPS port.

The suggestion is to use HTTPS for security reasons, but if you still prefer HTTP, that is the option.

Translate

Regards, Andrés Fallas -- Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs-up button.

PepeVoAuthor

Silver ⭐️⭐️⭐️

If I turned/use https, I can't start the nifi. It failed after nifi.sh start in 2 seconds even commented all the http local host out, nifi.sh start failed.

2026-01-05 17:58:45,520 INFO [main] org.apache.nifi.bootstrap.Command Application Process [53898] started
2026-01-05 17:58:45,521 INFO [main] org.apache.nifi.bootstrap.Command Bootstrap Process Running
2026-01-05 17:58:56,403 INFO [main] org.apache.nifi.bootstrap.Command Application Process [53898] Management Server [http://127.0.0.1:52020/health] communication failed
2026-01-05 17:59:45,526 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process not found
2026-01-05 17:59:45,526 WARN [StartBootstrapCommand] o.a.n.b.command.StartBootstrapCommand Application monitoring failed with status [STOPPED]

(sorry, I can't put the output in quote to reply and/or create new post)

Translate

MattWho

Titanium ⭐️⭐️⭐️

@PepeVo

Without the nifi-app.log output it would be impossible for us to guess where it is failing in the startup process. The NiFi bootstrap process simply starts the main NiFi process and monitors that child process id to make sure it still exists (NiFI has not died).

Apache NiFi should start securely out of the box without needing to make any configuration modifications to the nifi.properties file. All you need to do is make sure Java 21 is the default java version installed on the NiFi server host first.

So my guess is issue is with some configuration you have modified from the defualt in your nifi.properties file. Or perhaps an issue with a manual configuration you made in some other nifi configuration file within the conf directory.

Thank you,
Matt

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

I removed nifi and re-extracted it again, this time, w/o modify anything, I tried to connect and still failed.

2026-01-06 17:21:03,063 INFO [main] org.apache.nifi.runtime.Application Starting NiFi 2.7.2 using Java 21.0.9+10-LTS with PID 14284
2026-01-06 17:21:03,070 INFO [main] o.apache.nifi.runtime.PropertiesProvider Loading Application Properties [/opt/nifi-2.7.2/conf/nifi.properties]
2026-01-06 17:21:03,090 INFO [main] org.apache.nifi.nar.NarUnpacker Expanding 120 NAR files started
2026-01-06 17:21:10,846 INFO [main] org.apache.nifi.nar.NarUnpacker Expanded 120 NAR files in 7.756 seconds (7756135613 ns)
2026-01-06 17:21:11,139 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-jetty-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-jetty-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,155 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/framework/nifi-framework-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/framework/nifi-framework-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,205 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,245 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-provenance-repository-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-provenance-repository-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,247 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-standard-services-api-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-standard-services-api-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,265 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-standard-shared-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-standard-shared-nar-2.7.2.nar-unpacked]

....

2026-01-06 17:21:11,340 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-confluent-platform-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-confluent-platform-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,341 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-http-context-map-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-http-context-map-nar-2.7.2.nar-unpacked]
2026-01-06 17:21:11,342 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded NAR file: /opt/nifi-2.7.2/./work/nar/extensions/nifi-lookup-services-nar-2.7.2.nar-unpacked as class loader org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-lookup-services-nar-2.7.2.nar-unpacked]

..

2026-01-06 17:44:02,990 INFO [ShutdownCommand] o.e.j.ee11.servlet.ServletContextHandler Stopped oeje11w.WebAppContext@677cc4e8{nifi-api,/nifi-api,b=null,a=AVAILABLE,h=oeje11s.SessionHandler@395281c2{STOPPED}}{./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-api-2.7.2.war}
2026-01-06 17:44:02,997 INFO [ShutdownCommand] o.e.j.ee11.servlet.ServletContextHandler Stopped oeje11w.WebAppContext@ddffa6c{/nifi-standard-content-viewer-2.7.2,/nifi-standard-content-viewer-2.7.2,b=null,a=AVAILABLE,h=oeje11s.SessionHandler@1c7cd434{STOPPED}}{./work/nar/extensions/nifi-standard-content-viewer-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-standard-content-viewer-2.7.2.war}
2026-01-06 17:44:03,006 INFO [ShutdownCommand] o.e.j.ee11.servlet.ServletContextHandler Stopped oeje11w.WebAppContext@4d4c1ba9{/nifi-jolt-transform-json-ui-2.7.2,/nifi-jolt-transform-json-ui-2.7.2,b=null,a=AVAILABLE,h=oeje11s.SessionHandler@10a907ec{STOPPED}}{./work/nar/extensions/nifi-jolt-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-jolt-transform-json-ui-2.7.2.war}
2026-01-06 17:44:03,016 INFO [ShutdownCommand] o.e.j.ee11.servlet.ServletContextHandler Stopped oeje11w.WebAppContext@317890ea{/nifi-update-attribute-ui-2.7.2,/nifi-update-attribute-ui-2.7.2,b=null,a=AVAILABLE,h=oeje11s.SessionHandler@59c43561{STOPPED}}{./work/nar/extensions/nifi-update-attribute-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-update-attribute-ui-2.7.2.war}
2026-01-06 17:44:03,019 INFO [ShutdownCommand] org.apache.nifi.nar.NarAutoLoaderTask Stopping NAR Auto-loader
2026-01-06 17:44:03,019 INFO [ShutdownCommand] org.apache.nifi.nar.NarAutoLoader NAR Auto-Loader stopped
2026-01-06 17:44:03,020 INFO [ShutdownCommand] o.a.n.f.r.CompositeExternalResourceProviderService External Resource Provider Service is stopped
2026-01-06 17:44:03,020 INFO [ShutdownCommand] o.a.nifi.runtime.command.ShutdownCommand Application shutdown completed

I tried to connect and after accepted the risk, the browser with 400 error

I don't see any LISTEN running. Just regenerate the keystore and truststore and will try to update nifi.properties, hopefully it works.

JAVA21 installed
[root@c21a logs]# java -version
openjdk version "21.0.9" 2025-10-21 LTS
OpenJDK Runtime Environment (Red_Hat-21.0.9.0.10-1.0.1) (build 21.0.9+10-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-21.0.9.0.10-1.0.1) (build 21.0.9+10-LTS, mixed mode, sharing)

thank you,

Bach-Nga

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

i generate a new keystore and truststore, modified nifi.properties and still can't start the application.

[root@c21adbvo000000n conf]# vi nifi.properties
[root@c21adbvo000000n conf]# bin
[root@c21adbvo000000n bin]# ./nifi.sh start
JAVA_HOME=/usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64
NIFI_HOME=/opt/nifi-2.7.2

[root@c21adbvo000000n bin]# ./nifi.sh status
JAVA_HOME=/usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64
NIFI_HOME=/opt/nifi-2.7.2
2026-01-08 14:44:25,214 INFO [main] org.apache.nifi.bootstrap.Command Application Process [9450] Management Server [http://127.0.0.1:52020/health] communication failed

nifi-app.log:

2026-01-08 14:44:46,199 INFO [main] o.a.n.w.c.ApplicationStartupContextListener Flow Controller started successfully.
2026-01-08 14:44:47,659 INFO [main] o.e.j.ee11.servlet.ServletContextHandler Started oeje11w.WebAppContext@2e3252{nifi-api,/nifi-api,b=file:///opt/nifi-2.7.2/work/jetty/nifi-web-api-2.7.2.war/webapp/,a=AVAILABLE,h=oeje11s.SessionHandler@4f402027{STARTED}}{./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-web-api-2.7.2.war}
2026-01-08 14:44:49,319 INFO [main] o.e.j.s.handler.ContextHandler._nifi No Spring WebApplicationInitializer types detected on classpath
2026-01-08 14:44:49,401 INFO [main] o.e.jetty.server.handler.ContextHandler Started oeje11w.WebAppContext@7271ee48{/nifi,/nifi,b=file:///opt/nifi-2.7.2/work/jetty/nifi-ui-2.7.2.war/webapp/,a=AVAILABLE,h=oeje11s.SessionHandler@30f6791d{STARTED}}{./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-ui-2.7.2.war}
2026-01-08 14:44:49,413 INFO [main] o.e.j.ee11.servlet.ServletContextHandler Started oeje11w.WebAppContext@7271ee48{/nifi,/nifi,b=file:///opt/nifi-2.7.2/work/jetty/nifi-ui-2.7.2.war/webapp/,a=AVAILABLE,h=oeje11s.SessionHandler@30f6791d{STARTED}}{./work/nar/extensions/nifi-server-nar-2.7.2.nar-unpacked/NAR-INF/bundled-dependencies/nifi-ui-2.7.2.war}
2026-01-08 14:44:49,423 INFO [main] o.eclipse.jetty.server.AbstractConnector Started oejs.ServerConnector@58f252fe{SSL, (ssl, alpn, h2, http/1.1)}{localhost:8443}
2026-01-08 14:44:49,423 INFO [main] org.eclipse.jetty.server.Server Started oejs.Server@1283ca23{STARTING}[12.1.5,sto=0] @19055ms
2026-01-08 14:44:49,425 INFO [main] org.apache.nifi.web.server.JettyServer Started Server on https://localhost:8443/nifi
2026-01-08 14:44:49,435 INFO [main] o.a.n.runtime.StandardManagementServer Started Management Server on http://127.0.0.1:52020
2026-01-08 14:44:49,437 INFO [main] org.apache.nifi.runtime.Application Started Application in 28.667 seconds (28667492314 ns)
2026-01-08 14:45:06,147 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:45:26,147 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:45:41,062 INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository Successfully deleted 0 files (0 bytes) from archive
2026-01-08 14:45:41,063 INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository Archive cleanup completed for container default; will now allow writing to this container. Bytes used = 15.07 GB, bytes free = 20.83 GB, capacity = 35.9 GB
2026-01-08 14:45:46,148 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:46:06,148 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:46:26,148 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:46:38,683 INFO [Write-Ahead Local State Provider Maintenance] o.a.n.wali.SequentialAccessWriteAheadLog Checkpointed Write-Ahead Log with 2 Records and 0 Swap Files in 3 milliseconds (Stop-the-world time = 0 milliseconds), max Transaction ID 7
2026-01-08 14:46:41,092 INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository Successfully deleted 0 files (0 bytes) from archive
2026-01-08 14:46:41,093 INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository Archive cleanup completed for container default; will now allow writing to this container. Bytes used = 15.07 GB, bytes free = 20.83 GB, capacity = 35.9 GB
2026-01-08 14:46:46,149 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds
2026-01-08 14:47:06,149 INFO [Checkpoint FlowFile Repository] o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile Repository with 0 records in 0 milliseconds

Nifi-bootraps.log

026-01-08 14:44:20,057 INFO [main] o.a.n.b.command.RunBootstrapCommand Java Version: 21.0.9+10-LTS
2026-01-08 14:44:20,064 INFO [main] o.a.n.b.command.RunBootstrapCommand Available Processors: 2
2026-01-08 14:44:20,118 INFO [main] o.a.n.b.command.RunBootstrapCommand Total Memory: 7902167040
2026-01-08 14:44:20,118 INFO [main] o.a.n.b.command.RunBootstrapCommand Maximum File Descriptors: 262144
2026-01-08 14:44:20,129 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [AvailableLocalPorts] validation failed: Local Ports [28231] less than recommended [55000] according to [/proc/sys/net/ipv4/ip_local_port_range]
2026-01-08 14:44:20,129 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [Swappiness] validation failed: Swappiness [30] more than recommended [0] according to [/proc/sys/vm/swappiness]
2026-01-08 14:44:20,129 WARN [main] o.a.n.b.process.RuntimeValidatorExecutor Runtime Configuration [SocketTimedWaitDuration] validation failed: TCP Socket Wait [120 seconds] more than recommended [1 seconds] according to [/proc/sys/net/netfilter/nf_conntrack_tcp_timeout_time_wait]
2026-01-08 14:44:20,197 INFO [main] o.a.n.b.command.RunBootstrapCommand /usr/lib/jvm/java-21-openjdk-21.0.9.0.10-1.0.1.el8.x86_64/bin/java --class-path /opt/nifi-2.7.2/lib/nifi-server-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-api-2.5.0.jar:/opt/nifi-2.7.2/lib/slf4j-api-2.0.17.jar:/opt/nifi-2.7.2/lib/logback-core-1.5.22.jar:/opt/nifi-2.7.2/lib/jul-to-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-per-process-group-logging-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-property-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/logback-classic-1.5.22.jar:/opt/nifi-2.7.2/lib/log4j-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-properties-2.7.2.jar:/opt/nifi-2.7.2/lib/jcl-over-slf4j-2.0.17.jar:/opt/nifi-2.7.2/lib/nifi-nar-utils-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-stateless-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-python-framework-api-2.7.2.jar:/opt/nifi-2.7.2/lib/nifi-runtime-2.7.2.jar:/opt/nifi-2.7.2/conf -Dorg.apache.nifi.bootstrap.config.log.dir=/opt/nifi-2.7.2/logs -Dnifi.properties.file.path=/opt/nifi-2.7.2/conf/nifi.properties -Dorg.apache.nifi.management.server.address=127.0.0.1:52020 -Xms1g -Xmx1g -Dsun.net.http.allowRestrictedHeaders=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dcurator-log-only-first-connection-issue-as-error-level=true -Djava.awt.headless=true -Djavax.security.auth.useSubjectCredsOnly=true org.apache.nifi.NiFi
2026-01-08 14:44:20,217 INFO [main] org.apache.nifi.bootstrap.Command Application Process [9450] started
2026-01-08 14:44:20,219 INFO [main] org.apache.nifi.bootstrap.Command Bootstrap Process Running
2026-01-08 14:44:25,214 INFO [main] org.apache.nifi.bootstrap.Command Application Process [9450] Management Server [http://127.0.0.1:52020/health] communication failed
2026-01-08 14:45:20,227 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:45:20,228 INFO [StartBootstrapCommand] o.a.n.b.command.StartBootstrapCommand Application monitoring started
2026-01-08 14:45:25,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:45:30,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:45:35,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:45:40,234 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
~~...~~

2026-01-08 14:49:40,234 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:49:45,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:49:50,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:49:55,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:00,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:05,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:10,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:15,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:20,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:25,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:30,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:35,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:40,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:45,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:50,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:50:55,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:00,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:05,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:10,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:15,232 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:20,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running
2026-01-08 14:51:25,231 INFO [StartBootstrapCommand] o.a.n.b.c.ApplicationProcessStatusBootstrapCommand Application Process [9450] running

I see the process nifi is still running but can't connect after accepting the risk. using chrome and/or firefox

thank you,

BN

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

nifi.properties

Translate

MattWho

Titanium ⭐️⭐️⭐️

@PepeVo

The invalid SNI is not a NiFi thing. It is related to trying to use 127.0.0.1 local IP in the URL. You are going to need to use a hostname.

I see in you set https.host=localhost in the nifi.properties. Is "localhost" a SAN entry in the certificate?

Can you share the verbose output from the NiFi generated keystore and the keystore you manually created? The NiFi generated keystore should have SAN entry for localhost and your server/computer hostname.

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

keystore:

truststore:

I don't know how to check "localhost" a SAN entry in the certificate? I will check with my colleague for the output.

Thank you,

BN

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

when I generate the keystore

I set on /etc/hosts

still not bring the ui up

vr,

Bach-Nga

Translate

MattWho

Titanium ⭐️⭐️⭐️

@PepeVo

Look at the output from following java keytool command:

keytool -v -list -keystore <nifi-keystore.p12/jks

You'll want to verify the EKU, KeyUsage, and SubjectAlternativeName (SAN) fields in the output.

EKU must contain clientAuth and serverAuth
SAN must contain your server hostname and any other hostname your node may also be known as. One of these SAN names is what you must use in the browser URL.

Hostname verification in the TLS exchange between your browser and NiFi is done using the certificate SAN and not the Certificate DN.

You also can add the same IP address (127.0.0.1) to the /etc/hosts file multiple times. it will resolve to the first entry. If you want to assign additional names to 127.0.0.1, it needs to be done on same line. But SNI is not going to allow you to use 127.0.0.1 in the browser URL.

You should set the "nifi.web.https.host" property in the nifi.properties file to one of the SAN values from your keytstore and then use that name in your url to access the NiFi UI.

On NiFi startup, you can also tail the nifi-app.log looking for the line that looks like this:

... [main] org.apache.nifi.web.server.JettyServer Started Server on https://<hostname>:8443/nifi

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

Thank you for instruction and I don't see any EKU, KeyUsage, and SubjectAlternativeName (SAN) fields in the output.

in the nifi-app.log I do see " g.apache.nifi.web.server.JettyServer Started Server on https://localhost:8443/nifi "

but still can't start the ui by using the host ip address or hostname, I get the "secure connection failed", if I connect it using localhost/127.0.0.1 I still get "400 Invalid SNI" (I heard to commented that SNI is not going to allow you to use 127.0.0.1 in the browser URL, but I am trying to see if I get the same error)

When I set the ip address (not localhost) on nifi.web.https.hosts and connect it with error "the proxy server is refusing connections". Do I need to set the nifi.web.proxy.host to ipaddress too?

thank you for any helps.
BN

Translate

MattWhoAnswer

Titanium ⭐️⭐️⭐️

@PepeVo

"When I set the ip address (not localhost) on nifi.web.https.hosts and connect it with error "the proxy server is refusing connections". Do I need to set the nifi.web.proxy.host to ipaddress too?"

This because the IP does not exist in a SAN in your certificate. The first step here is create a proper clientAuth certificate that includes the SAN entries and EKUs.

Apache NiFI out-of-the-box would have created a proper format keystore certificate.

The CN value in the certificate is typically the hostname of the server it is being used on. I've seen multiple different value snippets in what has been shared by you.

That hostname you are trying to use in the NiFi URL must exist as a SAN entry in the certificate. (This is not a NiFi specific requirement, this is enforced by the JDK)

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

Translate

PepeVoAuthor

Silver ⭐️⭐️⭐️

I regenterate the keystore with the common server name. Nifi UI works but I thought I can find the username/password in the nifi-bootstrap.log

I found the username and password encrypted in login-identity-providers.xml

how can I decrypt them, or should I generate a new username/password and how?

thank you.

BN

Translate

Sign up

Please use your Cloudera account.

Login to the community

Please use your Cloudera account.