@Matthieu27 

yes lots of problems, 7 hours work yesterday. after I upgraded from 5.14.20.8 to 5.14.20.9 all ipsec VPN tunnels were offline, routers at the remote site were offline, I did a factory reset and tried but they didn't announce themselves on the controller even once. it was impossible to get them adopted again. As I said, I kept going for many hours. access points and switches on remote site were online on controller but routers not, so very strange.

in the end I had to downgrade to 5.14.20.8 again and run restore to get everything back up.

I made another attempt to upgrade but the same thing happened, no ipsec vpn s2s routers on the remote site went offline. So I downgraded and ran restore again.

what irritates me is that I used an early access version that worked, but what's the point of early access when the official release has changes made to it and doesn't work.

it's not the first time this happens, I had the same thing with the ER707-M2 not too long ago, the EA version worked perfectly but the official version crashed everything-

The VPN went to other controllers and sites and other routers than those that were offline, it wasn't just VPN to routers that were offline.
There is an ER8411 that stands in front of the controler and the remote site where router get offline and was unadoptable is ER707-M2 and ER706W.

Remote device EAP620HDv1, EAP653, EAP225v3 and SG2008P was online to controller and was not infected.

All device have latest aviable firmware.

ER8411 1.2.1 Build 20240308 Rel.75819

ER707-M2 1.2.2 Build 20240324 Rel.42799

ER706W 1.1.0 Build 20240523 Rel.71270(4555) (EA/BETA)

  @MR.S 

Thank you for your response. I see that I am not the only one who has had problems. Personally, my IPSec links still work, but I had to recreate one because it disappeared after the update. I will also perform a restoration. Fortunately, I installed my two switches last week and had not yet put them into production. I share your frustration and hope a solution will be available soon.

  @Matthieu27 

Very strange, my two switches have an IP in a nonexistent subnet. I can connect via the web directly, but it is impossible to log in.

  @Hank21 Thanks

  @Hank21 

Ok, thank you.

i made a third attempt to upgrade today and now it looks like it worked. I don't know why, the only thing I've done is delete all old sites that are no longer in use, I've also changed all vpn names with hyphens to underscores like this my-vpn to my_vpn on all site, and there were many vpn tunnels that had to be renamed, very many.

I don't know why it's not allowed to use hyphens in vpn names anymore. it may cause problems when there is a hyphen. I do not know. anyway, I'm glad that I was upgraded this time.

  @Matthieu27 

I'm trying to reset the switch today but I'm having trouble connecting: it asks me to authenticate, but the Omada credentials don't work. I also tried admin/admin in vain. I'm trying to connect via telnet. Thank you for your help.

  @Matthieu27 

Try device account, 

goto site config and device account and see your credential.

  @Matthieu27 

Thank you very much. It works. I don't know why the password is different from the admin account I use. I managed to get both my switches working. Here’s what I did: I reset the switch, connected directly to it to change the IP it had assigned me in a VLAN I don't use: 192.168.20.0/24. I set a static IP in the correct VLAN, then attempted adoption in Omada and it worked.