You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/12/22 19:23:00 UTC
[jira] [Commented] (NIFI-8265) S2S breaks in vanilla deployments
[ https://issues.apache.org/jira/browse/NIFI-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464015#comment-17464015 ]
David Handermann commented on NIFI-8265:
----------------------------------------
[~pvillard] With the changes in NiFi 1.14.0 to enable HTTPS as part of the default configuration, do you think this issue still warrants additional changes?
> S2S breaks in vanilla deployments
> ---------------------------------
>
> Key: NIFI-8265
> URL: https://issues.apache.org/jira/browse/NIFI-8265
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.0, 1.13.1
> Reporter: Pierre Villard
> Priority: Major
>
> Following NIFI-8221 we forced NiFi to have localhost as the default interface for HTTP. This breaks Site-to-Site with an out of the box deployment with no configuration change. If we take a reporting task and configure it to use
> {code:java}
> http://localhost:8080/nifi{code}
> the reporting task will fail indicating that it cannot connect to
> {code:java}
> http://<fqdn of host>:8080/nifi{code}
> I assume there is some hostname resolution happening here that is causing this issue. The recommended solution is definitely to have a secured deployment of NiFi. Last resort is to change the HTTP listen interface property to also listen on the FQDN interface.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)