*Dear Apache NiFi Support Team,* I am trying to set up Apache NiFi on a *Linux server using Docker*, but I am encountering an *"Invalid SNI" error* when attempting to access it.
>From my research, I understand that the issue is likely due to the *hostname used in the TLS certificates*, and the resolution would involve generating certificates with the *server’s hostname*. However, I am facing difficulties because the latest version of the *NiFi Toolkit(2.2.0) no longer includes tls-toolkit.sh*, which was previously used for certificate generation. The new CLI structure does not seem to provide a straightforward way to generate the necessary certificates for my setup. *I would appreciate your guidance on the following:* 1. *Certificate Generation:* What is the recommended approach for generating TLS certificates for a *Docker-based NiFi setup* on a Linux server, given that tls-toolkit.sh is no longer available? 2. *NiFi Setup Across the Organization:* I aim to have *NiFi running across the organization* for *validating data pipelines*. Could you provide best practices or recommended steps for setting up NiFi in an *enterprise environment* to ensure scalability, security, and ease of integration? Any documentation, examples, or guidance would be highly appreciated. Thank you for your time and support. *Best regards,* Anushree Shah
