provided updates to allow specification of the various ports in the container on startup via varying environment variables to aid the issue of the host whitelisting. NIFI-4824
It does not appear this information is readily available in our docs and has caused some confusion by users when trying to connect to an instance. We need to update the docs to enumerate these scenarios as well as the environment variables that are anticipated.
We could additionally enhance the experience via performing some logical checks. One example could be verifying that if a custom port is set and we are running secure, there is also an environment variable provided. Additionally, providing variables that would be unused, such as NIFI_WEB_HTTP_PORT when we are running secure could also cause an error/warning.