NWA90AX + NWA50AX reboot via "Wireless Auto Recovery" almost exactly every 17 hours

Options
ChristianW
ChristianW Posts: 9
First Comment First Anniversary
image  Freshman Member
edited November 4 in Nebula

Hey everyone,

I've been chasing down an intermittent WiFi mesh issue for a few weeks now (3x AP setup, 1 NWA90AX as root + 2x NWA50AX as mesh repeaters, Nebula-managed) and finally dug deep enough into the event logs to find a pattern I can't explain myself, so I figured I'd post it here before opening a ticket.

Quick setup rundown: NWA90AX is the main router, wired via Gbit LAN. One NWA50AX repeater is also wired via Gbit LAN. The second NWA50AX repeater connects via wireless mesh backhaul to the NWA90AX (no LAN cable available up there). All three are on the latest firmware as of an update I did on Oct 22.

What I'm seeing is:

Both the NWA90AX and the wireless-backhaul NWA50AX reboot on their own roughly every 17 hours, logged as:

"System event zyshd occurred..."
"Port 0 is down!"
"This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0"
"Port 0 is down!"
"Port 0 is up! The link speed is 1000M/Full."

I pulled the timestamps of every one of these reboots over a 12-day log and the gaps between them are suspiciously consistent — almost always 993 to 1057 minutes apart, which is 16h33m to 17h37m. That's way too regular to be a coincidence or random interference. It genuinely looks like some kind of internal timer or watchdog that's quietly counting down to a forced reboot.

A few things I've already ruled out while trying to track this down:

  • EEE / Green Ethernet is disabled on every switch port involved (FritzBox 7530), so it's not that.
  • I thought it might be DHCP lease renewal going wrong, but the NWA90AX has had a static IP reservation the whole time and it's still affected just as much as the dynamic-IP repeater, so that's not it either (at least not for the 90AX).
  • It's not a network-wide problem — I have a third identical NWA50AX (wired, same firmware, same network) that has had zero of these reboots in the same 12-day window. Only the 90AX and the wireless-backhaul repeater are affected.

Occasionally (not every time, maybe 1 in 4) the reboot is followed a few minutes later by "Wrong WPA2 Pre-Shared Key on 2.4GHz/5GHz, please check." on the mesh link, which then resyncs itself within a few minutes.

I put the wireless NWA50AX into the network by cable to resync their config, but still..

So right now my best guess is some kind of internal watchdog/counter bug that's specific to certain hardware/firmware states rather than anything in my network config, especially since the wired-but-unaffected repeater rules out EEE, cabling, and the upstream router as culprits.

Has anyone else seen this ~17h reboot interval, or know of a known bug around the "Wireless Auto Recovery process. IP:0.0.0.0" message specifically? Happy to share more log excerpts or exact firmware build numbers if that helps narrow it down.

Thanks in advance

Christian

All Replies

  • Zyxel_Melen
    Zyxel_Melen Posts: 5,242
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
    image  Zyxel Employee
    Options

    Hi @ChristianW

    May I know the firmware version of these devices? Because your issue symptom and the logs look like been fixed in 7.10 patch 4.

    Release note link

    If your firmware is earlier than 7.10 patch 4, I recommend you upgrade to the latest version. Please navigate the Site-wide > Configure > Firmware management > Overview in AP part: Select latest in "Firmware type" and select upgrade now and click save to start the firmware upgrade for all of your AP.

    Zyxel Melen


  • ChristianW
    ChristianW Posts: 9
    First Comment First Anniversary
    image  Freshman Member
    edited November 9
    Options

    Hi Melen,

    from what i can tell we are at 7.12:

    NWA50AX ==removed by Zyxel Melen== V7.12(ABYW.1)

    NWA50AX ==removed by Zyxel Melen== V7.12(ABYW.1)

    NWA90AX ==removed by Zyxel Melen== V7.12(ACCV.1)

    Best regards

    Christian

  • ChristianW
    ChristianW Posts: 9
    First Comment First Anniversary
    image  Freshman Member
    edited November 8
    Options

    Unfortunately it made zero difference — same pattern, same interval, same devices.

    Here's a fresh 3-day log sample taken entirely on 7.12:

    "2026-11-06 06:41:23","NWA50AX Repeater Oben","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0" "2026-11-06 07:05:41","NWA90AX Main Rooter","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0" "2026-11-06 07:12:19","NWA50AX Repeater Oben","smart-mesh","Wrong WPA2 Pre-Shared Key on 5GHz, please check."

    "2026-11-06 23:48:29","NWA50AX Repeater Oben","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0" "2026-11-07 00:12:30","NWA90AX Main Rooter","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0" "2026-11-07 00:15:48","NWA50AX Repeater Oben","smart-mesh","Wrong WPA2 Pre-Shared Key on 2.4GHz, please check."

    "2026-11-08 10:00:54","NWA90AX Main Rooter","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0" "2026-11-08 10:09:24","NWA50AX Repeater Oben","system","This AP successful rebooting by Wireless Auto Recovery process. IP:0.0.0.0"

    Three more things worth noting from this:

    • The interval between reboot #1 and #2 is 17h07m — still exactly in the same ~17h window I reported before. This confirms it's not a one-off, it's an ongoing, consistent timer-driven pattern even on the latest firmware.
    • The two affected devices always reboot within minutes of each other (9–24 min apart), alternating which one goes first. This still looks like one device's reboot is knocking out the mesh link and forcing the other to follow, rather than two fully independent bugs.
    • The "Wrong WPA2 Pre-Shared Key" mesh desync still happens right after the reboot in 2 out of these 3 occurrences — so that secondary symptom also survived the 7.12 update untouched.

    So to be clear for anyone following this thread or from Zyxel's side: the fix that was supposedly included in 7.11/7.12 for this behavior does not resolve it in my setup. Happy to provide full raw logs or a support ticket reference if that helps someone actually dig into this on the firmware side.

    Best regards

    Christian

  • Zyxel_Melen
    Zyxel_Melen Posts: 5,242
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
    image  Zyxel Employee
    Options

    Hi @ChristianW

    Thanks for the firmware information. Could you help to enable Zyxel support access so we can check the device's log to investigate further?

    Zyxel Melen


  • ChristianW
    ChristianW Posts: 9
    First Comment First Anniversary
    image  Freshman Member
    Options

    Hi Melen,

    thanks for stepping in, i enabled the support account.

    Best regards

    Christian

Nebula Tips & Tricks