Graylog: Troubleshooting: a Graylog input doesn't work

This documentation is part of the Configure inputs guide. View the full guide here: How to configure Graylog inputs.

👋 Welcome to Stackhero documentation

Stackhero provides a fully managed Graylog cloud solution designed for speed and simplicity. You can:

• Rely on an unlimited, dedicated SMTP email server included with your service.
• Apply updates effortlessly with a single click, with no manual intervention needed.
• Use a custom domain name secured by HTTPS (for example, https://logs.your-company.com), giving your team secure, direct access.
• Experience strong performance and security on a private, dedicated infrastructure with no shared resources or noisy neighbors.

Focus on your data, not your tooling: you can get started with Stackhero's Graylog cloud hosting solution in just a few minutes.

If a Graylog input does not work as expected, review the following checklist:

1. On the Graylog web UI:

   1. Go to System then Inputs and confirm that the input is running.
   2. Verify the protocol (UDP or TCP) is correct.
   3. If using TCP, ensure that tls_enable is set to false since encryption is managed on the Stackhero dashboard.
   4. Confirm that the port is correct.
   5. Verify that the data format is accurate (GELF, CEF, RAW or Syslog).

2. On the Stackhero dashboard:

   1. Select your Graylog instance and click the Configure button.
   2. In the Input ports list, ensure that the port is defined with the proper protocol (UDP or TCP).
   3. If using TCP, confirm that the TLS option is enabled for encryption (SSL/HTTPS).

3. On the firewall:

   1. In the Stackhero dashboard, select your Graylog instance and click on the Firewall tab.
   2. Ensure there is a rule accepting traffic for the input port and protocol. If you want to allow any IP, set the IP field to 0.0.0.0/0.

By following this checklist, there should be no reason for the input to fail.