pish180

Thanks that was very helpful mod and if it was also you with the quick license change thanks for that as well! Almost everything was recovered since I had the cache drives with all the appdata stored there and I was able to identify which drives were the parity drives. I also solved another issue that I was having with Radarr and got confirmed the backups are running with Unraid Connect. The Unraid Connect backup feature is really nice! Great feature! Highly recommend getting that setup ASAP! I do wish you could move you license manually but it was a pretty quick turn around after I posted here and sent in the email. Thanks! One thing to note for anyone who searches in the future. You can "pause" the parity rebuild but you can't "stop" the array and think it will pickup where it left off. I did this while reconfiguring Unraid and it had to start all over again. Just let it rebuild. It would be nice if the rebuild had a state file when it is restarted to continue where it left off. Overall off one of the easiest systems to recover from and I've had many RAIDs and severs go bad on me in the past. Good stuff!

Yup this sucks. I swear I had setup backups to the Unraid connect but it doesn't seem to be there. So I need to get my license transferred to my new GUID USB drive. I sent support an email already. I do not know which drives went where. I had 2 parity, 8 data drives, 2 cache drives (1 was no present, being replaced at the time of failure), 1 unassigned drive. How am I am able to figure out assignments? Can I mount the drives via console and see what is on them? I think I read the parity drives won't mount or something. Not sure. Any help would be appreciated.

I have a similar question on this topic. I am running Dual Parity with 10TB drives and all my data drives are 10TB. One of my data drives needs to be replaced but I only have 2 x 16 TB drives for replacement. Do I have to replace BOTH parity drives before I can start upgrading the capacity of the data drives to 16TB drives? OR can I upgrade 1 parity drives with the 16TB drive and then upgrade the failing data drive with the other 16TB drive? What would be the recommended procedure in my case?

Amazing job! App works amazing and is so much better to use than the ones in Sonarr and Radarr!

If anyone is having this issue I think I resolved it. Not very hard but did require time and tinkering. You will need to open a console to the UnRaid server and everything will be done under /mnt/user/appdata/ First try and get Sab to boot so you can get to the config settings menu screen. I had to chmod 655 the sabnzbd.ini file. Do this from the console (mentioned above). This file will be sabnzbd/sabnzbd.ini Restart the container once you do this from the Unraid UI. Go to the settings menu within Sab and backup your Sab settings. It's at the bottom and says "download backup". You should now have a sabnzbd-config.zip file on your local computer. Stop the Sab container From the console mv the sabnzbd folder to sabnzbd2 (just so you have the orig) (basically just renaming it). Start Sab container (This is going to cause the container to rebuild the files). If you had https it likely won't work so navigate to your http port. Mine was 8080. You should see a Sab setup wizard screen with an option at the bottom to import a config. Import the config. Save settings, Restart Docker. Test to ensure everything works. (Mine changed internal docker IP so I had to update Radarr, Sonarr, Lidarr, etc). Once I did this no more errors in my Sab docker logs. I noticed that after docker rebuild everything that nothing is root anymore in the sab folders. Confirmed this with an ls -al in both sabnzbd (after this process) and compared it to sabnzbd2 (folder that I backedup). Everything is set to nobody users. I'd image another fix would be to just reset all the perms from root root to nobody users may fix the issue. However I think having it fix it all was a better option. Hopefully this helps someone.

Messing with it a bit. I had to set the sabnzbd.ini to 655 to get it working. I was watching the log and there were other permissions issues. I had to change the admin/rss_data.sab to 666 Then it complained about can't Write to "History database" Which is (also at the default) set to 644. I'm guessing there is going to be more with the current trend. I recently upgraded both the SAB container and Unraid to 6.10.2 from 6.9.2 so I'm not sure what update broke it/updated perms. Anyone else having this issue?

After upgrading to Unraid 6.10 I am getting permissions errors on the docker config file. If I need to change this, what should it be set to? Perms on config. I assume it means this config file (/mnt/user/appdata/sabnzbd/sabnzbd.ini)

Prefect that worked! Had to restart FF after I applied the changes though.

Weird. I got some new monitors... the problem is gone. I'm guessing it more windows display setting issue than the actual monitors but still very weird. Anyways, looking forward to the 6.10 and hope the problem doesn't come back. As an FYI - Old Monitors were MSI MPG27CQ and the new ones are Samsung Odyssey G7s

Outstanding thanks. I'm on Unraid 6.9.2, any ideas on when 6.10 is going GA?

Bump, This is still an issue for Chrome on a Windows machine. This is the most widely used Web Browser out, really need to resolve this, thanks! Confirmed still broken with Chrome 95.0.4638

Any idea if you can use the configurator on a Dell PowerEdge R730XD? I have the 10G NIC installed and the fans go absolutely ballistic. I've ran the manual ipmitools command which drops them down to 9,500 RPM (ish) which is still VERY loud. I was rather hoping that I could use this tool to set the speeds lower to say like 7-8k RPM. I always Get this message when I go to Fan Control Tab. It tells me to click on configure button but there is no configure button. Any ideas?

Any of the devs consider looking at this? Maybe something like Anchore, Clair, etc or another docker file that we can add to Unraid that would scan all the docker images we have in our Local Docker Repo and provide a report for UnRaid users? I think this would be really valuable for the community so they know of the images they are running, if there are any vulnerability and let them determine if its an acceptable risk. Thanks!

Maybe a second look for an interested container expert to get this working for the community? Please.

Did anyone figure out the umask setting or how to get Qbit to write files with different permissions so that someone other than nobody/users can access the files? Currently all files are written with 755. I would also be even more happy if I could change the user from nobody to a set user that I already have set. The one post I read claims that the following works: set -e UMASK_SET=000 It however breaks the image and makes you have to redeploy the container using the "Add Container" at the bottom and choosing the template and then removing the extra line (that you just added). -- FYI for those who had the issue. Not sure if someone here is a bit more advanced with this container and/or permissions but it would be very much appreciated if you could provide some insight to this issue. Thanks!

Is anyone able to get this to work on the UDM Pro? I posted a community post in the Ubiquiti forums about this as well and contacted their support which deferred me to the Unifi forums. https://community.ui.com/questions/DNS-Rebinding-and-UDM-Pro-Unifi-Dream-Machine-Pro-Plex/6fcc3157-0352-4f1e-a582-a1810c437ab0

DOH. Are one of the mods able to move it? I swear I recall trying to and there was no button to create a thread. I guess as you mentioned I was probably in a sub-forum. Ideally I would like it in the FR section. If not I guess I can re-create it there.

That's a good point. I would have put this post in the request section but that is blocked off. The goal with this post is really 3 things: 1. Hopefully build some interest amongst the community 2. Once we have some interest, see if any devs want to take on the challenge. 3. End Product? Wanting to volunteer someone else's time. - Seems like a negative way to word it. If that is what you consider a request to build something is then I guess I'm guilty. 🙄 Every project starts with an idea/request/issue. With more users backing a request a dev would feel. 1. More motivated 2. More likely to be incentivised 3. Have a positive impact on the community Depending on what motivates them. FTR I have supported many developers via Patron and other donations for their work. Just wanted to throw that out there. Hope that helps.

Comment: Honestly surprised this has not receive more attention in here... Considering Unraid primary function is to house all your data as a NAS and I'd image many people store sensitive or personal data/documents on their servers... right? Combine that with running applications (docker images) that share the same kernel and mounted filesystems that someone else (other than the programers) are building (the docker images)... nobody is concerns? If if you trust the image owners, after they are deployed nobody has concerns about them containing exploits or knowing if they are vulnerable? I'm not sure if everyone is naive or just doesn't care about their data on their Unraid server or their home network in general. Can anyone who doesn't maintain the docker images tell me if you have CVE-2019-5021 on your Alpine linux running containers? I'd guess nobody can confidently answer that without spending significant researching it or already have tools scanning. Supporting Info: This is a decent writeup back in 2017. https://sysdig.com/blog/7-docker-security-vulnerabilities/ Also this in 2019 (has video) https://www.techrepublic.com/article/docker-containers-are-filled-with-vulnerabilities-heres-how-the-top-1000-fared/ Summary: My point is that many of these containers are communicating with the internet. 1. We don't know what is in the images we are downloading/updating. (unless you are one of those people that hash matches all the binaries and configs to the master). 2. Your containers will or do have vulnerabilities and you will have no idea about it. If you are running a container that the image maintainer stopped updating (maybe they are on vacation) and an exploit is discovered, well good luck. Considering the current state of the world with CoVid19... you will see an increase of ransomware! It won't matter who you are... people need money and take advantage in times like these. I can personally attest to this: I have a unifi firewall and it is running IDS and the amount of attacks against my IP has increased. https://www.businessinsider.com/ransomware-attack-hospitals-coronavirus-covid-19-2020-3 Want/Ask/Need: I would really like to see some integrations of tools that scan against the images and running containers. There are a lot of smart people in here and I'm sure everyone can benefit from having a container that does scanning of other containers. Wouldn't it be nice to know you have a problem with a docker (a CVE was released yesterday) and this image is vulnerable. That could allow you to at least disable the services until it is updated or follow the CVE and perhaps mitigate the risk another way. Disclaimer: I am not a dev. I want to generate interest from the community and see if any devs would be interested in this project. As GI Joe says.... Knowing is half the battle.

It would be nice to see some security tools around the docker. For example maybe something that can do vulnerability scanning and reporting of your running containers. It would be helpful for many reasons, perhaps adding additional firewall rules to prevent attacks, upgrading, downgrading etc. I know there are open source tools and images that already exist with many features that we could all benefit from.

Thanks for the replies. 1. Perfect thanks. (confusing because there is a ddclient.conf file in "/", "/etc" and in "/config". 2. It's more of a sanitary/security/housekeeping concern. This docker has 1 specific task to accomplish so IMO it really should just execute and be done. 3. How is ddclient being executed? (quick look at the github page, seems it's using s6? which i'm not familiar with at all) (I looked at the obvious cron.* and crontab and that's not being used). Politely My Feedback: I think it would be helpful for anyone using this docker to know: 1. A description of which conf file to modify. (this is somewhat mentioned in the "Application Setup" section on the other links but not on the Unraid Posting). The clutter of other ddclient.conf files makes it confusing. Application Setup Edit the ddclient.conf file found in your /config volume. This config file has many providers to choose from and you basically just have to uncomment your provider and add username/password where requested. If you modify ddclient.conf, ddclient will automaticcaly restart and read the config. 2. A description of how the conf file is executed and when. Noobs to s6 would find this helpful. 3. Overall this is a great addition to my Unraid server it just needs some polishing on the documentation. --------------------------------- I'm not good a writing scripts but I would image we could have ddclient return a result and then run the shutdown command? Not sure anyone would want to help me and the community write a script? 1. I was thinking something that would execute on boot but have a prompt, press any key to cancel (wait 30 seconds if not response and then execute). This would allow the admin time to cancel the execution and make changes (via Docker exec console) if necessary. 2. A nice to have would be a simple log output added to the appdata folder that says ddclient executed success/fail - %date stamp%. 3. Running the container on a schedule can be done via CA User Scripts app which requires another script. CA User Scripts allows the Unraid script to be added to the cron tasks for the Unraid server. I would image this would be a docker run script? I would need some help there as well. Hopefully what I'm mentioning would help everyone looking to use the ddclient container.

A few questions. 1. Which config are we editing? The one in appdata or are we editing the one in the filing system? There are several. 2. Which config is the container executing? All the documents say: /etc/ddclient/ddclient.conf. Is part of this setup of this container to transfer the config file to that location? 3. It is 100% not necessary to have this container running all the time. It has 1 function to and then then should exit/shutdown the container. This is a 2 part question. Can this be done natively? If so what would be the recommended path? 3a. Does the container automatically execute the ddclient command? Is it using cron? 3b. Pardon my newb-ness in Unraid, Can we schedule this container to execute every hour to execute the command it needs and then shutdown the container? Any help with this would be greatly appreciated if it is a script. Thanks!