johnc

Had the same issue. This resolved it for me: https://docs.microsoft.com/en-us/troubleshoot/windows-server/networking/guest-access-in-smb2-is-disabled-by-default Add the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth (dword) = 1 The logs about the security error are shown in event view here: Applications and Services Logs -> Microsoft -> Windows -> SMBClient -> Security

Sickrage is not working due to a bug in Sickrage that was fixed about 3-4 days ago (it's an error in scene_exceptions.py if you look in the sickrage logs). It looks like the docker may have been updated recently but not enough to pull in that fix. binhex, can it be updated?

I just updated sabnzbd and now it's failing to start. Looks like the /opt folder inside the docker is empty.

I'm sure that's just a cut-and-paste error from another docker. sabnzbd *IS* the downloader. Just think of /data as your "downloads" folder.

In Sickrage it's in the General section and is called "Show root directories where the files of shows are located." It should be the same or similar in Sickbeard.

I think you may have some problems with your folders in your docker setups. And there's also a setting for the watch folder in your autoProcessTV.cfg which has a path that won't work inside your docker. Here are all of the docker paths I have configured for my own sabnzbd and sickrage dockers: sabnzbd: /config = /mnt/cache/.sabnzbd/ /data = /mnt/cache/.Download/ sickrage (will be same as sickbeard settings): /config = /mnt/cache/.sickrage/ /data = /mnt/cache/.Download/ /media = /mnt/user/ (note: I also have sickrage configured to store all media into a TV folder so it will use /media/TV) Comparing these to yours, I suggest these changes: 1) Configure both dockers to the same /data folder. In your case, I think that should be "/mnt/cache/.sabnzbd/Downloads". Do not include the "complete/TV" part - both apps know that structure so you don't specify it here. 2) Since you have sickbeard configured with /media = /mnt/user/Media/TV, make sure that your setting inside sickbeard is just "/media". 3) Edit your autoProcessTV.cfg again and change the watch_dir path to "/data/complete/TV". I don't actually have that setting at all in mine (but I think my scripts are really old) so I'm not sure if it's used or causing a problem - but that path is definitely wrong from inside the docker. Good luck, I think you're almost there!

I can't say why it would show successful when you test. Mine does not... But as for your configuration, based on what you've said above: 1) You should configure sickbeard with a SABnzbd server URL of "http://192.168.1.103:8081/sabnzbd/" 2) For sabnzbd: edit your autoProcessTV.cfg file in your /config/scripts folder. In that file, set host=192.168.1.103 and port=8082. That should get them talking to each other on the correct IP:port.

I think you need to configure sickbeard to send to sabnzbd using a full IP address (not 127.0.0.1) as if it was sending from another machine in your network. For me, my unRaid server is at ip 192.168.1.51, sabnzbd has a host port of 8081. My sickrage (same thing as sickbeard - it's a fork of it) has it's SABnzbd server URL configured as "http://192.168.1.51:8081/sabnzbd/"

You can connect to the docker using "docker exec" like this (from an ssh/telnet session into unRaid): docker exec -it binhex-sickbeard bash replace "binhex-sickbeard" with the name of the docker container. For that, you need to look in your config ini files. If you changed the host port to 8082, then you need to also configure that port in your ini file. For sickbeard, that's the "config.ini" file in your config folder. Edit that with a text edit and search for "web-port", set it to 8082, save it and re-start your docker. Do the same for sabnzbd if you changed that port (config file = sabnzbd.ini and setting is "port"). Sorry, I told you this backwards... In those .ini files, you need to configure the ports to match the "Container port". So if sickbeard has (in the docker config) a container port of 8081 and a host port of 8082, you need to configure 8081 into the .ini file. Your unRaid server is basically routing port 8082 into the docker to port 8081. So your docker app (sickbeard) needs to be listening on port 8081.

You can connect to the docker using "docker exec" like this (from an ssh/telnet session into unRaid): docker exec -it binhex-sickbeard bash replace "binhex-sickbeard" with the name of the docker container.

ive actually applied the fix this morning, so if you now do a check for updates and then force update for the docker containers your interested in then it should work fine. thanks for reporting this issue, one of the nice side effects of sharing your work is debug by end users Thanks for checking on that so quick. But that didn't fix the issue. And it's my fault. I had tried a couple things to get it to work and didn't realize a change to the PRIMARY group was needed also. I re-tested a couple times (from scratch each time) using your latest dockers. This procedure (and in this order) fixes it every time: usermod -g users nobody usermod -G users,nobody nobody Then restart the docker. Sorry about that.

yes i have been aware of this just not really looked into the fix, im assuming you have created additional users and thus not accessing your shares as user nobody then, yes?. i can include the fix as you detailed, it will take a little while to ripple down though as the fix will be applied at the base image. Thanks, that would be great - no big rush since I know how to fix it. And yes, it caused issues for me because I have an additional user (which then could not access any of the new directories that had been created under the "nogroup" group). Maybe another workaround for me would be to add my user into the "nogroup" group, but I hadn't thought to try that that. In the meantime, if anyone else hits this, here's how to fix it: docker exec -it binhex-sabnzbd usermod -G nobody,users nobody Then restart the docker container. Repeat for any other dockers (for me, that's Couchpotato and Sickrage).

I am having an issue with the permissions of files created by the dockers. I'm not sure if it's specific to the binhex dockers or just unRaid dockers in general. But I'm specifically seeing it in the bixhex sabnzbd and sickrage dockers so I'm starting here. What I'm seeing is that all files/directories are being created with an owner of "nobody" and a group of "nogroup" when they should be nobody:users. I shelled into the dockers and ran "groups nobody" and the output I get is just "nobody". That should say "users nobody". So I then executed "usermod -G nobody,users nobody" and restarted the docker. Now everything is being created as nobody:users as it should. So I'm not sure where this needs to be done, but it looks like the "nobody" user needs to be put into the "users" group somewhere along the way.

The md5 for that file is: a6f1606b7fc032d28937a75c0cd3ae68 It also needs to be changed in the web server .plg as well. In both cases, like this: <FILE Name="&pkg;/sqlite-3.7.16-i486-1.txz" Run="upgradepkg --install-new"> <URL>&ur2;/ap/sqlite-3.7.16-i486-1.txz</URL> <MD5>a6f1606b7fc032d28937a75c0cd3ae68</MD5> </FILE>

Same thing happened to me. It turned out to be CouchPotato (v1) . I ended up updating CouchPotato to v2 as well as sabnzb and sickbeard using Influencers packages here: https://github.com/W-W/unRAID. To see if this is the case for you too, disable them all then reboot and see if it comes up clean. Then update 1 at a time.

Attached to this post is an unMenu package to install the "dnsmasq" service. This is a very lightweight DHCP and DNS server. Credit goes to aaronjb who first showed us how to do this here. Why would you want to do this on your unRaid server? In my case, I have a Netgear WNR2000v3 wireless router. Like most routers we all have in our home networks, it provides DHCP and appears to provide DNS. The reality is that it only provides "DNS forwarding" which blindly forwards all DNS requests it receives to the name servers provided by your ISP. This means that even though it will assign IP addresses to your local machines via DHCP, it won't respond to any DNS requests for those same machine names. This is not a problem if you only use Windows machines because they will resolve themselves using Netbios. But trying to resolve your local machine names in an OS that doesn't support Netbios - such as Unix and iOS - will result in disappointment. If your router is supported by Tomato or DD-WRT then you can also solve this by upgrading your router firmware to one of those packages which support full DNS of your local machine names. But if your router is not supported (like mine) or you don't wish to do that, this is a very simple and low impact way to put those services on your unRaid server. Installation Instructions: First, make sure your unRaid server is configured to use a static IP address. It will not be able to use DHCP to get an address from itself since the dnsmasq package won't be installed until after the network initializes. Copy the dnsmasq-unmenu-package.conf into your /boot/packages folder then use the unMenu PkgManager link in the Web GUI to install it and set it to auto start. Note: If you have a cache drive in your system, the "config-file-dir" Configuration Variable will default to storing the configuration file on your cache drive in /mnt/cache/.dnsmasq. ** If you do NOT have a cache drive, you must change this to be located on your flash drive. i.e. "/boot". If you do not do this, your config will be lost on reboot! After installation is complete, you will need to edit the dnsmasq.conf file (see above for location) and configure it for your network. The default dnsmasq.conf file contains all of the available options as well as comments about what each option does but will have all options completely unconfigured. Disable DHCP on your router. This should immediately cause your clients to request new addresses which should be assigned by dnsmasq on your unRaid server. As an example, these are the options I set in dnsmasq.conf on my server: domain-needed bogus-priv local=/local/ dhcp-range=192.168.1.100,192.168.1.150,72h dhcp-option=option:router,192.168.1.1 dhcp-option=option:dns-server,192.168.1.51,192.168.1.1 dhcp-leasefile=/boot/ConfigFiles/dnsmasq/dnsmasq.leases dhcp-authoritative local-ttl=60 Please read the comments in dnsmasq.conf for details. But this config is that is needed to... 1. Serve DHCP addresses in the range of 192.168.1.100-150 2. Set the gateway on the clients to 192.168.1.1 (which is my Netgear router with the internet connection) 3. Set the default DNS server on the clients to be my unRaid server (the .50 address) with a backup of my Netgear router 4. Store the lease file on my flash drive so it's persisted on reboots. (I don't have a cache drive installed yet) After making changes to dnsmasq.conf, you can restart it via: /etc/rc.d/rc.dnsmasq restart This has been tested on unRaid 4.7 and 5.0b14. dnsmasq-unmenu-package.conf