Skip to main content
pjang
Staff & Editor
Staff & Editor
March 6, 2026

Technical Tip: FortiEdge Cloud-managed FortiAP failing to upgrade firmware, reports "download firmware failed (HTTPS), code 4" in Event Logs

  • March 6, 2026
  • 0 replies
  • 304 views
Description

This article describes a known-issue that can occur when attempting to upgrade firmware on FortiAPs managed by FortiEdge Cloud. The following key symptoms can be observed when this issue occurs following an attempted firmware upgrade:

  • Administrators may find Event Log messages of Subtype: ap-upgrade on FortiLAN cloud reporting that 'AP FPXXXXXXXXXXXXX download firmware failed (HTTPS), code 4'. The Action may also state 'fw-download-failed'.
  • Meanwhile, firmware upgrades executed directly on the FortiAP (e.g., via the FortiAP's direct web GUI) work without issue.
Scope FortiAP, FortiEdge Cloud.
Solution

As per the FortiEdge Cloud User Guide, there is a general requirement that the FortiAP must be allowed to reach several listening ports on FortiEdge Cloud, which include but are not limited to TCP 443/514/8443 and UDP 5246/5247 (refer to the following document for the full list of ports and regional FQDNs that must be accessible: Upstream Firewall Rules for Cloud Communication).

 

In this particular case, the FortiAP must be able to make an outgoing connection for TCP port 8443 in order to download the firmware files from FortiEdge Cloud prior to performing an upgrade; otherwise, the download will fail, and the above event log message will be produced. Check any firewalls/routers in between the FortiAP and the Internet to ensure that these outgoing connections are not being blocked, then reinitiate the firmware upgrade after confirming that TCP/8443 connectivity has been allowed.

 

FortiEdge Cloud log exampleFortiEdge Cloud log example