@Cl0ck I see nothing you listed as having been removed as an issue. NiFi will create all of the following on startup if they do not exist: - All 4 repository directrories (content, flowfile, database, and provenance) and their contents provided the NiFi service user has permsissions to configured directory to do so. - flow.xml.gz - local state directory and its contents - users.xml (if needed based on authorizers.xml configuration) - authorizations.xml (if needed based on authorizers.xml configuration) I would start by digging in to your shutdown exception: java.lang.IllegalStateException: no valid keystore You'll want to get a verbose listing of your keystore and make sure the following exists: 1. Keystore contains only one PrivateKeyEntry 2. That PrivateKeyEntry has ExtendedKeyUsage (EKU) that supports both clientAuth and ServerAuth 3. That PrivateKeyEntry has one or more SubjectAlternativeName (SAN) entries. One of those SAN entries must match the hostname of the server on which this keystore is being used. 4. The password on the key inside the keystore must use the same password as the keystore itself. A verbose output of your truststore should show that it contains 1 or more TrustedCertEntry Also make sure that your NiFi service users owns and can navigate to the directory where the keystore and truststore files have been placed. Hope this helps, Matt
... View more
