BKS

Yeah, it started happening with HA for me as well. This problem was the final straw that pushed me away from unraid as a homelab server. Strange problem that I could never figure out and community support from here and reddit/discord didn't help.

I've had this happen on several instances, but twice with my Immich container over the past week. Container is present and working fine, then overnight it seems to disappear. Containers are getting started/stopped by CA Backup plugin but otherwise should not be changing. Any thoughts on where to look for troubleshooting this? Unraid Pro 6.11.5

I've provisioned a new esphome device using USB and https://web.esphome.io, able to connect to the device directly with HTTP. After it is provisioned, I think it should be detected with ESPHome at that point, correct? No config installed on the device itself yet.

Trying to get ESPHome separated from my HA pi box. I installed the container through CA store, get to the web UI and no devices are shown. I'm able to get into the container console and ping the relevant devices and get a response, seems like network connectivity is there. Not sure if it should be bridge networking or host, have tried both, but can't get the (working in HA) esphome devices to show in the dashboard through the esphome unraid image. Any thoughts?

Attempting to use db-backup container to back up a mariadb server, both running as bridge mode in an unraid host. On running the backup command, I get an error that the MySQL/MariaDB server is not accessible. I can ping the IP address from the shell of that container though. Seems to be a networking issue but can't figure it out. Any tips here?

I use your node-red container, thank you for maintaining it. A few node plugins I'd like to use give me errors when I try to add to the node-red palette. Logs show (excerpt): today at 1:54:50 PMnpm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you today at 1:54:50 PMnpm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your today at 1:54:50 PMnpm ERR! npm ERR! build environment-- today at 1:54:50 PMnpm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp today at 1:54:50 PMnpm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` today at 1:54:50 PMnpm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` today at 1:54:50 PMnpm ERR! today at 1:54:50 PMnpm ERR! npm ERR! A complete log of this run can be found in: today at 1:54:50 PMnpm ERR! npm ERR! /data/.npm/_logs/2022-08-14T17_54_38_092Z-debug-0.log Looks like I need to get some packages installed for compiling python code. Is this not included in the container by default? Any recommendations on best way for me to add it? Thanks!

Actually, nevermind. Device is less than a month old, I'm just going to take the easy way out and replace it while it's within the window!

I got an error randomly a couple of days ago: Tower: Warning [TOWER] - Cache pool BTRFS missing device(s) Unraid Cache disk message Warning [TOWER] - Cache pool BTRFS missing device(s) 1657356301 Samsung_SSD_970_EVO_Plus_1TB_S6S1Nxxx (nvme0n1) warning. I logged into web UI and all lights were green, thought it may have been a momentary issue. I then noticed that my /var/log was at 100% and dug into why. I had tons of BRTFS errors related to that drive. I restarted the server and now am getting the message that that drive is missing. Diagnostics attached. It's an M2 slot device, no replacing cables. What other steps can I try? The drive is less than 1 month old.

6.10.3 -- Removing that parameter worked! Thanks

Attempted without success steps 1-4. Thunderbird-2022-07-09T20-16-54.log.gz

Having this same issue as above. Attempted re-downloading the container image without success. today at 4:21:02 PMFluxbox crashed with exit code 1. Respawning.. Tried version specifying as above as well as latest. Any other ideas?

I just upgraded my unraid server. Now working on upgrading cache drive from existing by moving everything from cache drive to array with mover. Invoking mover and viewing logs, appears that every file is failing. Is this a permissions issue? Any idea what's going on? Excerpt from logs below. Jun 18 07:09:38 Tower move: file: /mnt/cache/appdata/speedtest-tracker/www/node_modules/webpack-cli/node_modules/.bin/which Jun 18 07:09:38 Tower move: move_object: /mnt/cache/appdata/speedtest-tracker/www/node_modules/webpack-cli/node_modules/.bin/which No such file or directory Jun 18 07:09:38 Tower root: Specified filename /mnt/cache/appdata/speedtest-tracker/www/node_modules/webpack/node_modules/.bin/terser does not exist. Jun 18 07:09:38 Tower move: file: /mnt/cache/appdata/speedtest-tracker/www/node_modules/webpack/node_modules/.bin/terser

Help in the Web UI is found by toggling the question mark button at the top right of just about any page.

I think the order needs changed. I did message the bot prior to testing. It appears the message needs to be sent after the bot sends an initial message to the client.

That did it for me, thank you. This should probably be in the documentation somewhere (unless it already is an I'm just missing it).