hedrinbc

Great to hear. I didn't create the Docker but did create the Unraid template and am a user. Happy to hear it's working, hoping others find this as it was a gap for me when I moved to Omada just a few weeks ago. Please help me support here for 3.2 upgraders if you can!

Hi there couple questions. Were you able to create paths on your system for the three paths required? Were those paths on your array or in a cache or unassigned drive? My 3 paths are on an unassigned drive versus in the array and I have heard there could be permission issues if on the array. Reading those logs it appears to me it can't write into the paths. Happy to continue to help, I do have it running over here so we can get there! -Ben

SETUP: PRIOR TO FIRST RUN - If you don't you may need to wipe all files in the 3 paths and start again. Set all Ports via the variables on the template prior to first run. My default Ports are set non-standard to avoid other used ports. These setting works great on my network, AP adoption, etc. and likely will with yours. Set the 3 paths to your cache or unassigned drive. I have heard permission issues come from using the array paths. In Advanced check the "WebUI" URL is you changed my default ports. Please let me know if you need any assistance.

Support thread for omada-controller on Unraid Community Applications. Template leverages mbentley's docker https://hub.docker.com/r/mbentley/omada-controller Docker specific, not related to Unraid, issues are logged here https://github.com/mbentley/docker-omada-controller/issues/

Yes, also having issues with the latest version. New video files don't get re-scanned quickly so I often restart the container and after the latest update the container doesn't boot properly and the logs are not helpful (supervisor and cron comments only) then the service is not visible form my Roku. My "fix" has been to delete all the files in the settings directory manually and restart then it starts every time. Any thoughts? Thanks, -Ben