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 have graylog-enterprise running using nginx proxy but its graylog-datanode in port 9200 has appearing not secure url and Authentication finally failed in web ui
2. Describe your environment:
OS Information: CentOS
Package Version: Stream 9
Service logs, configurations, and environment variables:
Authentication finally failed for null from [IP host]
3. What steps have you already taken to try and solve the problem?
modify opensearch in config file location of datanode = unsolved
modify datanode config related to certificate and authentication = unsolved
4. How can the community help?
Please help to assist me on what file path needs to modify/fix the authenticated finally failed and its not secured url ? or is that a normal running gui of graylog-datanode integrated opensearch?
Hi @Joel_Duffield
Appreciate your response,
I’m trying to secure the web of datanode or do i need to secure it? Addionally, it appears Authentication finally failed its that a normal web interface of datanode? Please help thanks in advance
There is no web interface of datanode just some api endpoints that only the graylog server talks to. As long as you went through preflight then that connection is already secured.
Noted on this I have running graylog-server but how about the message on port 9200? it says authentication finally failed do I need to do something to be authenticated when I access the port?
Thanks in advanced
When datanode is setup during preflight, it is setup to use certificates it generates as authentication, so the only way to access it is to generate a certificate for 3rd part access whixh yiu can do in the graylog UI
