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

Use the same LetsEncrypt certificate for all the parts of the ELK Stack #3

Open
WendelNevesWider opened this issue Nov 26, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@WendelNevesWider
Copy link

First of all thank you very much for your work, this helped a lot to get a start on using Elastic.

I´ve ran into a problem, it seems that when using the Lets Encrypt option to generate the scripts, the system sets the certificate for https right, but the certificate for kibana when using Elastic Agent is another one, pointing only to localhost, kibana and 0.0.0.0.

I would like to be able to use the same certificate file that works from Lets Encrypt instead of this localone from kibana.

Thank you very much for your attention,

@joshswimlane joshswimlane added the enhancement New feature or request label Nov 28, 2020
@joshswimlane joshswimlane self-assigned this Nov 28, 2020
@joshswimlane
Copy link
Contributor

Thanks for pointing this out! I’ll take look next week and will submit a PR as soon as I can! Thanks!

@joshswimlane
Copy link
Contributor

@WendelNevesWider i did look into this and I currently don’t see (or know) a way to do this. I’ll keeping looking & reach out to Elastic if needed but I’m stuck currently. If you have any luck finding this info let me know please!

@Und3rf10w
Copy link

Is it possible to use a wildcard certificate from LetsEncrypt for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants