@linkerman Is your ER605 on the same subnet as the controller?

If the router and the controller are not on the same network, you may need to check the ports and make sure all required ports are opening.

Here is the related post.

  @Somnus It's on a different subnet from the controller, but all the correct ports on the controller are open.

Topology looks like:

ER605 <> Internet <> Nginx (for 443 only) <> Omada Controller v5

Starting Nmap 7.70 at 2022-06-23 12:03 PDT
Nmap scan report for omada
Host is up (0.0064s latency).

PORT      STATE         SERVICE
443/tcp   open          https
29810/tcp closed        unknown
29811/tcp open          unknown
29812/tcp open          unknown
29813/tcp open          unknown
443/udp   closed        https
29810/udp open|filtered unknown
29811/udp closed        unknown
29812/udp closed        unknown
29813/udp closed        unknown

Nmap done: 1 IP address (1 host up) scanned in 1.89 seconds

EDIT

I tried a bunch of times, but nothing changes. These are the only logs I get from the controller.

06-24-2022 06:03:49.683 INFO [manager-upgrade-center-pool-22] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:03:54.682 INFO [manager-upgrade-center-pool-23] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:03:59.683 INFO [manager-upgrade-center-pool-24] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:04:04.682 INFO [manager-upgrade-center-pool-25] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:04:09.683 INFO [manager-upgrade-center-pool-26] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:04:14.682 INFO [manager-upgrade-center-pool-27] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:04:19.682 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(149): upgrade task upgradeId [-] of OmadacId(-) is running...
06-24-2022 06:04:19.683 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(330): v2 device mac14- of omadacId- upgradeId- finished upgrade process in FIRMWARE_DOWNLOAD_FAILED
06-24-2022 06:04:19.684 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.c.c(396): OmadacId(-)  upgradeId[-] DeviceMac(14-) upgrade status change from[false] to [true]
06-24-2022 06:04:19.685 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(469): OmadacId(-) upgrade[id=-] finish.
06-24-2022 06:04:19.688 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.t.DeviceUpgradeStaticTask(155): upgrade task upgradeId [-] of OmadacId(-) is finished
06-24-2022 06:04:19.689 INFO [manager-upgrade-center-pool-28] [] c.t.s.o.m.d.d.m.u.c.c(223): OmadacId(-) upgradeId[-] releaseUpgradeCatelog finished

  @linkerman I saw somewhere that upgrade failed issue may be also related to Download speed. I can't find that post now. Basically the logical is that if the controller took some much time to download the firmware, it will not able to upload the firmware to device properly.

I think you can try to download the firmware manually and upload it on the controller?

EDIT

@Somnus 

I don't think speed is the issue for me.

Home (ER605) speed test: https://www.speedtest.net/result/13325854881.png

Server (Controller) speed test: https://www.speedtest.net/result/13325851664.png

I tried uploading it manually via the controller and the result is the same. Same log messages and everything.

btx wrote

  @linkerman thanks for the log. In your log it clearly says following:

upgradeId- finished upgrade process in FIRMWARE_DOWNLOAD_FAILED

 

At least something, during my upgrades there was no indication to anything. If you had internet connection then of course it could be a bug, but probably you should ensure that you have internet during the upgrade, as example by pinging some server.

 

  @btx I have internet during the upgrade and don't have any ping drops.

btx wrote

 What I miss in your log is once again something that was told to tp-link multiple times, if firmware download failed, one wants to know the reason and here it is useful to show file hash of firmware to be flashed and downloaded file, but in logs there is none. It does not need to be no internet, it is sufficient if file can not be downloaded correctly and for some reason it is corrupted, this well could be on tp-links server, which might explain failures which I experienced, but like I said previously, there was nothing in logs indicating to anything.

Fully agree with you here. I wish there was a more detailed error explaining what the actual issue was.

EDIT