Skip to content
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

invalid configuration for xpack.security.transport.ssl when installing ElasticSearch 8.x #100

Open
nahall opened this issue Feb 22, 2024 · 3 comments
Labels

Comments

@nahall
Copy link

nahall commented Feb 22, 2024

I'm trying to use this Ansible role to install ElasticSearch 8.x. When ElasticSearch tries starting it dies with an error:

org.elasticsearch.ElasticsearchSecurityException: invalid configuration for xpack.security.transport.ssl - [xpack.security.transport.ssl.enabled] is not set, but the following settings have been configured in elasticsearch.yml : [xpack.security.transport.ssl.keystore.secure_password,xpack.security.transport.ssl.truststore.secure_password] at org.elasticsearch.xpack.core.ssl.SSLService.validateServerConfiguration

It appears that some additional configuration needs to be done for 8.x in order to get it to run.

Copy link

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label Jun 23, 2024
@profadminuniserviss
Copy link

profadminuniserviss commented Jun 28, 2024

@nahall Did you figure out whats missing?

EDIT:
Adding
xpack.security.transport.ssl.enabled: false
xpack.security.http.ssl.enabled: false
to extra options solved it for my case.

@github-actions github-actions bot removed the stale label Jun 30, 2024
Copy link

github-actions bot commented Nov 3, 2024

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants