• Posts

  • Joined

  • Last visited

About MaxAbsorbency

  • Birthday September 25


  • Gender

Recent Profile Visitors

242 profile views

MaxAbsorbency's Achievements


Newbie (1/14)



  1. is that because extrassd is full but /user/docker-settings is on a share spanning other disks and is not full? your new error is also a failure to write to file, perhaps that location is still on a full disk
  2. Check your MANAGE_HTTP_PORT / MANAGE_HTTPS_PORT variables on the omada-controller container and make sure that's the port you're connecting to (http:// or https:// respectively)
  3. Also seeing this happen again within the last few days. Still on 6.11.5, had the issue a few weeks ago and applied the patch as described previously in this thread. But about a week ago container versions started sporadically disappearing and becoming "not available" on the ui again. No pattern. Different maintainers on each image and everything. No funky DNS settings or anything either. Uninstalling and reinstalling the plugin made... some of the update links work again. Some are still showing not available.
  4. Thanks for chiming in. I still haven't had an issue at all with the container/image but I added that parameter just in case.
  5. Just wanted to confirm that when this issue occurred for me in Brave, disabling Brave web protection worked. You can click the Brave icon in the url bar and hit the slider to turn protection off in the console browser window.
  6. Define "wifi issues"? I've been running the container most of 2022 without problem. What should I look out for?
  7. My setup: Path in container <--> Path on host OS /opt/tplink/EAPController/data <--> /mnt/cache/appdata/omada-controller/data/ /opt/tplink/EAPController/work <--> /mnt/cache/appdata/omada-controller/work/ /opt/tplink/EAPController/logs <--> /mnt/cache/appdata/omada-controller/logs/
  8. First off, thanks for the container, very useful. TL-R605 v1.0 here no issue but I have heard of others having this issue - maybe its a device/version/firmware combination with the new version of the controller software?
  9. I didn't see a correct response to this, the answer is flarum doesn't use the newer default mysql password encryption. Assuming you have already created a user and a database, and given that user permissions to the database, I was able to fix this by going into my db and doing: ALTER USER 'flarum_user'@'%' IDENTIFIED WITH mysql_native_password BY 'flarum_user_password'; I discovered this by quickly going into the console of the container before it shutdown after that 60s wait and attempting to connect to my database in terminal mysql --host=$DB_HOST:$DB_PORT --user=$DB_USER --password=$DB_PASSWORD flarum_database_name which displayed an error: Authentication plugin 'caching_sha2_password' cannot be loaded: dlopen(/usr/local/mysql/lib/plugin/, 2): image not found