clincher

DM'd you the log file. I have a remote syslog server and scanning the log real quick, thought it may have an issue with that... not sure.

I'm on 6.8.3 and been messing around with this plug-in. So far the only indication to me that a drive is spun down is that the temperature indicator is replaced with a *. This was the same behavior before this plug-in so I'm not sure it's doing anything in my system. In monitoring my power usage (via Killawatt), it doesn't appear that there is much to any drop is power usage. The green light never goes gray on any of my SAS drives when I try to spin them down. I have a handful of SAS drives that are barely used so I'm pretty sure they're not being spun back up right away. I am getting the spamming of the mdcmd messages in my logs, but I'm not seeing any of the SAS Assist log messages that it appears I am supposed to. Is that right? Oct 5 04:39:58 teraserver kernel: mdcmd (26990): spindown 4 Oct 5 04:39:58 teraserver kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5 Oct 5 04:39:58 teraserver emhttpd: error: mdcmd, 2723: Input/output error (5): write Oct 5 04:39:59 teraserver kernel: mdcmd (26991): spindown 4 Oct 5 04:39:59 teraserver emhttpd: error: mdcmd, 2723: Input/output error (5): write Oct 5 04:39:59 teraserver kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5 Oct 5 04:40:00 teraserver emhttpd: error: mdcmd, 2723: Input/output error (5): write Oct 5 04:40:00 teraserver kernel: mdcmd (26992): spindown 4 Oct 5 04:40:00 teraserver kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5 All of my SAS drives are: HUH721010AL4200 The plug-in seemed to install fine. Happy to help troubleshooting or send logs.

After the array has started is fine. I had planned to run my script using User Scripts, but I need the supported python modules loaded. So I need to essentially "re-install" the Python modules at every boot by running 'pip install xxxx' in User Scripts at boot time? Thanks for the help.

I'm running Unraid 6.7.2 and newest NerdPack. I have a python script that I'm trying to run on Unraid that requires a few custom modules. I've installed them via pip, however, it seems that they get removed after a reboot. Does this sound right? Apologize if this is basic knowledge, but I couldn't find anything in forum archives and I figured since pip is included in NerdPack, that module installs would be carried across reboot.

Is it possible to run Deluge with Privoxy using a custom network interface (br0)? I tried doing this and I wasn't able to connect to the WebGUI nor the Privoxy port. Example: My server is 10.1.1.99/24 and I set the docker network type to Custom (br0) and set the IP to static 10.1.1.98. I can ping 10.1.1.98 from any host on my local LAN (10.1.1.0/24) but cannot connect to webGUi or Privoxy. I have the LAN network set to 10.1.1.0/24. Everything is working fine using Network Type: Bridge.

SRB, I had this issue - it appeared to get fixed by making sure my firewall port forwarding was correct. I had been playing with the port forwarding and had some of it incorrect. Not sure if it'll fix your issue. Sounds like you haven't messed with anything, but give it a double look.

I found this link: https://forums.plex.tv/discussion/259266/401-unauthorized-when-get-metadata-from-all It appears to be related to IPv6 which I have turned on in my network, but do not want Plex docker to pull an address. docker logs show Plex definitely pulling an IPv6 address. How do I go about disabling IPv6 completely in the docker? Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for fe80::42:dfff:fef8:a351 on docker0.*. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 2600:5501:c14:1fa:428d:5cff:fe08:a280 on br0.*. Registering new address record for 10.1.1.99 on br0.IPv4. Registering new address record for fe80::428d:5cff:fe07:a280 on bond0.*.

Hi there, I just upgraded to 6.5.0 from 6.3.5 and right after the upgrade, Plex is no longer pulling down Movie posters or backgrounds. I'm wondering if this may be related to any changes in docker networking or configuration changes in 6.5. This was working perfectly right up until the UnRAID OS upgrade. I see some strange errors in the PlexMediaServer.log but not yielding anything in Plex forums or Google and I'm pretty sure it's related to something in UnRAID. And I see some errors in com.plexapp.agents.imdb.log INFO (__init__:1472) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3Den 2018-03-31 14:45:34,766 (14934930f700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:45:49,798 (14934930f700) : ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:45:49,799 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D 2018-03-31 14:45:49,804 (14934930f700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%2Fimages' 2018-03-31 14:46:04,836 (14934930f700) : ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%2Fimages' 2018-03-31 14:46:04,837 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%2Fimages 2018-03-31 14:46:04,837 (14934930f700) : INFO (__init__:566) - Unable to get TMDb movie data (in Plex Movie) for 0118842: argument of type 'NoneType' is not iterable 2018-03-31 14:46:04,838 (14934930f700) : DEBUG (networking:166) - Requesting 'https://meta.plex.tv/m/0118842?lang=en&ratings=1&reviews=1&extras=1' 2018-03-31 14:46:04,991 (14934930f700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:46:20,021 (14934930f700) : ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:46:20,021 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D 2018-03-31 14:46:20,027 (14934930f700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:46:35,061 (14934930f700) : ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D' 2018-03-31 14:46:35,062 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: http://127.0.0.1:32400/services/tmdb?uri=%2Fmovie%2Ftt0118842%3Fappend_to_response%3Dreleases%2Ccredits%26language%3D Any help or guidance greatly appreciated. Plex Media Server Logs_2018-03-31_14-51-21.zip

I just re-tested and confirmed. If I don't have iptables-multiport as well as sendmail, I won't get a ban. These configs definitely work for my setup. I am only running .htpasswd on one of my NGINX locations if that changes anything. I did notice that the ban can potentially take a second or two to take effect, meaning I was able to get a username/password prompt once or twice more beyond my 5 fail threshold. I figured this is because i was entering wrong users pretty quickly. My default file is below if it helps. I only have security on my /cops/ URL. upstream backend { server 10.1.1.99:19999; keepalive 64; } server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name SOMESERVER.duckdns.org; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; client_max_body_size 0; # location = / { # return 301 /sonarr; # } location /ombi/ { proxy_pass http://10.1.1.99:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://10.1.1.99:3579 https://$host; } if ($http_referer ~* /ombi/) { rewrite ^/dist/([0-9\d*]).js /ombi/dist/$1.js last; } location /cops { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://10.1.1.99:8008/; }

Yes, I tested. I couldn't get a ban to work without adding the iptables-multiport. Are you restarting the docker every time you make a change to jail.local? I found strange behavior unless I restarted the docker. I can test again and report.

GilbN (and others), I'm not sure if you got this working or not, but I'm going to post this here to help others that may be struggling as much as I did with letsencrypt/fail2ban and email notifications. Here are my working configs and steps for letsencrypt/fail2ban and email notifications using gmail. Copy sendmail-whois.conf to sendmail-whois.local copy sendmail-common.conf to sendmail-common.local Make changes to both .local files outlined below. Edit jail.local with changes outlined below. sendmail-common.local (if you don't care about fail2ban start notifications, I think you can skip this) actionstart = printf %%b "Subject: [Fail2Ban] <name>: started on <fq-hostname> Date: `LC_ALL=C date +"%%a, %%d %%h %%Y %%T %%z"` From: <sendername> <<sender>> To: <dest>\n Hi,\n The jail <name> has been started successfully.\n Regards,\n Fail2Ban" | /usr/sbin/sendmail -t -v -H 'exec openssl s_client -quiet -tls1 -connect smtp.gmail.com:465' [email protected] -apPASSWORD <dest> Only need to change the last line. Replace the UPPERCASE with your username and password. Leave all else. sendmail-whois.local actionban = printf %%b "Subject: [Fail2Ban] <name>: banned <ip> from <fq-hostname> Date: `LC_ALL=C date +"%%a, %%d %%h %%Y %%T %%z"` From: <sendername> <<sender>> To: <dest>\n Hi,\n The IP <ip> has just been banned by Fail2Ban after <failures> attempts against <name>.\n\n Here is more information about <ip> :\n `/usr/bin/whois <ip> || echo missing whois program`\n Regards,\n Fail2Ban" | /usr/sbin/sendmail -t -v -H 'exec openssl s_client -quiet -tls1 -connect smtp.gmail.com:465' [email protected] -apPASSWORD <dest> Same thing... Only need to change the last line of the actionban. Insert your username and password where the UPPERCASE is. jail.local [nginx-http-auth] enabled = true filter = nginx-http-auth port = http,https logpath = /config/log/nginx/error.log ignoreip = 10.1.1.0/24 mta = sendmail action = sendmail-whois[name=letsencrypt, [email protected]] iptables-multiport[name=letsencrypt, port="http,https", protocol=tcp] ignoreip is my local home subnet. mta - set it to sendmail action - If you want fail2ban to notify AND add a block to iptables, you need both actions. I couldn't get it to block and send an email without adding both actions. These settings finally worked for me.