Andrew Arz

seeing this same problem

status of the following commands sudo docker ps docker-compose logs elasticsearch docker-compose logs kibana You can also do: docker-compose logs -f elasticsearch kibana and then attempt to login and view...

sorry run docker logs containername so docker logs lme_elasticsearch docker logs lme_kibana youll need the full name so copy it from under the 'names' column when you do docker ps

also you said here you're using ELK 5? Software Versions: ELK: 5.15.0-101-generic if you do a cat docker-compose-stack-live.yml can you confirm the versions are actually 8.11.1?

also for further troubleshooting -- from your windows machine do the following ssh -L 443:localhost:443 linuxmachineusername@linuxmachineipaddress After you have successfully logged into the linux machine - in your browser on...

You need the entire container name. from when you do 'docker ps' you need to copy and paste the entire container name it will look like lme_elasticsearch then lots of...

so basically what we want to see is what logs are generated when we attempt to login So you can do sudo docker logs -f {containername} and monitor live --...

@markofsuccess Do you have any kind of network security like a firewall / proxy etc that does ssl termination / inspection of your network traffic? If that doesn't have this...

> @markofsuccess Hey, I think I had the same problem, I was not getting any logs aswell. > > I solved this problem by removing my old certificates and regenerating...

also run: openssl verify -CAfile certs/root-ca.crt certs/elasticsearch.crt openssl verify -CAfile certs/root-ca.crt certs/kibana.crt Both should come back OK and also ensure the certs on your windows machine that youre importing into...