question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

https://localhost:5601/app/kibana: status: Error

See original GitHub issue

@Crazybus

I installed the helm chart o elasticsearch an kibana using alright_keep_your_secrets branch. it seems that everything worked just fine until I wanted to get into the UI of kibana it doesn’t load :

the make goss seems to be working without issue :

GOSS_CONTAINER=$(kubectl get --no-headers=true pods -l release=helm-kibana-security -o custom-columns=:metadata.name | sed -n 1p ) && \
echo Testing with pod: $GOSS_CONTAINER && \
kubectl cp test/goss.yaml $GOSS_CONTAINER:/tmp/goss.yaml && \
kubectl exec $GOSS_CONTAINER -- sh -c "cd /tmp/ && curl -s -L https://github.com/aelsabbahy/goss/releases/download/v0.3.6/goss-linux-amd64 -o goss && chmod +rx ./goss && ./goss --gossfile goss.ya
ml validate --retry-timeout 300s --sleep 5s --color --format documentation"
Testing with pod: helm-kibana-security-kibana-778dfcf8f9-p29zh
File: /usr/share/kibana/config/kibana.yml: exists: matches expectation: [true]
File: /usr/share/kibana/config/kibana.yml: contains: matches expectation: [server.ssl:   enabled: true   key: /usr/share/kibana/config/certs/elastic-certificate.pem   certificate: /usr/share/kiba
na/config/certs/elastic-certificate.pem xpack.security.encryptionKey: elasticsearch.ssl:   certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem   verificationMode: certi
ficate]
HTTP: https://localhost:5601/app/kibana: status: matches expectation: [200]
HTTP: https://helm-kibana-security-kibana:5601/app/kibana: status: matches expectation: [200]
Total Duration: 0.963s
Count: 4, Failed: 0, Skipped: 0

this is my pods :

NAME                                            READY   STATUS    RESTARTS   AGE
helm-kibana-security-kibana-778dfcf8f9-p29zh    1/1     Running   0          14h
security-master-0                               1/1     Running   0          14h
security-master-1                               1/1     Running   0          6h40m
security-master-2                               1/1     Running   0          12m

in the events log I am seing this warning : **Failed to update endpoint default/security-master: Operation cannot be fulfilled on endpoints "security-master": the object has been modified; please apply your changes to the latest version and try again | FailedToUpdateEndpoint**

but then my security-master pods are working :

security-master-0 |  running security-master-1 |  running security-master-2 | running

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:17 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
Crazybuscommented, Jul 19, 2019

Thank you for following up! I’m really happy that you got it working!

1reaction
mounaBoocommented, Jul 19, 2019

Thank you again for your kind help.

I wish I could get to your level of knowledge.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cannot access Kibana on port 5601 - Elastic Discuss
If I do curl http://127.0.0.1:5601, I get empty response, nothing, no error. Error log in /var/log/ doesnt exist. Few starting infos: curl 127.0.0.1:9200:...
Read more >
Kibana Not working at http://localhost:5601 URL
First make sure that you are using elasticsearch 1.5 and make sure you have started it by pointing your browser to. http://localhost:9200.
Read more >
Kibana cannot be accessed through port 5601 in browser
With the help of @user9517 asking if I'm aware that localhost and 127.0.0.1 (the same in the context of external connections in this...
Read more >
How To Install Elasticsearch, Logstash, and Kibana (Elastic ...
curl -fsSL https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo ... to the Kibana application, which is listening on localhost:5601 .
Read more >
Kibana server is not ready yet
This error could be due to different reasons: · Let's look at some logs to find out the origin of the problem: ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found