@RPGRCIT 

Are you using a controller or is the router stand alone?
Do you get any error messages?

  @RPGRCIT 

Can you try to install universal 1.3.0 firmware first (so the same version as you already have) and then (if successful) try to install 1.4.0?

That's just an idea :)

  @Clive_A 

Thank you for your guidance!

But I still have issues. Please excuse my ignorance but I don't know how to do it from the Omada Cloud Management Platform.

I tried to do it by connecting directly to the gateway but I cannot connect as admin, although I use the same credentials to connect to the controller (locally) succesfully.

Can you please guide me on how to find the status of https port and enable it if needed through the Omada Cloud Management Platform?

Thank you!

  @RPGRCIT 

If your device is Adopted by Omada Controller, you won't be able to login into it directly. 

Whole management goes by controller and the device will prevent any login attempts.

Also, since it's already controlled by the cloud - I'm not sure if it is needed to enable HTTPS on that device, since you are not logging into it directly... Maybe someone will correct me if I'm wrong.

As I see it, if you still wanna enable HTTPS manually, you would have to forget the device from controller, then you should be able to log into it directly as it should be back to Standalone Mode, change the HTTPS settings there, maybe proceed with firmware update, and then Adopt it again in the controller.

Standalone Mode:

But as I said, I'm not sure if that makes any sense since it's already controlled by Omada Cloud. Maybe it's worth to wait for Clive's response.