There have been some changes recently, and NiFi is now secure by default
with a self-signed cert I believe. It could be that NIFI_WEB_HTTP_PORT
conflicts with the expected NIFI_WEB_HTTPS_PORT.
Try this:
nifi:
image: apache/nifi:latest
ports:
- "8443:8443" # UI
- "10000" # Site-to-Site Input Port
environment:
SINGLE_USER_CREDENTIALS_USERNAME: admin
SINGLE_USER_CREDENTIALS_PASSWORD: some_password
NIFI_SENSITIVE_PROPS_KEY: some_other_password
If that does not work, can you please share the exact startup error?
On Feb 16, 2022 at 09:28:55, Jean-Sebastien Vachon <[email protected]>
wrote:
> Hi all,
>
> I'm trying to start a simple unsecured Nifi instance in a container as
> part of a larger docker compose stack and I'm stuck with an error regarding
> the TLS configuration and/or keystore properties. Here is the relevant part
> of my docker-compose file... what am I missing? Please make me feel stupid
> 😉
>
> nifi:
> image: apache/nifi:latest
> # command:
> ports:
> - "8080:8080"
> - "10000:10000"
>
> restart: always
> command:
> /bin/bash
> environment:
> NIFI_REMOTE_INPUT_HOST: 0.0.0.0
> NIFI_WEB_HTTP_HOST: 0.0.0.0
> SINGLE_USER_CREDENTIALS_USERNAME: admin
> SINGLE_USER_CREDENTIALS_PASSWORD: some_password
> NIFI_WEB_HTTP_PORT: 8080
> AUTH: none
>
>
>
>
>
> *Jean-Sébastien Vachon *
> Co-Founder & Architect
>
>
> *Brizo Data, Inc. www.brizodata.com
> <https://outlook.office365.com/mail/options/mail/messageContent/www.brizodata.com>
> *
>
