NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WAX610 is offline within INSIGHT allthoug it works fine
Hi Community, since a few days I've got some problems with my WAX610 within Insinght. I've got two WAX610 now working for at least 2 months. I use Netgear Insight Management to manage the devices. Allmost one week ago a got an alert message that one of the devices is offline, although it works fine. A reboot doesn't helped. Now I got an alert message for the second device that that one is offline too. Both devices are working fine. I can reach them via browser, no problems. My network config: Both AP's behind a AVM Fritz!Box. I didn't change anything on the firewall or any other setting on my router. The only thing I changeged was the switch fro DNS to DNS over TLS on the router some days befor the first alert message. What have I done/tried: 1. after the first AP was marked as offline I rebootet it, without succcess 2. I logged in and tried to ping an URL, works fine 3. Looked into the logs and to google for some of the messages. But without success. 4. Changing back DNS over TLS to DNS without success Here is a snipping from my logs: Feb 18 14:32:22 cloudAgent[16395]: Agent : retry_count NEt:9546 Feb 18 14:32:22 cloudAgent[16395]: Agent : No Response for Health Thread Feb 18 14:31:47 cloudAgent[16395]: Agent : retry_count NEt:9545 Feb 18 14:31:47 cloudAgent[16395]: Agent : No Response for Health Thread Feb 18 14:31:12 cloudAgent[16395]: Agent : retry_count NEt:9544 Feb 18 14:31:12 cloudAgent[16395]: Agent : No Response for Health Thread Feb 18 14:30:37 cloudAgent[16395]: Agent : retry_count NEt:9543 Feb 18 14:30:37 cloudAgent[16395]: Agent : No Response for Health Thread Feb 18 14:30:02 cloudAgent[16395]: Agent : retry_count NEt:9542 Feb 18 14:30:02 cloudAgent[16395]: Agent : No Response for Health Thread ....... cloud log: ....... 2021-02-18 09:05:35 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 10:19:47 (17858):proxy.c:111 WARNING: openssl read result: '-1', error: '5', errno: '104'. 2021-02-18 10:19:47 (17858):xbroker_connection.c:476 ERROR: Connection to xbroker was closed. Sleeping for 60 secs. 2021-02-18 10:19:47 (17858):message_sender.c:301 INFO: Sent to handler 109 bytes. 2021-02-18 10:20:47 (17858):xbroker_connection.c:340 INFO: xbroker_host=xbroker-z1-i1.ngxcld.com, xbroker_port=443, using ssl=1 2021-02-18 10:20:48 (17858):message_sender.c:301 INFO: Sent to handler 108 bytes. 2021-02-18 10:32:50 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 10:57:46 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 11:03:02 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 11:13:28 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 11:24:05 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 13:14:19 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. 2021-02-18 14:08:09 (17858):message_sender.c:301 INFO: Sent to handler 65 bytes. Can anyone give me a hint to solve the problem?