Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on 12-20-2024 10:08 AM - edited 12-20-2024 10:18 AM
Created on 12-22-2024 07:33 AM - edited 12-22-2024 07:35 AM
@Emery
I think this should resolve your problem, change the nifi.web.https.host and shown below so it binds to all network interfaces, allowing access from other machines in your intranet
Browser Trust for Self-Signed Certificates
Solution:
Please let me know if that helped
Happy hadooping
Created on 12-20-2024 10:16 AM - edited 12-20-2024 10:16 AM
Hi,
Is the host name defined in the DNS? If not then use the IP address or machine FQDN instead.
Created on 12-20-2024 10:30 AM - edited 12-20-2024 10:35 AM
Created on 12-22-2024 07:33 AM - edited 12-22-2024 07:35 AM
@Emery
I think this should resolve your problem, change the nifi.web.https.host and shown below so it binds to all network interfaces, allowing access from other machines in your intranet
Browser Trust for Self-Signed Certificates
Solution:
Please let me know if that helped
Happy hadooping
Created 12-22-2024 12:39 PM
Hi Shelton,
Thanks very much for your help. I think this may be working. I'm going to continue testing it with the few of us who require access, but for now it's working from different browsers from my laptop. I had the certificates set up correctly from the start, and this setting seems to have done the trick.
Thanks again for your reply and assistance!