-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Will not install on v2.3.91~WARNING~ WILL overwrite your Fireweall and TPM Filebeat Local files!!!!!!!!!!!!!!!!! #8
Comments
[2022-01-17T00:00:06,512][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error {:url=>"https://xxx.xxx.xxx.205:9200/", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :message=>"Got response code '401' contacting Elasticsearch at URL 'https://xxx.xxx.xxx.205:9200/'"} |
Thanks, I am aware of this issue and will have a look. In the meantime, I have updated the Logstash config file, here: Please keep in mind, this is not an officially supported integration, so using is it at your own risk and should not be done with a production system at this time. I'll be updating this repo very soon to improve stability, etc. |
Although this fixed the issue with authentiaction. ( thank you ) |
Indexes have not populated since installing Velo.. PLEASE HELP
The text was updated successfully, but these errors were encountered: