Jim,
You're welcome! Thanks for following up and confirming the solution, great
collaborative effort!
Regard,
David Handermann
On Tue, Nov 8, 2022, 7:25 PM James McMahon wrote:
> That was it. Adding the port to the docker run command proxy got me to the
> promised land. I was then able to
That was it. Adding the port to the docker run command proxy got me to the
promised land. I was then able to use the userid and password from the
docker log to access nifi on my ec2 instance.
David, Dmitry - thank you so much. This was a huge help to me, and I hope
it will help others trying the
Yes sir, I did. I used the full public domain name.
On Tue, Nov 8, 2022 at 8:08 PM Dmitry Stepanov wrote:
> Make sure you use your full domain name
> ec2-3-238-27-220.compute-1.amazonaws.com
> David shorten it in his code
>
> On November 8, 2022 5:57:26 p.m. James McMahon
> wrote:
>
>> Thank
It may also be necessary to include the port in the host variable:
docker run --name nifi -p 8443:8443 -e NIFI_WEB_PROXY_HOST=
ec2-3-238-27-220.compute-1.amazonaws.com:8443 -d apache/nifi:latest
It is possible to access the configuration and logs files using an
interactive shell with the
Make sure you use your full domain name
ec2-3-238-27-220.compute-1.amazonaws.com
David shorten it in his code
On November 8, 2022 5:57:26 p.m. James McMahon wrote:
Thank you, David. I’ve made that change, adding the proxy host
specification on the docker command line. I continue to get the
Thank you, David. I’ve made that change, adding the proxy host
specification on the docker command line. I continue to get the same error
message. Is it possible I need to indicate my key on the docker command
line too?
Related, how can one access nifi.properties and the usual nifi config
files,
Hi Jim,
Good adjustment on the security group inbound rules.
The error page is the result of NiFi receiving an unexpected HTTP Host
header, not matching one of the expected values.
For this to work, it is possible to pass the external DNS name as the value
of the NIFI_WEB_PROXY_HOST environment
Hi David. This is very helpful, thank you. I feel like I am close, but I
get an error. My Inbound Rules for my security group now include:
8443 TCP (MyIP)/32
443 TCP (MyIP)/32
22 TCP (MyIP)/32
In my browser - I tried both Edge and Chrome - I use this
URL:
> won't render if you're using Edge or IE to access.
The old, discontinued Edge had that problem, but Edge has worked just
fine for the last 2 years or so since it was redone on top of
Chromium.
IMO if you're going to use Chromium with NiFi, the best experience
seems to be Brave.
On Tue, Nov 8,
Hi Jim,
Thanks for the reply and additional background.
The instructions are dated March 2021, which is prior to the release of
NiFi 1.14.0. In particular, the run command is no longer accurate with the
default NiFi container image.
The current Docker Hub instructions [1] show the basic command
Hi and thank you, David and Dmitry. In my case I was following this
example,
https://joeygoksu.com/software/apache-nifi-on-aws/
which results in NiFi installed within a container. So to answer one of
your questions, I don’t yet know how or where to find nifi.properties in
the container
In addition to the other suggestions, the last time I checked, the HTML5
of the NiFi interface won't render if you're using Edge or IE to
access. Brave, Chrome, Firefox etc will work, however.
On 11/8/2022 1:53 PM, James McMahon wrote:
Has anyone successfully configured NiFi on AWS, and
We did.
Since NiFi is HTTPS by default (recent versions) you need to open ports
8443 or 443(default HTTPS)
Try opening those and see what happens
Cheers,
Dima Stepanov
Hi Jim,
NiFi 1.14.0 and following default to HTTPS on port 8443, listening on the
localhost address. The nifi.web.https.host can be changed to blank in order
to listen on all interfaces, but the default HTTPS setting with
authenticated required should be retained.
Can you provide the version of
Has anyone successfully configured NiFi on AWS, and accessed it from a
browser on a Windows desktop? I’ve tried following a few links to do this.
I’ve verified that my instance security group allows access to 8080 via its
inbound rules. I’ve putty’ed into the instance via ssh port 22 to verify
There is also some upgrade/migration guidance on the NiFi Wiki [1].
It hasn’t been reviewed/updated recently, so if you have any feedback that
would be much appreciated.
Thanks,
Drew
[1] https://cwiki.apache.org/confluence/display/NIFI/1.x.0+to+1.x.0+Upgrade
Hi HORNEMAN,
What I have done is the first option you mentioned, "move the users.xml and
authorizations.xml files to the new instances and then add the instances
manually”
The reason of this is that the authorizations for instances are just a few
while authorization for users could be a lot
Hello
I am currently trying to migrate users and their rights from a NiFi 1.13.2
cluster to a NiFi 1.16.3 cluster on new servers. What are the steps to
follow to keep the old users with the new configuration ?
Should I move the users.xml and authorizations.xml files to the new
instances and then
18 matches
Mail list logo
