<?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 Access Dockerized NiFi UI from remote host in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Access-Dockerized-NiFi-UI-from-remote-host/m-p/225016#M186879</link>
    <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to stand up a temporary NiFi server to support a proof of concept demo for a customer. For these types of short lived servers I like to use Docker when possible. I'm able to get the NiFi container up and running with out any issues but I can't figure out how to access its UI from the browser on a remote host. I've tried the following docker run variations:&lt;/P&gt;&lt;P&gt;&lt;CODE&gt;docker run --name nifi \
  -p 8080:8080 \
  -d \
  apache/nifi:latest&lt;/CODE&gt;&lt;/P&gt;&lt;HR /&gt;
&lt;P&gt;&lt;CODE&gt;docker run --name nifi \
  -p 8080:8080 \
  -e NIFI_WEB_HTTP_PORT='8080' \
  -d \
  apache/nifi:latest&lt;/CODE&gt;&lt;/P&gt;&lt;HR /&gt;
&lt;P&gt;&lt;CODE&gt;docker run --name nifi \
  -p 8080:8080 \
  -e NIFI_WEB_HTTP_HOST=${hostname-here} \
  -e NIFI_WEB_HTTP_PORT='8080' \
  -d \
  apache/nifi:latest&lt;/CODE&gt; &lt;/P&gt;&lt;P&gt;My NiFi version is 1.8.0. I'm fairly certain that my problems are related to the host-headers blocker feature added to version 1.5.0. I've seen a few questions similar to mine but no solutions. Is it possible to access the NiFi UI from a remote host after version 1.5.0? Can host-headers blocker be disabled for a non-prod demo? Would a non-Docker install on my server present the same host-headers blocker issues? Should a use 1.4 for my demo and save myself a headache&lt;/P&gt;</description>
    <pubDate>Tue, 30 Oct 2018 02:39:19 GMT</pubDate>
    <dc:creator>reynoldsblair</dc:creator>
    <dc:date>2018-10-30T02:39:19Z</dc:date>
  </channel>
</rss>

