Cannot login with local user anymore
Hi,
I just upgraded the Omada Controller app to 5.12.7. I used my local account to log in and manage my site and use some HomeAssistant integrations. This is broken since the upgrade, this is not accepting my password anymore. I can use only the cloud account. I tried to reset the local account password, but the edit/remove buttons are disappeared for that account.
Anybody else has the same bug, or i miss something?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@voltagex Yes, I'm already drinking the twentieth glass of wine because of it.
Joking aside, I have a regular installation on a headless Ubuntu server. Since then, there have been no updates, and I can only log in with a cloud account. What's interesting is that on the Omada web app, the modification icon is not visible for my local account, but it is visible in the Android app. However, as soon as I try to set a new password, it results in an error.
- Copy Link
- Report Inappropriate Content
I tried to write up some instructions based on what someone on Reddit found that might resolve the issue or at least help someone from TP-Link look at what might be the issue and how they can fix it in software as it seems to be an issue with conflicting data in the MongoDB:
https://github.com/mbentley/docker-omada-controller/discussions/344#discussioncomment-7254461
- Copy Link
- Report Inappropriate Content
I recently had this same problem on my OC200 controller. I could only connect via my Omada Cloud account, but not my local admin account. It turns out that the ad blocker I recently installed in Chrome (Total Adblock) is preventing local log-in. Even excluding the Omada IP address in the ad blocker didn't help, but completely turning it off allows me to log-in. I suppose using a different browser without ad block would also be a work-around.
I don't recall this being an issue immediately after the latest firmware update, so I can only assume that the newly installed ad blocker is the primary variable.
I hope this is helpful.
- Copy Link
- Report Inappropriate Content
@Petenun I actually had a similar experience, except mine was because of Dark Reader. Once I disabled it; the dashboard would login and load successfully.
- Copy Link
- Report Inappropriate Content
Hi All,
Thank you for reporting this issue to the TP-Link community!
Our support engineer has identified the cause of this issue, which is related to certain requests generated by crawler scripts in the browser. These requests are causing the login verification to fail. Rest assured, this will be addressed and optimized in subsequent iterations of the Controller.
Thank you for your patience and understanding.
- Copy Link
- Report Inappropriate Content
@Hank21 Any news on an update for this bug? Pretty significant of a bug to not be prioritized.
- Copy Link
- Report Inappropriate Content
Hi @mbentley，
After confirming with the R&D department, this issue has been located and will be fixed in the subsequent firmware of the Controller ASAP, thank you for your patience and understanding.
Please note that the information provided here is based on the current information we have, it's provided for informational purposes only, not a guarantee or a promise. Any plans are subject to change, the final firmware releases shall prevail.
- Copy Link
- Report Inappropriate Content
@Hank21 - has this been fixed in a released version yet?
- Copy Link
- Report Inappropriate Content
TP-Link, please fix this. It has been a while since this issue showed up, and it is really, really frustrating, and it complicates the usage of the controller. I don't expect issues to be fixed overnight, but this long?? It is quite a serious one, at least in my eyes. Come on, please...
- Copy Link
- Report Inappropriate Content
How the hell has this not been fixed yet? This many months later? What the hell is going on? Pathetic.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 5056
Replies: 22
Voters 3
