# Graylog 3.0.2 https

**URL:** <https://community.graylog.org/t/graylog-3-0-2-https/11594>\
**Category:** Graylog Central (peer support)\
**Tags:** sidecar\
**Created:** [August 14, 2019, 7:15pm UTC](https://community.graylog.org/t/graylog-3-0-2-https/11594 "2019-08-14T19:15:03Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![cbgraham](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@cbgraham](https://community.graylog.org/u/cbgraham)\
**Post date:** [August 15, 2019, 10:36pm UTC](https://community.graylog.org/t/graylog-3-0-2-https/11594/7 "2019-08-15T22:36:51Z")

</div>

Here is what I have tried numerous times already. I really don’t want to admit the amount of time I’ve spent on this.

[https://docs.graylog.org/en/3.0/pages/configuration/https.html#creating-a-self-signed-private-key-certificate](https://docs.graylog.org/en/3.0/pages/configuration/https.html#creating-a-self-signed-private-key-certificate)  
combined with  
[https://docs.graylog.org/en/3.0/pages/configuration/https.html#adding-a-self-signed-certificate-to-the-jvm-trust-store](https://docs.graylog.org/en/3.0/pages/configuration/https.html#adding-a-self-signed-certificate-to-the-jvm-trust-store)  
Which seems like the right combination to get the cert, and add it the java trust store, but maybe it’s not what you are supposed to do?  
I used the resultant cert.pem and pkcs8-encrypted.pem as the certificates in my server.conf.  
Result: didn’t work

I tried the steps in [Graylog3 with https (easy tutorial)](https://community.graylog.org/t/graylog3-with-https-easy-tutorial/9519)  
But I had to modifiy a couple things at the end which seemed to overwrite some steps that were previously done. There is a confusing array of .jks files in the final steps with 3 different jks files. I imagine they were typos referencing actually just 1 jks file?

Greg, I noticed your helpful response you have 2 different jks files, did you end up with 2, or was that just a typo? Also, I thought the jks default password was changeit and if you changed it from that you have to add another java opt to set the password?

I might have to end up going with the nginx solution here:

> [@Graylog SSL Certificates](https://community.graylog.org/t/graylog-ssl-certificates/8100/3):
>
> you might find this part of the documentation helpful: [http://docs.graylog.org/en/2.5/pages/secure/sec\_graylog\_beats.html](http://docs.graylog.org/en/2.5/pages/secure/sec_graylog_beats.html)

if this doesn’t work, but I’m really trying to use the graylog built https method.

---

_[View the full topic](https://community.graylog.org/t/graylog-3-0-2-https/11594)._