<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Apache Nifi Invalid SNI in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/380501#M244071</link>
    <description>&lt;P&gt;Hello i just installed APACHE Nifi in Linux CentOS and for testing purposes i have this configuration in nifi.properties&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;lt;pre&amp;gt;nifi.web.https.host=127.0.0.1 nifi.web.https.port=8443 &amp;lt;/pre&amp;gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;I saw a solution from here saying that Jetty 10 doesn't accept IP address but instead hostnames, so what I did was to change etc/hosts to 127.0.0.1 -&amp;gt; nifi.local and used that nifi.web.https.host=nifi.local for the configuration of the nifi.properties file. I run in browser&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://nifi.local:8443/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://nifi.local:8443&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and i get the same error:( Can someone assist please?&lt;/P&gt;&lt;P&gt;`&lt;STRONG&gt;HTTP ERROR 400 Invalid SNI URI: /nifi STATUS: 400 MESSAGE: Invalid SNI SERVLET: - CAUSED BY: org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Caused by:&lt;/P&gt;&lt;P&gt;org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:266) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:207) at org.eclipse.jetty.server.HttpChannel$RequestDispatchable.dispatch(HttpChannel.java:1594) at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:753) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:501) at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:461) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:969) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1194) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1149) at java.base/java.lang.Thread.run(Thread.java:1583)&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2023 16:44:55 GMT</pubDate>
    <dc:creator>Vas</dc:creator>
    <dc:date>2023-12-07T16:44:55Z</dc:date>
    <item>
      <title>Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/380501#M244071</link>
      <description>&lt;P&gt;Hello i just installed APACHE Nifi in Linux CentOS and for testing purposes i have this configuration in nifi.properties&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;lt;pre&amp;gt;nifi.web.https.host=127.0.0.1 nifi.web.https.port=8443 &amp;lt;/pre&amp;gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;I saw a solution from here saying that Jetty 10 doesn't accept IP address but instead hostnames, so what I did was to change etc/hosts to 127.0.0.1 -&amp;gt; nifi.local and used that nifi.web.https.host=nifi.local for the configuration of the nifi.properties file. I run in browser&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://nifi.local:8443/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://nifi.local:8443&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and i get the same error:( Can someone assist please?&lt;/P&gt;&lt;P&gt;`&lt;STRONG&gt;HTTP ERROR 400 Invalid SNI URI: /nifi STATUS: 400 MESSAGE: Invalid SNI SERVLET: - CAUSED BY: org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Caused by:&lt;/P&gt;&lt;P&gt;org.eclipse.jetty.http.BadMessageException: 400: Invalid SNI at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:266) at org.eclipse.jetty.server.SecureRequestCustomizer.customize(SecureRequestCustomizer.java:207) at org.eclipse.jetty.server.HttpChannel$RequestDispatchable.dispatch(HttpChannel.java:1594) at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:753) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:501) at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:461) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:969) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1194) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1149) at java.base/java.lang.Thread.run(Thread.java:1583)&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 16:44:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/380501#M244071</guid>
      <dc:creator>Vas</dc:creator>
      <dc:date>2023-12-07T16:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/380502#M244072</link>
      <description>&lt;P&gt;Just to update on what I use. Is latest Nifi 2.0 with Java 21. I double tripled check the nifi.properties file and straight out of the box the keystorep12 and truststorep12 files seem correct. I tried many combinations of IP addresses in the&amp;nbsp;&lt;SPAN&gt;nifi.web.https.host field including raw adresses and hostnames but nothing works for me.. If someone with more experience could help me i would greatly appreciate it!&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 16:48:07 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/380502#M244072</guid>
      <dc:creator>Vas</dc:creator>
      <dc:date>2023-12-07T16:48:07Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385226#M245655</link>
      <description>&lt;P&gt;did you find a solution ?&amp;nbsp;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/108241"&gt;@Vas&lt;/a&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 08:42:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385226#M245655</guid>
      <dc:creator>darkcoffeelake</dc:creator>
      <dc:date>2024-03-20T08:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385233#M245658</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In 2.0 , the only thing that worked specially if you use out of the box ssl configuration is placing localhost in nifi.web.https.host property. To use the machine FQDN you need to configure new ssl truststore and keystore against that domain.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 09:11:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385233#M245658</guid>
      <dc:creator>SAMSAL</dc:creator>
      <dc:date>2024-03-20T09:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385278#M245671</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/108241"&gt;@Vas&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;The straight out of the box generated keystore and truststore will not have "nifi.local" as a SAN entry.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;You could generate your own keystore and truststore with needed SAN entry(s).&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "&lt;SPAN&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;FONT color="#FF0000"&gt;Accept as Solution&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/EM&gt;" on one or more of them that helped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you,&lt;BR /&gt;Matt&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 19:14:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/385278#M245671</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2024-03-20T19:14:54Z</dc:date>
    </item>
    <item>
      <title>Re: Apache Nifi Invalid SNI</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/388136#M246547</link>
      <description>&lt;OL&gt;&lt;LI&gt;How to Resolve SNI issue when upgrading to NiFi 2.0&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;A href="https://medium.com/@chnzhoujun/how-to-resolve-sni-issue-when-upgrading-to-nifi-2-0-907e07d465c5#:~:text=Due%20to%20the%20upgrade%20to,400%3A%20Invalid%20SNI%20will%20occur" target="_blank" rel="noopener"&gt;https://medium.com/@chnzhoujun/how-to-resolve-sni-issue-when-upgrading-to-nifi-2-0-907e07d465c5#:~:text=Due%20to%20the%20upgrade%20to,400%3A%20Invalid%20SNI%20will%20occur&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 07:57:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-Invalid-SNI/m-p/388136#M246547</guid>
      <dc:creator>saquibsk</dc:creator>
      <dc:date>2024-05-21T07:57:35Z</dc:date>
    </item>
  </channel>
</rss>

