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:
Graylog is not binding to the new IP which is changed to 10.35.19.94 from 10.35.4.20
2. Describe your environment:
OS Information: RHEL 9.6
Package Version: Graylog 6.1
Service logs, configurations, and environment variables:
Graylog conf:
I did a tail -f /var/log/graylog-server/server.log
That error is just the certificate complaining that it’s not valid, which is true. It looks like the hostname being presented starts with graylogtest.ucs However the certificate was only set up for graylog.ucs, so its not trusting it. It may have failed back to the IP before since that was also listed, but now that you changed the IP you broke that way to verify the cert.
You will probably want to recreate the certs, which you can do by getting back into the preflight wizard.
You can do this by adding enable_preflight_web = true to server.conf and restart graylog, you will then need to get the temporary login credentials from the end of your server.log file.
Then once you recreate those certs you can remove the line from server.conf to go back to normal operations.
TL;DR: you need to recreate your certs between datanode and graylog.
