-
Controller Version4.4.8 Describe Your Issue or QuestionI attempted to upgrade from 4.4.8 to the latest controller version and when opening the webpage I keep getting the wizard to create a new account instead of being able to log in with my existing username/password. I went through that process thinking that the upgrade from 4 to 5 required a new account to be setup, but it didn't look like it imported anything. The volume settings for the new container are identical and I removed the "work" volume since it was stated it's not used anymore. Am I missing a step to correctly migrate from 4 to 5? In the meantime I've restored my backup and loaded 4.4 again successfully. Thanks! Expected BehaviorExpecting to be able to log into the new container with old credentials after upgrading. Steps to Reproducedocker stop -t 60 omada-controller How You're Launching the Container
Container Logs
MongoDB LogsNo response Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
So TP-Link removed the ability to upgrade from 4.x to 5.x as of version I know the details of a lot of this are difficult to find so what I should probably do is detect if the user was previously running 4.x in the entrypoint while trying to start 5.14.32.2 or greater and block the container from starting and send them to the instructions of how to proceed. |
Beta Was this translation helpful? Give feedback.
So TP-Link removed the ability to upgrade from 4.x to 5.x as of version
5.14.32.2
. I would suggest updating your image tag to 5.13, letting it do the upgrade, and then you can to go 5.14.x. See this section of the README about the upgrade path. Also see the release notes for5.14.32.2
which mention this in note 3.I know the details of a lot of this are difficult to find so what I should probably do is detect if the user was previously running 4.x in the entrypoint while trying to start 5.14.32.2 or greater and block the container from starting and send them to the instructions of how to proceed.