I understand this is a dumb question, but i have seen this happen often enough i have to ask, you are sure that you didnt get password and secret switched up in server.conf right?
Thank you! That was my bad i did get a new issue now. For some reason I’m getting this notification even if i put is_leader = true and running on a single-node
Hey @mouse1122 ,
The error banner does not disappear by itself. Did it come back when you “deleted” it?
Did you apply the server changes by restarting the graylog-server.service?
Greetings
check the Node-ID
node_id_file: …
look at the file. Are the permissions correct, does the file exist?
To be sure you can delete the id and let graylog create a new one: sudo rm /etc/graylog/server/node-id sudo systemctl restart graylog-server
Check MongoDB connection
Check Cluster-Status curl -X GET http://localhost:9000/api/system/cluster
Try following:
You change the default port 9000 to a different for example 8080
And you use for the bin address a wildcard address
Publish and external stay your fqdn or ip http_bind_address = 0.0.0.0:8080 http_publish_uri = http://yourip:8080/ http_external_uri = http://yourip:8080/
possibly check your firewall settings
do you have asccess to your api?
fqdn/ip and port are the same to access the web ui http://<fqdn/ip>:<port>/api/api-browser/
Okay, here I am again, I installed Graylog 6 by myself and set it up like in the manual. https://go2docs.graylog.org/current/downloading_and_installing_graylog/installing_graylog.html?tocpath=Installing%20Graylog|_____0
It worked absolutely fine…
I can only assume that maybe your connection to MongoDB on port 27017 (TCP) is sometimes failing, this could be a firewall or routing problem if you are not using the loopback address. I dont know if its possible but you can try to do a TCP dump on that port or change the Mongo URI in your Server.conf.