You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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,
The text was updated successfully, but these errors were encountered:
@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!
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,
The text was updated successfully, but these errors were encountered: