Router adoption failed
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Team,
See also attached images with the current status:
We do a weekly scheduled reboot of all Omada devices.
After the reboot of last night the router ends with the status "pending".
After a click on pending, the adoption process starts.
Shortly after, this stops with an error message stating that the username/password is not correct.
If I click retry and enter the (correct!) username and password, the adoption then ends with the error stating that the device is not compatible with the controller.
The controller is the Linux software edition 4.4.6 => tried re-installing the controller => no improvements.
Noticed several Java exceptions in the server.log (located in folder /opt/tplink/EAPController/logs).
Also tried rebooting the router and the controller a few times => no improvements.
Username and password is validated by logging into the router itself.
The router states it is not(!) connected to the TP-Link cloud.
Within the router, the cloud switch is turned off and the url-field below is empty.
Turning this switch to on and providing the URL doesn't make it any better.
The Internet connection and all applications (on-prem and cloud) are working as expected.
Meaning the router seems to be processing traffic? And this more like a cosmetic glitch in the portal?
Please advise - where to go from here?
Kind regards - Will
=====
Team,
See also attached image:
I was able to solve this issue by restoring one of the backups.
Meaning I tried restoring weekly backups. After the 3rd restore, everything was working as expected.
Most likely there was an issue in the router-config-files and/or that specific part of the database.
Thank you - Will
=====
Dear @ITV,
So you tried to re-install the Linux Controller v4.4.6 but no improvements, right?
Did you retain data when you re-install the controller?
May I confirm the detailed firmware version of your ER7206 Router?
I assume that you are talking about the Cloud-Based Controller management, and its connection shows as disabled below. Please kindly note that it's a setting for Omada Cloud-Based Controller, it doesn't make any sense here since you are using Linux Software Controller.
Your issue sounds unusual, I'd like to escalate your case to the TP-Link support team for further investigation.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community.
Thank you so much for your cooperation and support!
Team,
See also attached image:
I was able to solve this issue by restoring one of the backups.
Meaning I tried restoring weekly backups. After the 3rd restore, everything was working as expected.
Most likely there was an issue in the router-config-files and/or that specific part of the database.
Thank you - Will
=====