Nebula 19.30 unable to update a Flex 200H with 1.37

Hello everyone,

when forcing the update from Nebula, not all the H series firewalls go for the update:

So I used also Nebula App to push the update.

No positive results for all the devices I was "Upgrading" looking at the Nebula web UI.

As you can see this one:

Needed a manual reboot before the update to 1.37:

As you can see on Nebula there is the wrong timestamp for the last update (that timestamp is the last attempt made via Nebula App with NO success…):

Then I went to the Nebula area where to push the update:

And then FINALLY I have the firewall updated:

How can I solve all these issues when upgrading?

Hi @Zyxel_Melen

I see this issue (reboot before upgrade) more often lately.

It happened for various items from H series to budget routers like SCR50AXE (last time on 2026-02-24 19:27:22) that I tried to update. I understood that because I saw the upgrade failing, then I reboot, then I upgrade the hardware and then the job was done.

It is time consuming and frustrating because it is an operation you cannot schedule.

Considering the fact that on some ORGs there is an automatic update schedule and considering that when you press the button for the upgrade on Nebula you know you want that upgrade…. could be possible to set Nebula to make quick tests if there is enough room to complete the update and, if not, run an automatic reboot with automatic upgrade without asking the MSP to wait for all those actions?

Also because doing these steps during night time could be useful and not frustrating instead of doing that calling the Client, stop the office and accomplish that maintenance operation during office time because you are forced to do it manually.