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
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
@b10up Just made an account because I'm running into the same issue. Updated Omada Controller from v5.9.31 on a Raspberry Pi 64-bit to v5.12.7. Local login does not work and I do not use cloud access. I tried resetting my password and the lockout continues. I'll need to downgrade for now in order to use the Controller.
- Copy Link
- Report Inappropriate Content
Ther are several people posting about having the same issue. A user on reddit checked in MongoDB (see thread here) and looks like he might see the issue. Not sure why it comes up now or if it is the same for everyone but there are people reporting the problem on Reddit and on the GitHub repo for the Docker image I maintain.
- Copy Link
- Report Inappropriate Content
Is everyone installing the controller in docker to have this problem, it shouldn't be a problem without using docker?
- Copy Link
- Report Inappropriate Content
@ddtt1024 I doubt it has anything to do with a controller running in Docker unless there was something modified in the init script in 5.12.7 that I didn't see.
I run my controller in Docker but I didn't have any issues with the upgrade from 5.9.x to 5.12.7 migration and I could still login just fine myself without issues so it isn't something that just always happens.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@ddtt1024 I'm actually running this outside of Docker. I might have to take a look at the Reddit thread that dug into MongoDB... Still no luck with a local login.
- Copy Link
- Report Inappropriate Content
My OC300 was recently upgraded and I can no longer log-in to it via its LAN IP from the Web browser that was used to perform the upgrade. Logging-in from a different Web browser or remotely from Omada Cloud works though. I'd tried contacting technical support, but they've been next-to-useless and have made no real effort to actually resolve it.
- Copy Link
- Report Inappropriate Content
Same here, tried Docker and fresh LXC container but get stuck on the login screen. App works fine, but cloud says it's offline. Super annoying.
- Copy Link
- Report Inappropriate Content
@b10up Got the same problem. Upgrading from 5.9.31 to 5.12.7 using the docker image by mbentley (https://github.com/mbentley/docker-omada-controller). I couldn't login with my local admin user, cloud admin worked fine. Reset my local admin password and still couldn't login. Had to revert to a snapshot I took before upgrading and am running 5.9.31 again.
- Copy Link
- Report Inappropriate Content
Any updates on this issue?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 4997
Replies: 22
Voters 3
