Elasticsearch Cluster 2019(2)Kibana Issue or Upgrade
程序员文章站
2022-03-30 19:23:52
...
Elasticsearch Cluster 2019(2)Kibana Issue or Upgrade
Recently, our Kibana get error messages as follow:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'nonce-6l5WfCDQyGKomWFe'". Either the 'unsafe-inline' keyword, a hash ('sha256-SHHSeLc0bp6xt4BoVVyUy+3IbVqp3ujLaR+s+kSP5UI='), or a nonce ('nonce-...') is required to enable inline execution.
Solution:
Currently, I do not know. My Elasticsearch and Kibana Versions are 7.2.1
Try to upgrade the Kibana version to 7.5.1
> wget https://artifacts.elastic.co/downloads/kibana/kibana-7.5.1-linux-x86_64.tar.gz
> tar zxvf kibana-7.5.1-linux-x86_64.tar.gz
> mv kibana-7.5.1-linux-x86_64 ~/tool/kibana-7.5.1
> sudo ln -s /home/elastic/tool/kibana-7.5.1 /opt/kibana-7.5.1
> sudo ln -s /opt/kibana-7.5.1 /opt/kibana
Edit the configuration file
> vi config/kibana.yml
server.host: "els.sillycat2.com"
server.basePath: "/kibana"
elasticsearch.hosts: ["http://els.sillycat3.com:9200"]
The kibana-7.5.1 does not help, we still need kibana-7.2.1, but we need the server.basePath there. And we need to update our nginx settings as well.
location /kibana/ {
proxy_pass http://els.sillycat2.com:5601/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
}
It works pretty well.
References:
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html
Nginx proxy to kibana
https://segmentfault.com/q/1010000011782771
https://www.cnblogs.com/yanjieli/p/11187689.html
https://discuss.elastic.co/t/nginx-reverse-proxy-setup-for-kibana/167327/5
Recently, our Kibana get error messages as follow:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'nonce-6l5WfCDQyGKomWFe'". Either the 'unsafe-inline' keyword, a hash ('sha256-SHHSeLc0bp6xt4BoVVyUy+3IbVqp3ujLaR+s+kSP5UI='), or a nonce ('nonce-...') is required to enable inline execution.
Solution:
Currently, I do not know. My Elasticsearch and Kibana Versions are 7.2.1
Try to upgrade the Kibana version to 7.5.1
> wget https://artifacts.elastic.co/downloads/kibana/kibana-7.5.1-linux-x86_64.tar.gz
> tar zxvf kibana-7.5.1-linux-x86_64.tar.gz
> mv kibana-7.5.1-linux-x86_64 ~/tool/kibana-7.5.1
> sudo ln -s /home/elastic/tool/kibana-7.5.1 /opt/kibana-7.5.1
> sudo ln -s /opt/kibana-7.5.1 /opt/kibana
Edit the configuration file
> vi config/kibana.yml
server.host: "els.sillycat2.com"
server.basePath: "/kibana"
elasticsearch.hosts: ["http://els.sillycat3.com:9200"]
The kibana-7.5.1 does not help, we still need kibana-7.2.1, but we need the server.basePath there. And we need to update our nginx settings as well.
location /kibana/ {
proxy_pass http://els.sillycat2.com:5601/;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
}
It works pretty well.
References:
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html
Nginx proxy to kibana
https://segmentfault.com/q/1010000011782771
https://www.cnblogs.com/yanjieli/p/11187689.html
https://discuss.elastic.co/t/nginx-reverse-proxy-setup-for-kibana/167327/5