![]() ![]() 08:50:33,068 WARN .server.JettyServer Failed to start web server. Check the nifi.properties file and ensure that either the HTTP hostname and port or the HTTPS hostname and port are empty 08:50:33,066 WARN .server.JettyServer HTTP connector: 08:50:33,066 WARN .server.JettyServer HTTPS connector: 08:50:33,066 ERROR .server.JettyServer NiFi only supports one mode of HTTP or HTTPS operation, not both simultaneously. See the NiFi Admin Guide for more details Only one of these connectors should be configured. 08:50:33,066 WARN .server.JettyServer Both the HTTP and HTTPS connectors are configured in nifi.properties. Not if I just list the content of that folder.Īfter the build, I ran a new container ( docker run -name my_nifi -p 19443:19443 -d my_nifi and even adding -e NIFI_WEB_HTTPS_PORT='19443' is the same) and tried to enter it and manually cpīut at the restart of this second container I get this ERROR: 08:50:33,022 INFO .log Logging initialized to .log.Slf4jLog Says that the files have been copied in the conf/ folder, they are In STEP 5-6, I see the problem that even though the cp command In STEP 3 I use the NiFi tls-toolkit to create the jks keys and the new nifi.properties file, but: '/opt/nifi/nifi-current/localhost/nifi.properties' -> '/opt/nifi/nifi-current/conf/nifi.properties' '/opt/nifi/nifi-current/localhost/keystore.jks' -> '/opt/nifi/nifi-current/conf/keystore.jks' STEP 5: RUN cp -fv /opt/nifi/nifi-current/localhost/* /opt/nifi/nifi-current/conf/ nifi-current/CN=user_1_OU=NiFi.p12Ġ 08:38:17 INFO .: Successfully generated client certificate. nifi-current/localhostĠ 08:38:16 INFO .: Generating new client certificate. nifi-current/localhostĠ 08:38:16 INFO .: Successfully generated TLS configuration for localhost 1 in. nifi-current/nifi-key.keyĠ 08:38:16 INFO .: Writing new ssl configuration to. ![]() nifi-currentĠ 08:38:16 INFO .: Generated new CA certificate. STEP 3: RUN /opt/nifi/nifi-toolkit-current/bin/tls-toolkit.sh standalone -n "localhost" -C "CN=user_1, OU=NiFi"Ġ 08:38:15 INFO .: No nifiPropertiesFile specified, using embedded one.Ġ 08:38:16 INFO .: Running standalone certificate generation with output directory. ![]() RUN cp -fv /opt/nifi/nifi-current/localhost/* /opt/nifi/nifi-current/conf/ # :19443/nifiĭockerfile build docker build -t my_nifi -no-cache. RUN /opt/nifi/nifi-toolkit-current/bin/tls-toolkit.sh standalone -n "localhost" -C "CN=user_1, OU=NiFi" I have created my simple testing Dockerfile: FROM apache/nifi:latest I want to use the port 19443 now, but eventually I will be using the 9443. I want to secure my NiFi with HTTPS using the tls-toolkit in standalone mode inside a Docker container, on a remote virtual machine running RHEL 8 (so actually using Podman instead of Docker but using a podman-docker module, I can treat podman as a Docker). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |