The whole point of sentry nodes is to relay information to your actual node.
So when someone tries to look for how your validator communicates; they will only see your sentry node and try to take it down. When they do this; another sentry node should take it’s place making it seem as if you changed your validators IP address.
but in reality you are just changing how the message gets from and to your validator.
This is an added level of security incase your Service Provider does not offer DDOS protection.
@ClaudioxBarros@kenorb yes as @l4zyboi has correctly pointed out. right now our validator nodes have port 26656 which is the p2p port to the public. that way it opens it up to ddos attacks.
having a sentry node allow any queries to be directed at the sentry nodes instead of your validator nodes.
you may set up more than 1 sentry node in different regions to have an added layer of security.
more information on how to set it up can be found here. and obviously your sentry node must be created in a different machine compared to your validator node.
I need help with configuring a node monitor.
Everything goes fine : I configured a monitor on a hardware (different than my node), setup my IP address, left default password.
But each time I open grafana’s “Fx Chain Dashboard”, all modules tell me “client_error : client error : 401”.
is this just grafana? did you set the target’s ip correctly? and also you can add users in the grafana user page. server admin–>username. yes make sure you do not copy and paste your password. its a salt hash
