Re: NIfi and Nifi Registry Connection Error

Usually the error "unable to find valid certification path to requested target" means that the truststore used by NiFi is not trusting the cert presented by NiFi Registry. You can check this by using keytool to inspect the keystores and truststores. On the NiFi server, use keytool to list the

Re: NIfi and Nifi Registry Connection Error

So now since I have restarted I am now getting an SSL error when trying to access my buckets this is the following stack trace from the nidi-user.log o.a.n.w.a.config.NiFiCoreExceptionMapper org.apache.nifi.web.NiFiCoreException: Unable to obtain listing of buckets:

Re: NIfi and Nifi Registry Connection Error

Ok, can you provide the stacktrace from nifi-app.log when it gets the socket timeout? On Wed, Mar 28, 2018 at 3:45 PM, Scott Howell wrote: > Yes I have https: defined on the registry client. > >> On Mar 28, 2018, at 2:29 PM, Bryan Bende wrote: >> >>

Re: NIfi and Nifi Registry Connection Error

Yes I have https: defined on the registry client. > On Mar 28, 2018, at 2:29 PM, Bryan Bende wrote: > > Just to double-check, when you defined the Registry Client in NiFi, > did you enter the URL starting with "https" ? > > On Wed, Mar 28, 2018 at 3:13 PM, Scott Howell

Re: NIfi and Nifi Registry Connection Error

Just to double-check, when you defined the Registry Client in NiFi, did you enter the URL starting with "https" ? On Wed, Mar 28, 2018 at 3:13 PM, Scott Howell wrote: > I have a single node nifi server setup with a self-signed keystone and > truststore. I then used the

NIfi and Nifi Registry Connection Error

I have a single node nifi server setup with a self-signed keystone and truststore. I then used the same self-signed cert to create a keystone and truststore for Nifi-Registry. Currently I am able to access the UI for both Nifi and Nifi-Registry securely while also seeing the correct