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:
2. Describe your environment:
OS Information: Ubuntu 22.04.3 LTS / Linux 6.5.0-1014-aws
Package Version: Graylog Server 5.0.13-1
Service logs, configurations, and environment variables:
3. What steps have you already taken to try and solve the problem?
Service restarts and address changes
4. How can the community help?
This is my first time trying to setup Graylog on a server and I’ve run into an issue. I’m towards the end of the process via these steps: Ubuntu installation
The issue I’m having is at the Edit the Configuration File Section, Step 3 (http biding address). I have it set as my server’s (Linux AWS EC2 Instance) Public IP address but unable to access the Graylog GUI via Google Chrome. I’ve tried restarting the services and also made sure to add a inbound rule for the 9000 port on the Security Group in AWS.
Just set the bind to 0.0.0.0:9000 AWS uses and internal address and translates it to external in most cases, plus your external could change under certain conditions.
Why does having the bind address 0.0.0.0:9000 in the server.conf file make the address of the Ubuntu server (in the 2nd screenshot) in Google Chrome work?
When I put http://0.0.0.0/9000 in the browser it doesn’t work as I would assume. Just trying to understand the logic trail. Thanks in advance!
Setting http://0.0.0.0:9000 you are allow that the graylog service can respond for any IP that the server has.
I suppose that if you consult the ip it set (ip -c address) no interface will have the ip 92.200.89.16
0.0.0.0 isn’t a true address it’s a special address that means all of any. So in this case listen on any interface that the machine has. In this case most likely whatever internal address AWS has assigned to that machine. what is 0.0.0.0 ip address? - DEV Community
