I have a problem with connecting to Elasticsearch under proxy settings. I have installed Bigdesk plugin manually with bin/plugin -DproxyHost=myproxy.proxy.com -DproxyPort=80 --install lukas-vlcek/bigdesk, everything went all right with it.
I run my Elasticsearch on docker, it generated some private IP.
After http://[GeneratedIP]:9200/_plugin/bigdesk/ I have error 504, Proxy Timeout in web browser console.
After running ElasticSearch locally with service elasticsearch start and then in browser http://localhost:9200/_plugin/bigdesk/ it stops loading and I can see just white screen, no output in inspect-console.
Any ideas?
Related
I have downloaded the Elasticsearch 8.1 in my Ubuntu. After successful installation, when I execute
curl -u elastic https://127.0.0.1:9200 -k
It is showing expected elasticsearch response. But when I hit http://127.0.0.1:9200/ or http://localhost:9200 in my browser, it is returning
After installation, I added network.host: 127.0.0.1 to elasticsearch.yml
Can anybody help me, why it is not running in browser ?
I am using Ubuntu 20 OS & following this Doc
As of version 8.0, Elasticsearch security is turned on by default and SSL/TLS is required for HTTP communications.
You can disable HTTP security if you want, but that's discouraged.
I am using the windows platform, the steps are the same. When you run the elasticsearch.bat in cmd
use this port for elasticsearch HTTPS secure https://localhost:9200/
check the username and password scroll down the cmd running elasticsearch
After login into the elasticsearch. Hurry...
Thanks
But
the best solution is to use Docker Image of ELK stack which is easy instead of downloading the E L K and then run on the local machine.
I had installed x-pack earlier and used it, and hosted Kibana through Nginx.
I yesterday uninstalled x-pack from both elasticsearch and kibana, via
sudo bin/elasticsearch-plugin remove x-pack
and
sudo bin/kibana-plugin remove x-pack
Now, when I try to start elastic, elastic is started, but Kibana does not start when I start kibana.
The Kibana.stdout log says,
{"type":"log","#timestamp":"2017-04-27T06:23:39Z","tags":["info","optimize"],"pid":49497,"message":"Optimizing and caching bundles for kibana, timelion and status_page. This may take a few minutes"}
And Kibana is never started.
The sudo service kibana status says it is running, but sudo netstat -ntlp, I can not find the port 5601.
It is never started. Why so ?
What can be the possible issue ?
Try deleting the kibana/optimize/bundles directory as well as the kibana/optimize/.babel-cache.json file and restarting Kibana. That will trigger a completely fresh rebuild of the Kibana source without x-pack.
Note: If you're using kibana as a system daemon, run the kibana process through the command line once to re-compile the optimize bundle before starting the daemon.
./usr/share/kibana/bin/kibana
I created a new AWS account and started a new tier 2 instance. So I did following things afterward :
Created elastic IP and associated it with the instance.
Configured the inbound security groups for http, https and custom TCP rule:8080
Installed tomcat7 using "sudo yum install tomcat7"
Started tomcat using "sudo service tomcat7 start"
Finally, i tried to check the tomcat, by hitting http://elastic-ip:8080 from the browser but a blank page comes up.
I guess this is a 404 error. Please help me which part have i missed.
I'm not able to access marvel in my browser.
http://localhost:9200/_plugins/marvel/ returns
{"error": "ElasticsearchIllegalArgumentException[No feature for name [marvel]]","status": 400}
I have installed elastic search 1.7.1 and its up and running running at http://localhost:9200/
I'm running on a window 2008R2 server with chrome and java 1.7.0_79
I did (and tried) the following things:
I installed the marvel plugin marvel (marvel-latest.zip). The
folder marvel folder is created in the plugins folder
The log shows the plugin is started ([INFO ][plugins ]
[MY_01_dev] loaded [marvel], sites [marvel])
tried giving in teh path to the index page manually (http://localhost:9200/_plugins/marvel/_site/kibana/index.html#/dashboard)
Changed the config with: marvel.agent.exporter.es.hosts: localhost:9200
No luck so far, all commands with cURL seems to work, but as much as I'm fond of command lines, my colleagues aren't, so i realy would like to get the plugin up and running
The url is not with _plugins, but with _plugin (singular):
http://localhost:9200/_plugin/marvel/kibana/index.html#/dashboard/file/marvel.overview.json
Marvel and sense plugin should be installed to Kibana and then access it using marvel agent on elastic node.
https://stackoverflow.com/a/33732567/1013528
I am using wamp for 2 years, but now it is giving an error
HTTP Error 404. The requested resource is not found.
on running localhost and phpmyadmin.
I tried the following:
Restarted all services.
Downloaded and installed again
Checked that no other program was using port 80.
skype is not running.
In services wampmysqld is running but wampapache is not running.
Tried to run service manually and it says
Windows could not start the wampapache on local computer.
Do you have any solution for this?
The wampserver shows the status of online and its color is orange.
Before the error occurred it was green.