Mister Pipps

So, I'm not super great navigating Github. Where would I got if I was looking for the version.php file for lscr.io/linuxserver/nextcloud:24.0.6-ls204 ? Also what commands did you use to set the correct permissions? Thank you in advance!

So it looks like my problem was that I didn't assign a local IP to the container. I skipped over it because Spaceinvader skipped it in the video and it was listed as (optional) in the config. I was able to get a result from apt-get update using both dns=1.1.1.1 AND dns=192.168.111.6 (Lancache-dns) I think I should be able to continue from this point. Thank you so much for all the help! I hope this helps someone else out as well.

I assume you meant to run those commands under the containers terminal, but I ran them under the base unraid terminal too and came up with these results.

Thank you for getting back to me so quickly. I've gone ahead and removed the --dns portion of the config and still no luck. I even uninstalled, removed image and reinstalled once more without making any changes to the default config and still no dice. The only thing I can think of is if there's some sort of filtering on my network going on. I'm using a Unifi Dream Machine Pro for my router/firewall and I use Cloudflares Malware DNS filter 1.1.1.2 and 1.0.0.2 as default DNS for my network. However I've never had any issues like this using any other Unraid Container/Application. IPS/IDS Filter settings in my UDMP Firewall

Hello, I seem to be having an odd issue with Lancache Prefill not fully installing for some reason. I followed Spaceinvader One's video guide on setting up Lancache, Lancache DNS and Lancache Prefill. Lancache itself seems to be working fine as is, but when I try to configure Lancache Prefill I first ran into errors when trying to CD to add in my Steam Credentials. Lancache is at 192.168.111.5 Lancache DNS 192.168.111.6 Lancache Prefill is pointing to 192.168.111.6 in extra parameters. When I enter cd ${DATA_DIR}/SteamPrefill I get this directory not found error. I checked the logs for the container itself and I see this I've tried restarting the container, reinstalling, no dice. Even checked the directory itself and I'm not seeing anything. Like I said Lancache itself seems to be working fine, but obviously the lancache prefill will be a great convenience. Any help would be greatly appreciated, thank you!

Thanks for the help man, the USB was locked down on write protect and no way to salvage it. Restored on a new USB and good to go!

So forgive me if I'm being thick but I plugged my USB into my Windows machine, it popped up there was an error and to attempt repair (I assume that's what you meant by file system check) and I got a message that the disk is write protected. Attempted to unlock disk write protection through DISKPART and it says it was successful, but after plugging in again and attempting repair. It says it's locked again. Is this root of the issue we're looking at? If so, what are my next steps? Wipe and deploy backup? (It's a fairly old backup of USB). I also copied everything off the USB before attempting anything. Thank you!

Hey guys, I wonder if you can help me out. I downloaded some Google Photos container the other day, but then deleted it before really messing with it too much. Then I noticed I couldn't update my plugins for some reason. Restarted server (Uptime 80 days). And tried updating plugins again and get these errors. Here's CA for an example. Then I noticed in the bottom left of the web gui the "starting services" message kept flashing. Pulled up the logs and I'm getting this error on repeat. I posted this issue in the Unraid discord and was given these options. I went through Midnight Commander and from what I can tell, there are no remnants of this Google Photos Container in boot/config/shares, boot/config/plugins/dockerman, boot/config/plugins-removed, and I didn't find a boot/config/plugins-error directory. I have run the Docker Safe New Permissions tool 3 times now and restarted my server after each attempt to no result. What's kind of interesting is that I tried to reboot into safemode to look around some more and now I get this warning when I try to reboot into safemode. Warning: touch(): Unable to create file /boot/unraidsafemode because Read-only file system in /usr/local/emhttp/plugins/dynamix/include/Boot.php on line 87. Impact on the server so far is inability to update plugins, log file filling up constantly, intermittently losing link to "Apps", and a noticeable slowdown in network share performance. Any suggestions on how to resolve these issues would be greatly appreciated!

Yeah mods are weird for 7DtD. It doesn't support steam workshop so it won't natively pull from Steam. You have to download individual mods from sources like nexus and paste them into the mods folder. From what I've seen, most quality of life mods tend to just be XML files that change the game files without actually editing the base config.... something to that effect.

Coooool okay so that got rid of the writing issue however, the mod is still not working. Will try removing all mods and replacing.

Hello, I have an odd issue with my 7 Days To Die server. For some reason some mods are getting a permissions error when trying to apply. So end results is I have some mods that work, but others that do not. These are the mods I've added. The ones that aren't working are the Crafting Queue, 30K Item Stack and vehicle storage is questionable. Here is my container log. Seeing the permissions errors in there, I tried doing a chmod 777 -R /mnt/user/appdata/7dtd/ and a chmod 777 -R /mnt/user/appdata/7dtd/Mods to no result. Any suggestions?

Hey there great guide! Just a couple things I'm having issue with. When I test my custom webhook I get an error response, I'm pretty sure I setup the webhook right. You didn't put much detail into that portion and there's not really much to it on Discord side that I can see. Discord > Server settings > Webhooks > create webhook > webhook name > channel > webhook URL > save. Do you know what I might be missing? The only other things I have issue with are the parsing for Movies Title and Shows Title. Following those particular rules, it pulls some odd information from the email. I don't know if that has anything to do with the error, but that was the only other thing I found was odd, but didn't want to mess with it before testing.