![]() Note: will be generated by the Docker container at startup and can then be viewed. Or (which is the recommended way) we can declare the location of the Elasticsearch certificate: curl -u elastic: -cacert /usr/share/elasticsearch/certs/ca/ca.crt For this there are two simple solutions, namely firstly bypassing the certificate locally (not recommended, but working): curl -u elastic: -k The problem is quite clear: we try to establish a secure connection without specifying the Elastic username and a key. But if we now change the connection settings to https, the next error will occur and logging on to Elasticsearch will fail again: curl: (60) Peer's Certificate issuer is not recognized. Is then almost self-explanatory: our connection attempt happened with http and not https ( because this Docker container uses secured TLS connections). The error curl: (52) Empty reply from server You will not be able to connect with a simple CURL command because of the TLS encryption. If you log into the Elasticsearch container via docker exec -it elasticsearch /bin/bash Again, Elastic uses self-signed certificates. This happens, for example, if you have the official elastic-stack via Docker. The default port of Elasticsearch is Port 9200: curl However, you can or should setup Elasticsearch with TLS and a certificate. ![]() ![]() If you want to connect to Elasticsearch from the Linux command line, you can do that with CURL, for example.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |