subscriptions stopped updating

Steve_ESteve_E
in Firebox - Subscription Services

Hello

locally managed M270 +fw 12.11.8

fsm dashboard says subsciptions outdated going on awhile

https://services.watchguard.com from a web browser says healthy

log says

2026-03-08 06:54:00 sigd Server response code for register: 502
2026-03-08 06:54:00 sigd register failed
2026-03-08 06:54:00 sigd URL string for update status report: https://services.watchguard.com/ServiceJoined/ServiceJoined.asmx/RegisterResultJoined
2026-03-08 06:54:00 sigd POSTDATA for update status report: sSerialNumber=xxx&sApplianceVersionNumber=12.11.8&sModelNumber=M270&sServiceType=AVService&sResultCode=5

manual update button on fsm sometimes works

Are there other update servers to try?

Is this worth a shot? Do you use it? Does it cost extra?

https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/services/botnet/botnet_updates_c.html

WatchGuard offers Offline Signature Updates that enable you to download the latest signatures for these services directly from WatchGuard, and then use a script to manually install these files on your Fireboxes.

Comments

  • CraigSCraigS
    edited March 9

    Yeah, I'm seeing similar behavior trying to manually update in FSM with 12.11.8. I had a case open last Thursday with support and it appeared to be fixed Friday. The status page stated there was an issue that was corrected, so I closed the case. This morning (Monday) I am getting a "The update failed: Register procedure failed. An error occurred in the initial connection to the update server (5)" error with every manual subscription update (GAV, WebBlocker, M365, etc.). This is occurring at multiple locations.

    I guess I'll reopen the case.

    (edit: I have confirmed the error is also occurring on version 12.11.4)

  • CraigSCraigS

    The manual updates are now working instantly across all the subscriptions at all our locations. No changes were performed on our devices, so I suspect it was an issue upstream.

  • james.carsonjames.carson Moderator, WatchGuard Representative

    Hi @Steve_E @CraigS
    The behavior you're seeing suggests that the update may not have synced across all of our CDNs. It appears this has since been fixed.
    If you're still running into this issue on any of your devices, please open a support case so we can get more details.

    Thank you,

    -James Carson
    WatchGuard Customer Support

Sign In to comment.