# Help please with using HTTPS on clustered Graylog

**URL:** <https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004>\
**Category:** Graylog Central (peer support)\
**Created:** [May 2, 2017, 12:11pm UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004 "2017-05-02T12:11:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![David83](https://avatars.discourse-cdn.com/v4/letter/d/22d042/32.png) [@David83](https://community.graylog.org/u/David83)\
**Post date:** [May 2, 2017, 12:11pm UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/1 "2017-05-02T12:11:36Z")

</div>

Hello,  
I need help with using HTTPS on clustered Graylog please.  
According to manual below I created certificate and keys (cert.pem, pkcs5-plain.pem , pkcs8-encrypted.pem, pkcs8-plain.pempkcs5-plain.pem) in path /etc/graylog/server/certificates/.  
[http://docs.graylog.org/en/2.2/pages/configuration/https.html?highlight=https](http://docs.graylog.org/en/2.2/pages/configuration/https.html?highlight=https)

On first node I configured required parameters:

```auto
rest_enable_tls = true
rest_tls_cert_file = /etc/graylog/server/certificates/cert.pem
rest_tls_key_file = /etc/graylog/server/certificates/pkcs8-encrypted.pem
rest_tls_key_password = {password_used_for_pkcs8-encrypted.pem}
web_enable_tls = true
web_tls_cert_file = /etc/graylog/server/certificates/cert.pem
web_tls_key_file = /etc/graylog/server/certificates/pkcs8-encrypted.pem
web_tls_key_password = {password_used_for_pkcs8-encrypted.pem}

```

Graylog doesn’t work after restart:

```auto
[root@xxxx certificates]# /etc/init.d/graylog-server status
● graylog-server.service - Graylog server
   Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2017-05-02 14:02:48 CEST; 3s ago
     Docs: http://docs.graylog.org/
  Process: 7255 ExecStart=/usr/share/graylog-server/bin/graylog-server (code=exited, status=1/FAILURE)
 Main PID: 7255 (code=exited, status=1/FAILURE)

```

```auto
[root@xxxx certificates]# sudo tailf /var/log/graylog-server/server.log | grep -i exception
com.github.joschi.jadconfig.ValidationException: Unreadable or missing REST API private key: /etc/graylog/server/certificates/pkcs8-encrypted.pem

```

Can you help me with this issue please?

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [May 2, 2017, 1:38pm UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/2 "2017-05-02T13:38:58Z")

</div>

Are all files readable for the system user running the Graylog process? All directories leading to the file must be readable for that user, too.

You can check this with `namei -l /etc/graylog/server/certificates/pkcs8-encrypted.pem` etc.

What’s the content of the exception you’ve posted? (Lines before and after the actual exception)

---

<div class="post-metadata">

**Author:** ![David83](https://avatars.discourse-cdn.com/v4/letter/d/22d042/32.png) [@David83](https://community.graylog.org/u/David83)\
**Post date:** [May 3, 2017, 10:18am UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/3 "2017-05-03T10:18:41Z")

</div>

Hello,  
thank you a lot, there was really problem with access rights which I resolved and both Graylog nodes running well now.

---

<div class="post-metadata">

**Author:** ![Labidi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/labidi/32/5597_2.png) [@Labidi](https://community.graylog.org/u/Labidi)\
**Post date:** [April 4, 2019, 8:21am UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/4 "2019-04-04T08:21:55Z")

</div>

![problem%20service](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/c/cb9f8df07862da028cb2d334caf7758b1d4e32ff.png)

please @jochen i have the same problem

---

<div class="post-metadata">

**Author:** ![Labidi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/labidi/32/5597_2.png) [@Labidi](https://community.graylog.org/u/Labidi)\
**Post date:** [April 4, 2019, 8:27am UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/5 "2019-04-04T08:27:55Z")

</div>

> [@David83](#):
>
> sudo tailf /var/log/graylog-server/server.log | grep -i exception

 ![Exception](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/e/e59ef664c0509fdc77cec4e70feb65bc2a2fe028.png)

---

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [April 4, 2019, 8:33am UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/6 "2019-04-04T08:33:44Z")

</div>

1. Do not re-use old threads for different version in your behalf
2. read your logs yourself - the reason is written cleary in your screenshot
3. random shouting to people will not help you!
4. we - the community are not your sparing partner that helps you to do your work.
5. use your brain.

---

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [April 4, 2019, 8:33am UTC](https://community.graylog.org/t/help-please-with-using-https-on-clustered-graylog/1004/7 "2019-04-04T08:33:55Z")

</div>

Closed on April 4, 2019, 8:33am UTC