pfelk / docker

Deploy pfelk with docker-compose
Apache License 2.0
56 stars 20 forks source link

Logstash 401 Unauthorized errors #39

Closed impovich closed 1 year ago

impovich commented 2 years ago

New installation. I see 401 Unauthorized error in logs. Also, Kibana asks for credentials.

To Reproduce Steps to reproduce the behavior:

  1. Install
  2. check logs
    logstash    | [WARN ] 2022-04-26 11:28:56.121 [Ruby-0-Thread-10: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-11.4.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:213] elasticsearch - Attempted to resurrect connection to dead ES instance, but got an error {:url=>"https://pfelk_logstash:xxxxxx@es01:9200/", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :message=>"Got response code '401' contacting Elasticsearch at URL 'https://es01:9200/'"}

Screenshots If applicable, add screenshots to help explain your problem.

Operating System (please complete the following information):

Elasticsearch, Logstash, Kibana (please complete the following information):

Additional context Add any other context about the problem here.

a3ilson commented 2 years ago

@AlexanderHamza

impovich commented 2 years ago

@a3ilson 1) yes 2 and 3) they were set by default as:

    user => "pfelk_logstash"
    password => "pf31k-l0g$tas#-p@sSw0Rd"
a3ilson commented 2 years ago

Odd...My setup is the same except I'm running Ubuntu Server v20.04. Let me install a fresh instance of v22.04 and see if I can replicate the issue - might be later on in the week when I have time to get around to it.

impovich commented 2 years ago

@a3ilson

Please take a look at this once you get your hands on the issue:

Screenshot at Apr 26 15-24-13
a3ilson commented 2 years ago

@impovich this issue should be mitigated with the #40 Fix provided by @braunbearded

Please confirm/close

impovich commented 2 years ago

Hi, @a3ilson I will check and provide you with feedback, thank you for the notification.