MassimoMx

Hi Binhex, fantastic job on this Docker image! I have a question: How can I change the favicon and title of Jellyfin? I googled it and found this: https://github.com/BobHasNoSoul/jellyfin-mods. I tried to follow "Method 1" and looked in `\\MINIMAX\appdata\binhex-jellyfin`, but I can't find the .html file. Additionally, I can't figure out where to place the `title.sh` as suggested in "Method 2 (The old way)." Edit 1: Eventually I found this guide and modified it a bit: https://www.reddit.com/r/selfhosted/comments/1eyh84b/comment/ljd674a/ From the "Docker" Tab, I opened the console in the container by clicking on the Jellyfin icon cd /usr/share/jellyfin/web touch title.sh nano title.sh added to the title.sh file: grep -rl 'document\.title="Jellyfin"' . | while read -r file; do sed -i 's/document\.title="Jellyfin"/document\.title="TITLE"/g' "$file" done grep -rl 'document.title=e||"Jellyfin"' . | while IFS= read -r file; do sed -i 's/document.title=e||"Jellyfin"/document.title=e||"TITLE"/g' "$file" done chmod +x title.sh ./title.sh Restart container Cleared the cache of the browser Jellyfin title is now replaced with `Title` This approach seems to work, but it's a bit janky as the `Jellyfin` title still appears on load and only after a split second is replaced, does anyone have any suggestions? Edit 2: I managed to get `Method 1` to work, and I was able to append the custom script to the `index.html` using Nano. It turns out I need to learn to use Nano when I want to edit files directly in the container. Was it worth it? Eh, kinda, I was hoping for this to be a 2min job not more Have I learned something new? Absolutelly

I checked and the .ini file that the game spits out, has the `SaveWorldEveryMinutes` set to 0, while the one from your container has 10. And I use the file that the game creates, I will set this value to 10/30 for my server too and let you know. For more context, The server got restarted often because multiple mods got updated in the last 2 days. Anyway, Thank you as always for the quick reply.

@ich777 Do you know if the zomboid server is shut down using the `quit` command in the console? Asking because I'm experiencing zombie respawning in my base after restarting the server after pressing the "stop" button on my container UI A few links with similiar related problems: - https://theindiestone.com/forums/index.php?/topic/50007-4166-mp-server-restart-triggers-zombie-respawn-event/ - https://theindiestone.com/forums/index.php?/topic/45483-4165-multiplayer-zombies-respawn-on-server-reboot/ - In this last link the user says: Please let me know.

Thank you for the reply, Interestingly I didn't have many issues running the Container itself as we only had 3 people at best online at the same time. Regardless I took the opportunity to finally get the 4th RAM stick to go with the 3rd I kept spare. So, right now my miniserver has 33GB of Ram and i'm running a memtest86 to ensure everything is fine.

@ich777 Did anyone complain about the Palworld Container making unraid unstable and freezing it? There are two threads about unraid instability and freezes fixed only by removing the palworld container, mine, and one from @UNRA1DUser

This thread could be related to the this one too, as we both had (almost) the same issue, and similiar solutions.

interesting, that you mentioned the Palworld Server, I had similiar problems since I used that container, but now 6 days after resetting my unraid, and without installing the palworld server my unraid server hasn't crashed once. My post about this similiar issue here if you want more information:

Sorry for the delay, but I have good news! My minimax looks like it's working just fine and I'm on 5 days and 20 hours of it running just fine with a docker container running 24/7 For transparency sake I have do say that I don't know exactly what fixed it. But I can share a list of things I did that might have helped fixing the problem, in order of when I did it. Reseated my RAM as I did get a memtest fail on a single address one night and reseating them didnt cause any fail over 3 different overnight tests. - I had to make sure the ram was matching the slot 1 and 2 of my MOBO to ensure it worked in dual channel. Made a Backup of my cache and 2TB HHD (to use in later step) Unraid 6.12.8 Fresh installed on my USB (Previously it was 6.12.6) Formatted my Cache and HDD to use zfs (Previously xfs) Set my `appdata` `domains` `isos` and `system` shares Primary storage to Cache, and Secondary Storage to None I disabled the VM Manager (I don't need VMs right now, so, I turned it off before changing my docker setting) Set my Docker vDisk location to `/mnt/cache/system/docker/docker.img` Set my Docker Default appdata storage location to `/mnt/cache/appdata/` I left the Docker custom network type to it's default (ipvlan) This time I did NOT run the New Permissions tool to edit my Docker Container files from my Windows machine, instead I followed this guide to set the permissions of my appdata share: I reinstalled the container `assaro/ddbot:latest` I did NOT install the container `scrutiny` and `Palworld` Restored my HDD and cache data from backup and docker config/data files from backup No more steps, I turned on the docker container I needed to run 24/7 and it looks like it's working just fine for now, 5 days and 20 hours later it's still working fine. Notes: I copied the docker location settings from this video I forgot to set up the syslog server, but I will after sending this message.

Okay, I guess I will give it a try, thank you.

Bumping in case someone has any suggestions.

I have been havig a similiar issue on both 6.12.8 and 6.12.6. I even made a post for it, but for now. No luck at all https://forums.unraid.net/topic/156267-6126-random-crashesunresponsiveness-overnight/

@Moderators I got told that apparently the attachments I shared are unavailable Added a backup link for my syslog and diagnostics: https://mega.nz/folder/MUEX2ZRT#HAFjmTNMFTwZ0VxYA8lizQ

I recently bought a basic license, but my unraid has become unresponsive overnight every 2-3 days, and I have no idea how to fix that. The only fix was to shutdown the server using the case button, and turning it on again. It's worth mention that I noticed this behaviour after I set my SSD as cache drive, before I was using the SSD as unsassigned device and everything seemed to work just fine. My Unraid is running on a optiplex 5050 SFF, with the latest bios 1.28.0 - CPU: i7 7700 - RAM: Ballistix Sport LT 16GB Kit (8GBx2) DDR4 2400 MT/s - Cache SSD: SanDisk X400 M.2 2280 128GB - Array HDD: Seagate Barracuda Sata III 7200rpm 2TB - Everything else is stock Optiplex 5050 SFF. Memtest 86+ passed: https://imgur.com/YPYZ0ok I'm also using Docker: - 1 24/7 container using `assaro/ddbot:latest` - 1 container with `scrutiny` running only when needed - 1 container with `Palworld` (ich777/steamcmd) running only when needed - Docker set to use IPVLAN My settings here (imgur) Network Protocol is set to IPv4 Only. I did enable syslogs, and I run all diagnostics. I will attach the logs and diagnostics to this post. minimax-diagnostics-20240303-1221.zip syslog-192.168.0.55.logminimax-diagnostics-20240303-1221.zipsyslog-192.168.0.55.log