[Bug]: Controller closing session #396
-
Controller Version5.12.7 Describe the BugAfter updating, the omada phone app no longer connects and the webUI will let me poke around for 30 seconds before bringing me back to the login screen. Expected BehaviorNot restarting. Steps to Reproduce1.Start docker How You're Launching the Container
Container Logs
Additional ContextI see report #340 with a similar issue but starting my own bug report since they were on 5.9 and issue might be different. |
Beta Was this translation helpful? Give feedback.
Replies: 33 comments 17 replies
-
#340 was related to the entrypoint trying to read values from the properties file that didn't exist before the controller itself would start so this is a different issue. In your logs, I don't see where the controller is restarting. Do you have logs from where that was happening (assuming it was actually restarting)? It almost sounds like you're just getting logged out of the web interface for some reason. What browser/OS are you using? Have you tried another browser? Odd that you wouldn't be able to login through the web app. I am not seeing problems with either the web interface or the iOS app here. Is there a specific page you're going to when you have it kick you back to the login page? |
Beta Was this translation helpful? Give feedback.
-
Hm I'd only assumed it was rebooting since the webui would bounce me back to the login. I noticed it only bounces me back when looking at the logs within the controller, but the android app will no longer connecting after updating the container yesterday. Tried the webUI on different browsers and computer with same behavior. Controller is also extremely slow before it bounces me. Was working fine before the update. Is it possible to downgrade the docker version to test? I noticed no specific tags within 5.12 to try. |
Beta Was this translation helpful? Give feedback.
-
No, you can't downgrade without having a backup as the controller does database migrations (and attempting to downgrade will cause it to fail). As of late, TP-Link hasn't provided very many bugfix versions of any minor versions and just keeping the latest major.minor versions up to date is a pretty significant effort since I build images for amd64, arm64, and armv7l, even with automation in place. Typically when they release a new version, they've moved to the next minor version. Here is the list of all of the versions they have published today:
5.9.x was one of the few instances of them releasing multiple bugfix versions since they released 5.x. In addition, it might be worth looking at the |
Beta Was this translation helpful? Give feedback.
-
I have something similar after upgrade from 5.9 to 5.12.
|
Beta Was this translation helpful? Give feedback.
-
I updated to the latest version, and it keeps rejecting my password. Not sure if this matches anyone elses experience. |
Beta Was this translation helpful? Give feedback.
-
So far, I have not seen anyone with that issue yet. |
Beta Was this translation helpful? Give feedback.
-
This seems like something in common and it looks like it is a bug in the software. Something is specifically calling for So I can login and navigate around just fine but if I directly try to access There must be a page in specific where the error is - could either of you tell me exactly which page it is where you're experiencing this when it kicks you back to the login page? If you have that detail, I can submit a bug report on the TP-Link forums to see if they can fix it. |
Beta Was this translation helpful? Give feedback.
-
The logs tab within the dashboard https://192.168.x.xx:8043/login#log It seems to be working now though. I didn't restart the container or anything just randomly lets me view the logs now. |
Beta Was this translation helpful? Give feedback.
-
Mine won't let me log in. And the initial response from the app hangs for a while, then fails. |
Beta Was this translation helpful? Give feedback.
-
@Aevrin - could you start a new discussion on this as it is unrelated? |
Beta Was this translation helpful? Give feedback.
-
Sure, I had thought it might be related due to the app experience. |
Beta Was this translation helpful? Give feedback.
-
I could view logs through cloud connection, but was logged out immediately on local connection on 5.12 5.9 is stable |
Beta Was this translation helpful? Give feedback.
-
One thought I had is that maybe something is cached in browser and they changed a URL but the cache still has it pointing to the previous URL which might trigger the behavior. I can't trigger it myself just browsing the user interface, only when specifically going to a URL that will log me out as described above. I created a forum post so hopefully someone will take a look. |
Beta Was this translation helpful? Give feedback.
-
Good Afternoon, I am also on 5.12.7 and am having similar reboot loop issue, my controller is no longer starting at all. Does this look like a similar issue to #342?
|
Beta Was this translation helpful? Give feedback.
-
This looks different @Robert-litts. I would suggest filing another issue with details about the architecture, how you're starting the container, etc as the issue in #342 isn't the controller actually restarting, just the user session being reset from the interface. |
Beta Was this translation helpful? Give feedback.
-
Issue is still present. |
Beta Was this translation helpful? Give feedback.
-
I just ran into this issue I think. Unable to login into software controller anymore since yesterday. What happens: I enter my username and password to the web UI, I think it tries loading the web UI but then redirects me back to the login screen. it logs following message in docker omada logs on every login attempt:
I see this in the browser:
Note: I only use the local omada controller, I don't use cloud access, not sure if that matters. Edit1: Ive enabled the omada cloud through the mobile app (which I really didnt want doing), still unable to login into the web ui. Edit 2: randomly seeing these exception on login attempts:
Edit: It just started working for me - I didnt do anything and have no explanation. |
Beta Was this translation helpful? Give feedback.
-
The only thing that makes sense to me would be something that is cached in browser that eventually gets cleared but I don't really have any evidence to back that up. |
Beta Was this translation helpful? Give feedback.
-
yeah it started working again for me later in the same day. I definately tried clearing browser cache, differnet browsers and restarting docker OC container N-times. But it started working again I dont know why - maybe me enabling the cloud access through app "did something" . i have not explanation for this behavior. |
Beta Was this translation helpful? Give feedback.
-
Then again, I also have no idea how the backend data store works with any relation to the frontend - for all I know there are some references in the MongoDB to a specific path for a theme that either aren't getting updated properly or are failing to update. |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing the same issue here I've tried 3 browsers, cleared caches, safe mode, etc |
Beta Was this translation helpful? Give feedback.
-
I forgot to update this issue but TP-Link support did reply saying that they will fix this in a future version:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for contacting their support, I just updated to the latest version and still having all flavors of "sessionCSRFToken is null for request", like "sessionCSRFToken is null for request /img/exp-improve.png" and "sessionCSRFToken is null for request /img/loading_apng.png". |
Beta Was this translation helpful? Give feedback.
-
in 5.13 this issue is still there. klicking on any kind of menu, or device kicks me back to login. i downgraded to 5.9. this version run stable. no time to experiment much. i use this docker for my bnb. the guests demand internet ... |
Beta Was this translation helpful? Give feedback.
-
After some back and forth with TP-Link support they stated that "For the Controller local login issue, it is planned to be fixed in Controller v5.14, which is expected to be released in 2024Q1.". |
Beta Was this translation helpful? Give feedback.
-
As a temp workaround, I added the following rule to ublock origin to block the bad requests that were resetting the session.
and that seems to have fixed getting logged out |
Beta Was this translation helpful? Give feedback.
-
I have the same problem. Details: IMHO this whole dockered "solution" is unusable with this version and should not be published at all. |
Beta Was this translation helpful? Give feedback.
-
@leuchtrakete666 : Currently I'm trying to find out, how to change back to the |
Beta Was this translation helpful? Give feedback.
-
Report: v5.9 Works fine.
v5.12+ , v5.13 breaks things.
Downgrade not possible:After tried 4 hours long everything, I've concluded:
If that file is getting deleted, (which is not an easy task, since the container stops, and it's difficult to edit files inside a non-running container,) it stops because of other errors. |
Beta Was this translation helpful? Give feedback.
-
@mbentley Thank your very much for trying to help and for fixing the problem in forward! 👍 ... but as long it is not solved, how about putting 1 line to the main ❗ Warning |
Beta Was this translation helpful? Give feedback.
I forgot to update this issue but TP-Link support did reply saying that they will fix this in a future version: