Double check your settings for running in insecure mode in the nifi.properties. If you are using an OpenShift route you can have it use https as well with the backend being http (nifi configured in insecure mode) and it should still all work (copy/paste will also work). We run with both a cluster/node port setup and headless service with routes for different types of NiFi setups.
# Site to Site properties nifi.remote.input.host=<hostIpAddress> nifi.remote.input.secure=false # web properties nifi.web.http.host=<anyHostWillDoLikeContainerHostName> nifi.web.http.port=<anyPortYouLike> nifi.web.https.host= nifi.web.https.port= nifi.web.proxy.host= # security properties # nifi.sensitive.props.key=<yourMadeUpKeyValueHere> nifi.security.keystore= nifi.security.keystoreType= nifi.security.keystorePasswd= nifi.security.keyPasswd= nifi.security.truststore= nifi.security.truststoreType= nifi.security.truststorePasswd= nifi.security.user.authorizer= nifi.security.allow.anonymous.authentication= nifi.security.user.login.identity.provider= nifi.security.user.jws.key.rotation.period= Jeremy On Mon, Sep 1, 2025 at 10:13 PM Lakshman Gupta < [email protected]> wrote: > Hi, > > We are trying to deploy Nifi 2.5.0 in openshift environment. We have > configured it to work in *http* instead of https. We have also enabled > anonymous authentication. > We are able to open the Nifi UI with the route but some of the APIs like > below are failing. Looks like port number is getting appended to the > openshift route hostname. > > http://nifi-http-test.com:8443 > /nifi-api/process-groups/f57168a8-0198-1000-0000-00007064a8f2 > > This is a PUT API that is getting generated when we try to move the > processGroup within the nifi canvas. > > We have already tried setting "nifi.web.proxy.host" to openshift route > hostname but still the issue persists. We even tried to run the nifi with > port 443 but still the port is getting added. > > Can someone please let us know if we are missing any configuration to make > the Nifi work with openshift in *http mode.* > > *P.S: It works fine when we are using https.* > > Thanks, > Lakshman > > DISCLAIMER > ========== > This e-mail may contain privileged and confidential information which is > the property of Persistent Systems Ltd. It is intended only for the use of > the individual or entity to which it is addressed. If you are not the > intended recipient, you are not authorized to read, retain, copy, print, > distribute or use this message. If you have received this communication in > error, please notify the sender and delete all copies of this message. > Persistent Systems Ltd. does not accept any liability for virus infected > mails. >
