Binding Software Controller to Omada Cloud fails with "General Error"

Binding Software Controller to Omada Cloud fails with "General Error"

Binding Software Controller to Omada Cloud fails with "General Error"
Binding Software Controller to Omada Cloud fails with "General Error"
2024-05-03 06:33:35 - last edited 2024-05-03 06:35:37
Tags: #API #Binding
Hardware Version: V5
Firmware Version: 5.13.30.8

Hello to everybody!

 

There is already an old thread but it was closed without a solution, and it seems I have a slightly different setup compared to the other thread.

 

I used to run my controller on a Proxmox Windows VM, but the overhead of Windows and restarts for updates to "inconvenient times" made me set up an Ubuntu 22.04 LTS and migrate my controller to Ubuntu.

 

It worked from the scratch and also was accessible via Omada Cloud.

 

But about 4 weeks ago, the Omada Cloud showed the controller as offline. Reboot did not help. So I removed the controller from the cloud to rebind it. But all I get is the "General Error" mentioned above.

 

Other threads had a pppoe-interface needing to be removed, but my setup is very simple, there is only the pve-bridge-interface and all internet traffic seems to run normally (ping, dns, apt etc.)

 

When trying to bind, the server.log throws this messages:

 

05-03-2024 06:13:38.585 ERROR [https-jsse-nio-8043-exec-10] [] c.t.e.c.h.ApiHttpClient(): Device information from deviceMgmt is illegal.
05-03-2024 06:13:38.946 WARN [Thread-8] [] c.t.e.c.c.e(): Request params from delegate is in invalid format.
05-03-2024 06:13:38.993 WARN [https-jsse-nio-8043-exec-10] [] c.t.e.c.h.ApiHttpClient(): Failed to validate device.
05-03-2024 06:13:38.993 WARN [https-jsse-nio-8043-exec-10] [] c.t.s.o.c.p.b.d(): Request: checkDeviceBindStatus, cloud errorCode: -20104, msg: Parameter doesn't exist
05-03-2024 06:13:38.993 WARN [https-jsse-nio-8043-exec-10] [] c.t.s.o.c.a.b.a(): Unexpected cloud error: -20104
05-03-2024 06:13:38.993 WARN [https-jsse-nio-8043-exec-10] [] c.t.s.o.i.a.b.b.a(): Unexpected error when binding owner.
05-03-2024 06:13:39.020 INFO [Thread-213] [] c.t.e.c.c.n(): ssl recv thread is stopped.

 

The "offline controller" has adopted the hardware without problems - its also a quite simple setup, containing one SG2008P switch having 3 EAP 245 EU (2 Revison V3, 1 Revision V4)

 

Does anyone have an idea, what error "-20104" does mean and how to solve the problem?

 

Or should I setup a new controller and try to migrate?

 

Regards,

Markus

 

  1      
  1      
#1
Options
2 Reply
Re:Binding Software Controller to Omada Cloud fails with "General Error"
2024-06-13 15:30:41

  @MarkusL 

I don't know if you got your answer but the only I was able to fix this is delete the db folder and let it recreate it from scratch.

You will need to reconfigure it though. You may try to reload config from backup but I suspect it will then break again.

  0  
  0  
#3
Options
Re:Binding Software Controller to Omada Cloud fails with "General Error"
2024-10-27 09:29:19

I recently migrated from OC200 to the software controller, but i, like @MarkusL having problems with connecting to the cloud, this thread still seemed unsolved, so I figured to revive it.

 

This is from my server.log

 

10-27-2024 10:27:44.147 ERROR [https-jsse-nio-443-exec-13] [] c.t.e.c.h.ApiHttpClient(): Device information from deviceMgmt is illegal.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.e.c.h.ApiHttpClient(): Failed to validate device.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.i.a.b.b.a(): Unexpected error when binding owner.
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.c.p.b.d(): Request: checkDeviceBindStatus, cloud errorCode: -20104, msg: Parameter doesn't exist
10-27-2024 10:27:44.333 WARN [https-jsse-nio-443-exec-13] [] c.t.s.o.c.a.b.a(): Unexpected cloud error: -20104

 

These 5 lines, comes everytime i try to enable and bind to omada cloud.

 

I on the latest beta - 5.15.6.4

 

/Stephen

  0  
  0  
#4
Options