JustinAiken

Oh lol it was a flash drive issue - 2GB used of 2GB does not leave much room 🤣

plugin: updating: dynamix.unraid.net.plg Executing hook script: pre_plugin_checks plugin: downloading: dynamix.unraid.net-4.15.1-x86_64-1.txz ... 28% plugin: dynamix.unraid.net-4.15.1-x86_64-1.txz download failure: File I/O error Executing hook script: post_plugin_checks Trying to go from 2025.07.10.1432 to 2025.08.20.2129

How do you get this to work for Palworld (Steam), for players on a local network instead of a community server? Trying to connect directly to the docker ip/port gives a "No password entered" even after stripping it out of the .ini

Right now on the current docker image, I'm seeing this error on startup: /usr/lib/python3.8/site-packages/sickchill/locale /usr/lib/python3.8/site-packages/sickchill/locale Traceback (most recent call last): File "/usr/bin/SickChill.py", line 14, in <module> import sickchill.start File "/usr/lib/python3.8/site-packages/sickchill/__init__.py", line 1, in <module> from .show.indexers import indexer, ShowIndexer File "/usr/lib/python3.8/site-packages/sickchill/show/indexers/__init__.py", line 1, in <module> from .handler import ShowIndexer File "/usr/lib/python3.8/site-packages/sickchill/show/indexers/handler.py", line 5, in <module> from sickchill.tv import Show, TVEpisode File "/usr/lib/python3.8/site-packages/sickchill/tv.py", line 15, in <module> import imdb ModuleNotFoundError: No module named 'imdb' EDIT: Opened issue on github at https://github.com/linuxserver/docker-sickchill/issues/25

..you got me interested in a dark theme, I just gave it a try. ``` # Run this while Node Red is up and running: $ docker exec -it NodeRed-OfficialDocker /bin/bash # Then you'll be inside the running container # Now run: $ npm install node-red-contrib-theme-midnight-red # And exit the container: $ exit # Now from unraid, edit settings.js: $ vim /path/to/nodered/settings.js ``` You'll want it to look like: ``` .... editorTheme: { page: { css: "/usr/src/node-red/node_modules/node-red-contrib-theme-midnight-red/midnight.css" } } ``` Then restart nodered docker from the unraid docker GUI.

NOT the toplevel appdata folder !- the path to your nodered appdata folder. Something like `/mnt/user/appdata/nodered` https://github.com/bonanitech/node-red-contrib-theme-midnight-red#install Looks like you have to manually do some `npm`'ing

Just tested, and at least as `root` it worked

To update to v1.0 that came out today: - Edit your docker template's repository field from `nodered/node-red-docker` to just `nodered/node-red` - I needed to `chown -R 1000 /path/to/appdir` to update it to the new uid used by the container

I almost feel bad about getting one of these and putting it on my ancient beat up Norco 4220! (Cover doesn't fit since I jammed in the 120mm fanplate :p )

Love unRaid... started as a way to just hold lots of movies for XMBC to play, now it's an automated downloading behemoth that's also running backups and home automation.

I'd love RSS for both blog posts, and new unRaid stable/beta releases

+1

Just had the same problem, and deleting the server.key/server.cert in `appdata/sabnzbd/admin` worked for me too 👍

@TexasAg - if you do that, then does the query log show the host instead of the IP under "Client"? Or is that just to make local DNS queries resolve?

After updating to the new version yesterday, I get this: ::: Testing DNSmasq config: ::: Testing lighttpd config: Syntax OK ::: All config checks passed, starting ... ::: Docker start setup complete [✗] DNS resolution is currently unavailable [cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. And it doesn't stay up. DNS is set to use to 1.1.1.1

Has anybody figured any ways to optimize memory usage? Right now I've got the cap set at 8GB (`8192M`) - half of the 16GB in my system. After a few hours, I'm still getting warnings that I'm hitting 85 or 95 percent of the memory limit, and the GUI gets unresponsive. Before I resort to buying more RAM, is there any config settings to help tame that? Or does one just need 16GB dedicated to Crashplan to back up 10TB of data? Or will it chew through 16GB just as fast as it chews through 8GB? ? (Not related to @Djoss's dockerization work - that's working perfectly - , but this thread is where the most active CP discussion is..)

That worked! Pretty graphs loaded... wow, I need a faster cache drive!

Just tried to "Purge Everything and Start Over" (which seemed to work), then ran the benchmark again... got the same thing: Lucee 5.2.6.59 Error (application) Message source file [/tmp/DiskSpeedTmp/benchmark_0000_01_00.0.txt] is not a file Stacktrace The Error Occurred in /var/www/Benchmark.cfm: line 117 115: <CFIF URL.Restart EQ "Y"> 116: <CFLOOP index="CR" from="1" to="#BenchCheck.RecordCount#"> 117: <CFFILE action="Delete" file="/tmp/DiskSpeedTmp/#BenchCheck.Name[CR]#"> 118: </CFLOOP> 119: <CFLOCATION URL="Benchmark.cfm" addtoken="NO">

Updated to today's version, tried to run a benchmark, got this error: Lucee 5.2.6.59 Error (application) Message source file [/tmp/DiskSpeedTmp/benchmark_0000_01_00.0.txt] is not a file Stacktrace The Error Occurred in /var/www/Benchmark.cfm: line 117 115: <CFIF URL.Restart EQ "Y"> 116: <CFLOOP index="CR" from="1" to="#BenchCheck.RecordCount#"> 117: <CFFILE action="Delete" file="/tmp/DiskSpeedTmp/#BenchCheck.Name[CR]#"> 118: </CFLOOP> 119: <CFLOCATION URL="Benchmark.cfm" addtoken="NO">

Yep, walked through the space invader video. First time I was using the container heavily, got a hard lock. Next I tried just running it for a few days, but not using it for DNS; so it was running 24/7, but handling 0 requests. After a few days, the docker container showed as "healthy", but was unkillable. Anecdotally speaking, every hardlock a docker container has ever done to my unRaid has been a container using the s6 system (gogs used to lock mine up occasionally, but it quit using s6, and hasn't locked since)

This container seems to be locking up my whole Docker - the Docker page in unraid wouldn't load. Tried stopping Docker from the settings tab, no luck. SSHing I see this: root@Tower:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 62518c9bb052 diginc/pi-hole:latest "/s6-init" 6 days ago Up 4 days (healthy) pihole root@Tower:~# docker stop pihole # Hangs for a few minutes. Eventually ctrl-c out root@Tower:~# docker kill pihole # Hangs forever

Ran the benchmark, was admiring the graphs (really nice looking data!), when suddenly it changed to this error: https://gist.github.com/JustinAiken/4a554195fefa3d5abf584d5779bcf26e

Different PIDs, but seeing the same thing. WebUI doesn't load at all

Neither; in the container settings page, click "Edit" next to the storage path mapping, and a modal popups; It has a few options, but you'll just change "Access Mode" off of read-only.