I have reviewed this post but it is not helping:
Installing Nifi on Google Cloud Compute Engine
Here is what I have already done:
installed java 11 on ubuntu lts
installed nifi on ubuntu lts
This is what i have when i start the nifi.sh :
Java home: /usr/lib/jvm/java-1.11.0-openjdk-amd64
NiFi home: /usr/lib/nifi
Bootstrap Config File: /usr/lib/nifi/conf/bootstrap.conf
I have even tried to edit the nifi.properties by editing nifi.web.http.host and nifi.web.port
nifi.web.host=MY external ip from GCE
nifi.web.port=8080
I have even adjusted the Firewall settings and added port 8080(tcp) any my ip in IPRanges.
When I try to start the NIFI GUI it just does NOT load.
Can you please help me with that?
As per this doc can you cross check whether it is installed properly . Seems to be the default port for nifi is 8443. As you said changed to 8080, make sure that this port is not running in any other service and also there is no firewall blocking for this port.
open a web browser and navigate to https://localhost:8443/nifi or replace the port that you have changed and give it a try.
As per this SO, cross check whether the logs are listening or not by using logs/nifi-app.log. Share the screenshot if you are getting any errors.
Refer to this similar kind of issue : link1, link2, link3
Related
Problem:
I'm using apache nifi on ubuntu 18.04 on virtualbox 6.1. I manage to use apache nifi once without any problems. The log in page using localhost:8443 works the first time, but after a while when I start apache nifi again (e.g. after a reboot of the machine) and when I goto localhost:8443 again I do not get a page to log into nifi anymore.
All that appears are some symbols and I cannot log into nifi like the first time. Basically I want to be able to log into apache nifi. I'm not sure why the symbols appear instead of the log in page.
Here's what I do:
I start apache nifi-1.16.3 from its installation with its start command:
bin/nifi.sh start
bin/nifi.sh status
Nifi looks to start correctly and the status command shows that nifi is running
I then enter localhost:8443/nifi/login in firefox web browser and I am presented a page that only contains symbols.
What i've tried:
I've downloaded nifi again and started another instance using the fresh download. This does the same i.e. it will show the login page correctly the first time I use it. Then when I try to access the login page after a time via the localhost it will show the symbols instead of the log in page.
I've checked to see whether the port 8443 is being used by something else but it seems free. When nifi is running I check the port, then I shut it down. Once it is shut down no other service etc. is using port 8443. When trying to access localhost:8443 instead of the symbols it shows "Unable to connect" when nifi is shutdown down.
Not sure what else to explore to solve this issue where I can't access the log in GUI through the localhost.
Just add a secure HTTP protocol like this: Local Host
Good afternoon community,
I have the following problem, which will surely be silly, but I do not give with the key. I have a Debian 9 machine where I have ELK installed (Elasticsearch, Logstash and Kibana). It has been configured as it comes in the documentation. The installation versions correspond to the 6.x.
The services start correctly each and every one of them, the problem is when accessing the Kibana console through port 5601, when I access the browser and enter the url : 5601, I get a message that tells me the following "Kibana server is not ready yet"
I have not configured much more than what the official documentation says, so I do not understand why I do not lift the console to start configuring it.
Thanks in advance.
On my server I have installed elasticsearch-2.2.1 and couchbase server version 4.1.0. The aim is to transfer data from bucket x on couchbase to elastic search.
Ive installed the transport-couchbase plugin on elastic-search which will basically allow for xdcr from the server to elastic search.
As I understand it, transport-couchbase listens by default on port 9091 so in essence I'm supposed to create a cluster reference that points to that port (both couchbase and elastic search are installed on the same machine).
When I try create the reference I get an internal server error. The logs don't give me much information regarding the issue and I can ping the port. However when I try to telnet the machine on the port it refuses connection.
the server is sitting behind a proxy and i am starting to think that the issue lies within either couchbase server or elasticsearch ( transport-couchbase plugin)
Im going out on a limb here but I think maybe im supposed to configure the plugin so that it accepts requests going through tthe proxy. If this is the issue, is there a way to embed proxy settings into the plugin so that it can accept connections for xdcr?
PS: When I did this whole process on a separate machine that isnt sitting behind a proxy, everything worked fine. So I have a strong suspicion that it is proxy issues
If you can't telnet or browse to port 9091, this most likely indicates a network config issue. The plugin binds to the interface that elasticsearch binds to. The first thing to check is that the bind_host and publish_host in elasticsearch.yml is configured to bind to an interface that allows connections from wherever the proxy is located and that the proxy is really connecting on that interface.
There is a thread in github for the bug in transport plugin where it might not bind to all interfaces :
https://github.com/couchbaselabs/elasticsearch-transport-couchbase/issues/134
The above solutions didn't work for me, however I added this line:
-Djava.net.preferIPv4Stack=true
to /etc/elasticsearch/jvm.options and it seemed fixed the issue in my case
While i am trying to install the Apache service then It shows Service not install. How can i solve this problem?
xampp version:3.2.2enter image description here
That means that apache cannot be currently installed as a service. It happens because the system failed to start apache.
Try to run it pressing the start button, to see if you can get more details about the error.
One of the most common thing is that the port 80 (or the port you have configured to serve web) is being used by another application such as Skype.
In order to solve this, you have to close that application and stop all services using that port and configure the application or service to run in another port.
To see what process is using your port: How can you find out which process is listening on a port on Windows?
i hosted an apache server by changing few details in the httpd.conf file, used this tutorial. i also did port forwarding so that the server is able to respond behind the wireless router (firewall), it worked completely fine ( i checked by typing the ip and port number from some other host outside the network). now i am trying to run servlets for which i need tomcat server. i have installed tomcat but i am unable to access the server from another host that is not on the same network. could somebody please guide as to how can i achieve this.
I guess I would go with The Apache-Tomcat Connector and use it to connect your new tomcat instance to your Apache.
I did the same thing just as I for apache server, except that I changed the listening port to something else. added that entry in the router. incorporated tomcat in eclipse and then started the sample project. using whatismyip.com, i got the ip address. i could access my webserver from elsewhere...