-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to configure for JUST allowing LAN IP visit web monitor dashboard? #2067
Comments
Hi, could you please post the |
[web] Okay, this is my web section configuration. |
It says "bing to", not "bind to". |
one way to check your config is to get it from netdata: http://your.netdata.ip:19999/netdata.conf |
Wow, I'm so sorry, thanks ktsaou a lot! |
I was wondering monitor all of my servers, so I chose a server as public visit interface through a sub domain URL, because I used Nginx proxy to protect my real server IP and port information, and I wanted to not allowed anyone visit readIP:PORT to monitor netdata dashboard.
My information as bellow:
SERVER1(Nginx server):
WAN IP: 120.xx.xx.xx
REAL SERVER1(target monitor server):
WAN IP: 121.xx.xx.xx
LAN IP: 10.xx.xx.xx
Nginx configuration:
server{
port 80;
host www.xyz.com;
location /monitor/ {
proxy_pass http://10.xx.xx.xx:19999/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
then I have configured "bind to = 10.xx.xx.xx" in '/etc/netdata/netdata.conf' on REAL SERVER1, then I restarted netdata service, but I could still visit througth 121.xx.xx.xx:19999. I want anyone just can visit it through
so, anyone who knows anywhere I configured error? thanks!!!
The text was updated successfully, but these errors were encountered: