elasticsearch升级后出现kibana 3 Could not contact Elasticsearch
2016-12-27 14:51
260 查看
在升级了最新的elasticsearch1.5之后,原来的kibana 3提示无法连接到elasticsearch的9200端口,“kibana 3 Could not contact Elasticsearch”
解决方法:在elasticsearch的配置文件config/elasticsearch.yml下添加:
http.cors.allow-origin: “/.*/”
http.cors.enabled: true
重启elasticsearch,kibana3可以访问了,解决
解决方法:在elasticsearch的配置文件config/elasticsearch.yml下添加:
http.cors.allow-origin: “/.*/”
http.cors.enabled: true
重启elasticsearch,kibana3可以访问了,解决
相关文章推荐
- elasticsearch升级后出现kibana 3 Could not contact Elasticsearch
- Cloudera Manager 安装时出现socker gaierror[error -2] name or service not know 或者could not contact scm ser
- ads 编译时出现(Fatal)L6002U:Could not open file 的解决办法
- linux安装Vmware的时候出现“Could not open /dev/vmmon”
- MYSQL安装出现could not start the service mysql error:0处理
- cxf客户端调用webservice,出现问题 Found element arg0 but could not find matching RPC/Literal part
- 使用ftp.storlines进行文件上传时出现553 Could not create file.的解决方法
- Plsql Developer连接Oracle时出现Could not initialize oci.dll解决方案
- IOS研发之路-Xcode7.1真机调试出现"Could not find Developer
- Open edXDevstack启动出现:could not connect to localhost:27017: [Errno 111] Connection refused.
- maven项目出现如下错误,求指点;CoreException: Could not calculate build plan:
- linux安装mysql出现Could NOT find Curses (missing CURSES_LIBRARY CURSES_INCLUDE_PATH),提示解决方法
- 真机调试出现Could not find Developer Disk Image问题解决办法
- Myeclipse出现:Could not create the view: An unexpected exception was thrown.
- 简单方法解决设置IBOutlet变量时中出现的“Could not insert new outlet connection”
- ODP.NET 开发 出现 ORA-12154: TNS:could not resolve the connect identifier specified 错误
- "Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased."
- 安装MSSQL2012 出现 "the windows installer service could not be accessed"
- Nhibernate出现NHibernate.QueryException: could not resolve property异常
- eclipse 调试时出现!MESSAGE Could not find bundle: org.eclipse.equinox.console解决办法