Member since
08-27-2024
5
Posts
5
Kudos Received
0
Solutions
12-27-2024
10:27 AM
1 Kudo
If you're using the docker image it's just a matter of voluming in your customized version of the start.sh or copying it in at image build time. But I can understand not wanting to do that. It should be completely configurable with env variables. It seems like that's how it worked in nifi 1.X
... View more
12-23-2024
07:33 AM
2 Kudos
I've found that you have to modify the start.sh script itself rather than relying on passed environment variables. By default it will apply the host name of the container to the https host unless you prevent it from doing so in the start.sh script. Which then takes precedent over any http configuration you've done. I'd also try messing with `nifi.remote.input.secure` I'm uncertain if that is also required to be set to false
... View more
12-05-2024
02:23 PM
1 Kudo
I'm running Nifi in ECS with an ALB. Everything is up and seems normal except there are intermittent 502 errors that pop up in the Nifi ui that look like this It seems that the source of the 502 is the load balancer but since it's intermittent it seems like an interaction between the load balancer and Nifi that is causing this behavior. I've tried messing with the following settings so that the idle timeout (60 seconds) on the ALB is lower nifi.web.request.timeout nifi.remote.input.http.transaction.ttl I've also made sure the nifi.web.proxy.host configuration is set the hostname that I'm using to hit the loadbalancer. Has anyone else experienced something similar getting a load balancer in front of Nifi?
... View more
Labels:
- Labels:
-
Apache NiFi
11-25-2024
01:55 PM
1 Kudo
So it turns out if you "unset" the following properties in the start.sh script like so, you are able to run nifi without tls nifi.security.keystore nifi.seucrity.keystoreType nifi.security.truststore nifi.security.truststoreType
... View more
11-25-2024
08:08 AM
I'm currently trying to get Nifi running in docker in the insecure mode without tls enabled. The reason for this is I want to run Nifi with ssl termination upstream and not have to deal with the complications of having to manage truststores and keystores. By default it seems that even configuring the environment variables for `nifi_web_http_port` and `nifi_web_http_host` will not remove the default configuration for the https port and host. I've modified the start.sh script for the container to set the http_port and http_host to be the expected values and removing the default values for https_port and https_host. I've also set the configuration `nifi.remote.input.secure` to be false. Now on startup Nifi failing to load a Key Store at ./conf/keystore.p12. Even with tls seemingly disabled by the means I've found necessary from all other guides on the matter Nifi is still expecting a keystore? Has anyone had success with running nifi 2.0 insecure in docker?
... View more
Labels:
- Labels:
-
Apache NiFi
-
Security