Operational Defect Database
BugZero found this defect 1357 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000bpL6SAI
Fully managed devices do not attempt to register with WatchGuard Cloud
Last update date:
5/2/2023
Affected products:
Firebox M200
Firebox M300
Firebox M270
Firebox M370
Firebox M470
Firebox M570
Firebox M670
Firebox M290
Firebox M390
Firebox M400
Firebox M500
Firebox M440
Affected releases:
All
Fireware
12.x
12.5.x
12.6.x
12.7.x
12.8.x
12.9.x
Fixed releases:
All
Description:
Issue
Devices that are fully managed by a Management Server might not attempt to register with WatchGuard Cloud. When this occurs, WatchGuard Cloud status remains as Not Registered.The issue is not resolved when you disable and enable WatchGuard Cloud or reboot the device.This information appears in the Status Report: WatchGuard Cloud Status-----------------------registration_status: 0enabled: 1connected: 0token_required: 0management_enabled: 0disconnect_reason: Not registered This appears in the Web UI: WatchGuard CloudStatus Not RegisteredNot registeredClick here to register.
Workaround/Solution
To force registration with WatchGuard Cloud, run the watchguard-cloud CLI command. For Fireboxes that can automatically register with WatchGuard Cloud (NV5, T15, T20, T25, T35, T40, T45, T55, T80, T85, M270, M290, M370, M390, M470, M570, M590, M670, M690, M4800, M4900), specify 1 as the ident parameter value. For other Fireboxes, specify the Verification Code generated in WatchGuard Cloud as the ident parameter value. For example: watchguard-cloud ? <ident> Verification Code, input the Verification Code to register the device.WG<managed-by-wsm>#watchguard-cloud 1WG<managed-by-wsm># Recheck WatchGuard Cloud status.
