Cant login to omada controller via cloud

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Cant login to omada controller via cloud

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Cant login to omada controller via cloud
Cant login to omada controller via cloud
2023-02-03 08:19:28
Hardware Version: V5
Firmware Version: 5.8.4

setup a new controller, restored from the backup of another controller. Both of them are software cloud controllers running 5.8.4. They are a basically identical except I changed the controller name of the new one. I restored from a fresh backup of the old one. I restored during the initial setup phase and everything seemed to work. I have "connected/linked" it to my tplink ID for the cloud connection and that works and goes green as well. However, when I try to actually login to my controller via omada:tplinkcloud:com I can't login. I have tired the android app and all the different web browsers on my desktop. I can however login to the controller locally. When I look at the logs I get this error:

 

Exception in thread "Thread-56" java.lang.NullPointerException: Cannot invoke "com:tplink:smb:omada:identityaccess:domain:model:user:d:m:y()" because "aUser" is null
02-03-2023 07:49:48.647 WARN [Thread-58] [] c.t.e.c.c.q(): send heartbeat getting timeout response: {"error_code":-20002}
02-03-2023 07:49:58.653 WARN [Thread-58] [] c.t.e.c.c.q(): send heartbeat getting timeout response: {"error_code":-20002}
02-03-2023 07:50:08.660 INFO [Thread-58] [] c.t.e.c.c.q(): unsuccessful heartbeat response: {"error_code":-20002}
02-03-2023 07:50:08.660 INFO [Thread-58] [] c.t.e.c.c.q(): Thread 'heartBeatThread' is stopped
02-03-2023 07:50:08.660 INFO [Thread-54] [] c.t.e.c.c.CloudClient(): Close connection to service server.
02-03-2023 07:50:08.661 INFO [Thread-54] [] c.t.e.c.c.q(): set connection status: DISCONNECTED_NORMAL
02-03-2023 07:50:08.661 INFO [Thread-57] [] c.t.e.c.c.q(): expiredRequestCleanThread is interrupted.
02-03-2023 07:50:08.661 INFO [Thread-57] [] c.t.e.c.c.q(): Thread 'expiredRequestCleanThread' is stopped
02-03-2023 07:50:08.666 INFO [Thread-54] [] c.t.e.c.c.CloudClient(): Connect service server automatically, ConnectionType is PERSISTENT_CONNECTION.
02-03-2023 07:50:08.666 INFO [Thread-54] [] c.t.e.c.c.q(): set connection status: CONNECTING
02-03-2023 07:50:09.117 INFO [Thread-54] [] c.t.e.c.c.q(): set connection status: CONNECTED
02-03-2023 07:50:09.117 INFO [Thread-54] [] c.t.e.c.c.q(): The result of connection is true.

 

this error is comming up a lot in the logs. It seems like maybe its having issues communicating to the tplink cloud services? not sure. any help would be appreciated. thanks.

  0      
  0      
#1
Options
7 Reply
Re:Cant login to omada controller via cloud
2023-02-06 07:35:51

  @zeropoint46 

 

I'm using Windows version software controller and I did not see cloud service issue recently.

 

In normal case the cloud service only require Internet access. However, just in case, please try a public DNS server like 8.8.8.8(for the controller host).

 

I don't really understand the Log but from my experience, the " heartbeat missed" happens when the omada device cannot communicate with the controller host. What is the firmware of your router? Tplink did release an "issue" firmware last month but had fixed it recenetly. 

  0  
  0  
#2
Options
Re:Cant login to omada controller via cloud
2023-02-06 22:34:21

  @zeropoint46 

 

Did you "forget" the old controller from the cloud yet?  Since your new controller is created from a backup of the old one, it may use the same SID (or whatever the unique controller id key is).  Having two of those registered in the cloud may confuse it...

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#3
Options
Re:Cant login to omada controller via cloud
2023-02-27 04:42:20

  @zeropoint46 

I have the exact same issue, did you find a fix?

  0  
  0  
#4
Options
Re:Cant login to omada controller via cloud
2023-02-27 04:49:03

  @Emmesp so I did fix it and my issue is how I restored my omada controller. I used the omada docker container you can find on docker hub. The way I moved to a new host was shutting it down and moving the whole data directory to a new host. That is what I assume broke it. The fix was to create a new one from scratch with an empty data directory and do a proper restoration with the restore file from my original omada container. Not sure if that helps but it's what worked for me.

  2  
  2  
#5
Options
Re:Cant login to omada controller via cloud
2023-02-27 14:13:23

  @zeropoint46 

I'm also using the Docker Container and i did the migration process from the maintenance page, where i download the config file and import it on the new controller, but the issue persist

  0  
  0  
#6
Options
Re:Cant login to omada controller via cloud
2023-02-27 14:22:10

  @zeropoint46 

 

Maybe you can share a screenshot of the error?

 

Even though you do a restore, the upgraded controller will have a new controllerID...so you do need to remove traces of the old.  If you log into omada.tplinkcloud.com, you should remove your old controller and allow the new one to join.  I used the Omada app to do this when I migrated my Docker-based controller, and you also have to remove the Direct entry as well.

 

If that still doesn't work for you, migrate your controller to a new instance but on a different IP.

<< Paying it forward, one juicy problem at a time... >>
  0  
  0  
#7
Options
Re:Cant login to omada controller via cloud
2023-02-27 22:05:56

 Thanks  @d0ugmac1 i was able to fix the issue by taking a new back up of the failing controller with out the checking `Retain User Info` (wich i did check before) and `Settings Only`  (before is selected 7 days) after restoring and rebooting i was able to connect successfully 

  1  
  1  
#8
Options