@Ghilani  The Invalid SNI is caused by the server certificate presented in the TLS exchange not containing a SubjectAlternativeName (SAN) matching the hostname in the request URL. Valid SAN entries are required by the latest version of Java. The solution is to issue new certificates for your NiFi instance(s) that contain all possible SANs used when connecting to the NiFi. So you should have a SAN entry for you NiFi hostname as well as any alternative names used in connection URLs like "nifi" coming form your proxy to NiFi. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@Matt  Thank you so much this has been a big help! ... View more

@AbhiTryingAgain Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@ose_gold Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

@ayu_dev  Welcome to the Cloudera Community. Please start a new Cloudera Community question rather then adding a new thread on an existing question from over a year ago.  You'll get much better traction there.  Your query is unrelated to the original question in this thread around log rotation and retention policies. Fell free to ping me in your new community question and I'll be happy to take a look. Thank you, Matt ... View more

@Shampy  You are saying that with no flow.json.gz file present, NIFi throws above exception on startup.  With No flow.json.gz file, NiFi will create one during startup. I also suggest using the official Apache NiFi 2.x release and stop using the pre-release Maintenance releases that were put out during development of NiFi 2.x.  There were 4 maintenance (M1 - M4) releases put out before the first official release of Apache NiFi 2.0.0. The latest official release ofd Apache NiFi 2.x is NiFi 2.2.0 which can be downloaded from here: https://nifi.apache.org/download/ Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@mslnrd  While kind of related, to prevent confusing other community members, it would be better to start a new community question for this.  This question involves proper authorizers.xml configuration and the new question is specific to user-group-provider configuration.  Feel free to ping me in that new question so I get notified when it is created. Thank you, Matt ... View more

Based on the initial input in the question, slightly adapted the following seems to work for me (1.27.0) docker run --rm --name nifi -p 8080:8080 \ -e NIFI_WEB_HTTP_PORT=8080 \ -e NIFI_WEB_HTTPS_PORT= \ -e NIFI_WEB_HTTPS_HOST= \ -e NIFI_SECURITY_KEYSTORE= \ -e NIFI_SECURITY_KEYSTOREPASSWD= \ -e NIFI_SECURITY_KEYPASSWD= \ -e NIFI_SECURITY_TRUSTSTORE= \ -e NIFI_SECURITY_TRUSTSTOREPASSWD= \ apache/nifi:1.27.0 --- --- from container nifi@xxxxxxxxxxxx:/opt/nifi/nifi-toolkit-current/bin$ ./cli.sh _ ___ _ Apache (_) .' ..](_) , _ .--. __ _| |_ __ )\ [ `.-. | [ |'-| |-'[ | / \ | | | | | | | | | | ' ' [___||__][___][___] [___]', ,' `' CLI v1.27.0 Type 'help' to see a list of available commands, use tab to auto-complete. Session loaded from /home/nifi/.nifi-cli.config #> nifi get-root-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ... View more

Thank you ... View more

Hi Matt, This is the error, we receive in the log: Thanks, Amit. ... View more