Operational Defect Database
BugZero found this defect 1017 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA16S000000Fx5aSAC
Cannot connect to Firebox after reboot when Reverse Proxy URL exceeds 32 characters
Last update date:
8/9/2021
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.6.x
12.7.x
Fixed releases:
v12.8
Description:
Issue
In Fireware 12.6.4 or higher, if you configure a Reverse Proxy URL that is more than 32 characters and reboot the Firebox, you can no longer connect to the Firebox from Web UI, WSM, Mobile VPN with SSL, or Access Portal because the Firebox web server process (nginx) fails to start.To regain access to the Firebox: Use an SSH client, such as Putty, to connect to the Firebox on port 4118.Log in with admin credentials.Run this command: confshow access-portal url-mappings The URL mappings appear: --URL-Mappings--Url mapping : EnabledName: TESTDescription:External URL: Example-URL-that-exceeds-32-characters.comInternal URL: Example-URL-that-exceeds-32-characters.com Identify the name of the entry with a URL that is longer than 32 characters.Run this command (replace TEST with the name of your URL mapping): no access-portal url-mapping name TEST Press Enter. You can now connect to the Firebox.
Workaround/Solution
No workaround exists at this time.
