Apache Nifi first access failed

[#1]

Hello everyone,

I have installed Apache NiFi 2.7.1 on RHEL9. Unfortunately, I can't access it via a web browser (port 8443) from another computer.
The firewall in RHEL is configured for port 8443, and even disabling the firewall doesn't allow access.
The following entries appear in the nifi-app-log:

2025-12-17 13:27:51,876 INFO [main] org.eclipse.jetty.server.Server Started oejs.Server@6f25bf88{STARTING}[12.1.5,sto=0] @11898ms
2025-12-17 13:27:51,877 INFO [main] org.apache.nifi.web.server.JettyServer Started Server on https://vm-P004-4067:8443/nifi 
2025-12-17 13:27:51,883 INFO [main] o.a.n.runtime.StandardManagementServer Started Management Server on http://127.0.0.1:52020 
2025-12-17 13:27:51,884 INFO [main] org.apache.nifi.runtime.Application Started Application in 15.213 seconds (15213111810 ns)

In the nifi.properties file, I only specified the hostname of the Linux server in the following entry: nifi.web.https.host.
Does anything else need to be configured? All the example videos for installing Nifi don't mention any further configuration.
If you'd like me to add an excerpt from the log, please let me know.
Thanks in advance for your help.

bg
Mirko

[#2 · Accepted solution]

Hello @mimei 

Thanks for reaching our community. 

When you set nifi.web.https.host, that will be the only interface used for login. 
If for some reason it does not reply properly or respond as 127.0.0.1, the web UI will never connect. And this looks like it's what is happening in your side: 

2025-12-17 13:27:51,877 INFO [main] org.apache.nifi.web.server.JettyServer Started Server on https://vm-P004-4067:8443/nifi 
2025-12-17 13:27:51,883 INFO [main] o.a.n.runtime.StandardManagementServer Started Management Server on http://127.0.0.1:52020 

As you see, vm-P004-4067 it's answering on 127.0.0.1. 

What you can do here is leave nifi.web.https.host empty or specifically set the IP you want to use for the connection. 
Also, if you need to change the port, you can this setting: nifi.web.https.port

[#3]

Hello @vafs 

Sorry for the late reply.
Thanks, the tip helped.
I also had to replace the self-signed certificate from nifi.
Then I was able to access it. 🙂

bg

mirko