# Graylog Open with self-signed certificate

**URL:** <https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254>\
**Category:** Graylog Central (peer support)\
**Created:** [March 18, 2025, 5:01pm UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254 "2025-03-18T17:01:32Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mstjohn2](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mstjohn2](https://community.graylog.org/u/mstjohn2)\
**Post date:** [March 18, 2025, 5:01pm UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/1 "2025-03-18T17:01:32Z")

</div>

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.  
**Don’t forget to select tags to help index your topic!**

**1. Describe your incident:**  
I am in the process to setup a demo with graylog open and I already got the WebUI working with a self-signed certificate but I am having issues to make it work for secured input for my syslog servers. When I tail the /var/log/graylog-server/server.log I am seeing a lot of the following message:

2025-03-18T10:56:07.120-06:00 WARN [ProxiedResource] Failed to call API on node \<27552e57-a257-47ff-a9da-263519580deb\>, cause: None of the TrustManagers trust this certificate chain. (duration: 198 ms)

I generated this self-signed certificate on this same host where graylog is running on. Like I mentioned it is working alright for the WebUI

**2. Describe your environment:**

- OS Information:  
I am running this on a Red Hat 9.5 VM

- Package Version:  
graylog-6.1-repository\_latest.rpm

- Service logs, configurations, and environment variables:

**3. What steps have you already taken to try and solve the problem?**

**4. How can the community help?**  
How can I make it work with a self-signed certificate? Is it even possible?

**Helpful Posting Tips:** [Tips for Posting Questions that Get Answers](https://community.graylog.org/t/tips-for-posting-questions-that-get-answers/21828) [Hold down CTRL and link on link to open tips documents in a separate tab]

---

<div class="post-metadata">

**Author:** ![Wine\_Merchant](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/wine_merchant/32/14596_2.png) [@Wine\_Merchant](https://community.graylog.org/u/Wine_Merchant)\
**Post date:** [March 19, 2025, 9:48am UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/2 "2025-03-19T09:48:31Z")

</div>

The certificate probably needs to be added to the trust store, [following this guide](https://graylog.org/post/how-to-guide-securing-graylog-with-tls/) should help explain the complete process.

---

<div class="post-metadata">

**Author:** ![mstjohn2](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mstjohn2](https://community.graylog.org/u/mstjohn2)\
**Post date:** [March 20, 2025, 6:54pm UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/3 "2025-03-20T18:54:14Z")

</div>

I followed this guide and even created cert and key, also imported our local networks CA Root and intermediate Certs etc…nothing is working. I cannot even get a unsecured syslog port 514/udp or 10514/udp up and running. There is seriously something wrong with the install/config but i dont know where to start to troubleshoot it. Any ideas?

---

<div class="post-metadata">

**Author:** ![Wine\_Merchant](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/wine_merchant/32/14596_2.png) [@Wine\_Merchant](https://community.graylog.org/u/Wine_Merchant)\
**Post date:** [March 21, 2025, 9:22am UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/4 "2025-03-21T09:22:34Z")

</div>

@mstjohn2

The below error suggests that while the WebUI is secure, the Graylog node is unable to make api calls to itself. It explicitly says that a certificate trust chain is missing from your keystore. Is this a Docker setup?

`2025-03-18T10:56:07.120-06:00 WARN [ProxiedResource] Failed to call API on node <27552e57-a257-47ff-a9da-263519580deb>, cause: None of the TrustManagers trust this certificate chain. (duration: 198 ms)`

Regarding inputs, you should be able to send logs if an input has not been secured. Are the inputs in a running state? As the node can’t call itself it might be that it’s unable to start the inputs.

Not to keep throwing guides at you [but this “Hardening” course](https://academy.graylog.org/course/hardening-graylog-with-tls) was recently released and covers securing inputs and goes into mutual auth.

---

<div class="post-metadata">

**Author:** ![mstjohn2](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mstjohn2](https://community.graylog.org/u/mstjohn2)\
**Post date:** [March 21, 2025, 1:37pm UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/5 "2025-03-21T13:37:10Z")

</div>

Well, I followed this installation guide: [Red Hat Installation: Single Graylog Node](https://go2docs.graylog.org/current/downloading_and_installing_graylog/red_hat_installation.htm)  
and used this one for adding my root and intermediate Certs as well as my generated cert with key  
[https://graylog.org/post/how-to-guide-securing-graylog-with-tls/](https://graylog.org/post/how-to-guide-securing-graylog-with-tls/)

---

<div class="post-metadata">

**Author:** ![mstjohn2](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@mstjohn2](https://community.graylog.org/u/mstjohn2)\
**Post date:** [March 25, 2025, 3:39pm UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/6 "2025-03-25T15:39:57Z")

</div>

Well, I couldnt get it to work properly with my certs, even with adding them to the keystore etc. I ended up removing all TLS stuff and got it to work insecure for now and will tackle TLS to a later point

---

<div class="post-metadata">

**Author:** ![reckless](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/reckless/32/17810_2.png) [@reckless](https://community.graylog.org/u/reckless)\
**Post date:** [April 5, 2025, 12:52am UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/7 "2025-04-05T00:52:17Z")

</div>

How did you remove all the TLS stuff like you said, what exactly did you do?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [April 19, 2025, 12:52am UTC](https://community.graylog.org/t/graylog-open-with-self-signed-certificate/35254/8 "2025-04-19T00:52:21Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
