[Help]: Fail to start omada-controller - falling back to 1 default profile: "default" #465
-
Controller Versionlatest Describe Your Issue or QuestionI recently tried to install the omada-controller using the [mbentley] package and seems like everything went well until I waited almost 30 minutes for the container to start and never did. I went into the logs from portainer and I am getting the following error. . ____ _ __ _ _ Apparently the No active profile set is causing the issue but no other components of why this is happening... I made sure I enabled all the necessary ports and restarted the console. No luck. Expected Behaviorhere is the command that I used to build the omada container: --name omada-controller Steps to Reproducen/a How You're Launching the Container
Container Logs
MongoDB Logs
Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
Duplicate of #418 There is a software bug in the 5.14 version of the controller and that’s on TP-Link. Use 5.13 for now. |
Beta Was this translation helpful? Give feedback.
-
Hi! Same problem for version 5.15. Bug is still unresolved? When trying to downgrade to 15.13, I get the following message:
Will I lose my data if I try to force downgrade? I have lots of data and settings, so don't want to try it without making sure 😅 LOGS:
|
Beta Was this translation helpful? Give feedback.
Duplicate of #418
There is a software bug in the 5.14 version of the controller and that’s on TP-Link. Use 5.13 for now.