Lakshman, The NiFi System Administrator's Guide section on Proxy Configuration [1] provides some important configuration details for running NiFi behind a proxy server.
Of particular note, the proxy server must pass the public port number using the X-Proxy-Port header, which NiFi will use to generate appropriate redirect URLs. It is also important to note that the unofficial Docker image does not support running NiFi with plain HTTP, so HTTPS is required. You may build your own container image with customized startup if plain HTTP is desired, but the project recommends HTTPS for all deployments. Regards, David Handermann [1] https://nifi.apache.org/nifi-docs/administration-guide.html#proxy_configuration On Mon, Sep 1, 2025 at 11:26 AM Lakshman Gupta <[email protected]> wrote: > > The Issue seems resolved when we use port 80 instead of 8443. > > Any pointers to make it work with custom port will be greatly appreciated. > > ________________________________ > From: Lakshman Gupta <[email protected]> > Sent: Monday, September 01, 2025 19:41 > To: [email protected] <[email protected]> > Subject: Port number getting appended to the openshift route > > 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.
