@XP-Mai I used “```” at the beginning and at the end of the block to show my iptables, probably if you also add them, you will be able to plot firewall output here.
Yes, Akismet prevented me from posting even though I enclosed it with triple backticks. Maybe it got to do with the length of the message. Because overall it’s quite long.
@XP-Mai I am assuming that your iptables output is different of my output, this means that you have a firewall running, so you will need to enable connections to port 19999 to access from outside your network.
@XP-Mai I used “```” at the beginning and at the end of the block to show my iptables, probably if you also add them, you will be able to plot firewall output here.
@Mai-Vu-Tan considering that you have success to access it locally, this means that probably you have a firewall blocking requests to port 19999 that comes from outside the machine. You can confirm this running the command iptables -L and iptables -L -t nat . If you see something different of :
@Mai-Vu-Tan , this is a successful request. When you ran curl on terminal, it got the html code and prints it on screen, this happens because the terminal cannot convert this for a web page.
I would suggest starting the investigation by using curl to try and fetch the dashboard from inside the VM: curl HTTP://localhost:19999. If it works, then for some reason Netdata can not be accessed by another machine. Then, we could look into whether Netdata itself has this restriction (by looking at the configuration) or whether AWS EC2 needs some configuration to allow inbound access. Chances are that if you are using netdata default configuration, then netdata is accessible by any machine, so it must be EC2 specific.
BTW, Welcome to our community! Thank you for posting your questions and be sure to stick around and help a user or two if you happen to have any insight on their questions. We would love to see you how you use netdata