NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
netdata NT not working
installed this app on my 2120 v2 and pro 6 running with xeon quad 3230 with firmware 6.5.1 both got error message showing "" Service Temporarily Unavailable The server is temporarily unable...
cpu8088 wrote:""
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.31 (Debian) Server at 192.168.1.xx Port 443""
amazz20 wrote:
Looking at the syslog while turning the app on I get:
400699 Date Today 22:45:12 Host Ezekiel Messagetype Syslog Syslogtag apache2 ProcessID 22660 Message [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1 
:19999 (localhost) failedThe Apache web server is responsible for proxying requests to netdata so that you can go to https://NAS/apps/nastools-netdata instead of http://NAS:19999, and use the ReadyNAS user list for authentication. Those errors mean that Apache can't connect to netdata.
Running systemctl status fvapp-nastools-netdata via SSH should give a good clue as to what's going on. Do either of you have IPv6 disabled by any chance?
cpu8088 wrote:""
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.31 (Debian) Server at 192.168.1.xx Port 443""
amazz20 wrote:Looking at the syslog while turning the app on I get:
400699 Date Today 22:45:12 Host Ezekiel Messagetype Syslog Syslogtag apache2 ProcessID 22660 Message [error] (111)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1
The Apache web server is responsible for proxying requests to netdata so that you can go to https://NAS/apps/nastools-netdata instead of http://NAS:19999, and use the ReadyNAS user list for authentication. Those errors mean that Apache can't connect to netdata.
Running systemctl status fvapp-nastools-netdata via SSH should give a good clue as to what's going on. Do either of you have IPv6 disabled by any chance?
ipv6 was disabled
now enabled under network and netdata NT is working
thanks
cpu8088 wrote:ipv6 was disabled
now enabled under network and netdata NT is working
I thought that might be it. I have the default configuration of netdata set to listen on IPv6 loopback, which should listen on IPv4 loopback as well. Shouldn't need to have IPv6 enabled. I'll look into it.
whilst this netdata NT is working on both 2120 v2 arm cpu and pro6 with xeon quad, i noticed that under system overview the disk read should be disk write and disk write should be disk read?
if the system overview showing disk temp cpu temp, motherboard temp, fan speed would be ideal
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
