Email Updates
Sign up to get the latest product news, updates, and support alerts from WatchGuard.
SubscribeRelated Posts
End-of-Sale Announcement for Firebox T45 (Non-PoE/Non-WiFi)
End-of-Sale Announcement for Firebox T45 (Non-PoE/Non-WiFi)
WatchGuard Technologies is announcing the end-of-sale (EOS) date for the Firebox T45 model. The T45 model will be replaced by the T45-PoE, which offers identical performance and functionality but also includes one PoE port.
Effective April 1, 2025, the T45 will no longer be available for purchase and will be removed from our price list.
EOS and EOL Milestones for T45
Milestone | Definition | Date |
End-of-Sale | WatchGuard will no longer sell new T45 hardware | April 1, 2025 |
End-of-Life | WatchGuard will discontinue support for T45 hardware | January 1, 2031 |
Migration Options
Customers looking for a Firebox model with equivalent performance and functionality to the T45 should consider the T45-PoE model. Please note that the T45-PoE has separate SKUs based on the required AC power cord.
Affected Products
This announcement applies to T45 hardware and service licenses. However, renewals will still be available for previously purchased hardware.
Contact Us
WatchGuard is dedicated to providing industry-leading solutions that keep our customers secure. If you have any questions regarding this announcement, please contact your WatchGuard account manager.
For details on WatchGuard’s Global End-of-Life Policy, visit:
WatchGuard Global EOL Policy
For more information on our standard End-of-Life policy, visit:
WatchGuard Standard EOL Policy

Knowledge Base Digest - February 2025
Knowledge Base Digest - February 2025
Articles
- How to disassemble a Firebox for recycling and waste
- App Hibernation and Ignore Battery Optimizations Permission Issues in AuthPoint mobile app
- ThreatSync+ Best Practices: Operate ThreatSync+ in your Managed Security Service
- Migrate Panda products to WatchGuard Endpoint Security products
- AuthPoint protection against replay attacks
Known Issues
- WatchGuard Endpoint Security firewall protection's automatic network location is incorrect when using IKEV2 VPN adapters
- WatchGuard Cloud Directory users cannot authenticate
- Modifying the VLAN configuration in Policy Manager removes wireless interfaces from the VLAN
- Network Discovery misidentifies WatchGuard Access Points and Microsoft OS versions
- Session/idle timeouts do not take effect for SAML logins to Mobile VPN with SSL
- Firebox System Manager shows incorrect BOVPN routes when connected to Firebox Cloud
- Microsoft services do not function as expected with Microsoft 365 when you enable content inspection
- Internal error in WatchGuard Cloud Log Manager and Log Search pages when you query data by date
- HTTP 400 error messages when you search log messages in WatchGuard Cloud

Knowledge Base Digest - January 2025
Knowledge Base Digest - January 2025
Articles
- Cannot connect to APs after Firebox upgrade to Fireware v12.11
- Language support for ThreatSync+ NDR Linux collector installation
Known Issues
- WatchGuard Endpoint Security shows Trojan/RansomDecoy.A detections as 'Ignored' in the Threats Detected by the Antivirus tile
- WatchGuard Endpoint Security performance issues and computers erroneously identified as "Unmanaged" with Endpoint Access Enforcement
- Active Directory authentication fails with message "search binding error, check your searching username or password"
- Unnumbered PPPoE connection unable to obtain IP address from ISP
- When you enable TCP MTU Probing, WatchGuard Cloud shows error "{'type': 'ipv4_host', 'value': ''} is not valid under any of the given schemas."
- Changes to Access Portal applications not applied after upgrade to Fireware 12.11
- Access Portal logins fail in 12.11 with "403 Forbidden Invalid Session" error
- WebBlocker deny page not shown when cloud-managed Firebox blocks request for web content
- Error message and unable to save BOVPN between two cloud-managed Fireboxes: 'Configured network does not belong to XXXXXXX'
- Close policy type actions missing from ThreatSync automation policies