Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About noties

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So I gave this a try on my UnRAID system and it did not seem to have an effect. It does not appear to put the drives to sleep or UnRAID isn't seeing them as asleep. I was able to manually put them to sleep using sdparm --command=stop. I ended up stopping my testing there. I didn't wait to see if UnRAID would wake the disk on activity.
  2. 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 and I set the docker network type to Custom (br0) and set the IP to static I can ping from any host on my local LAN ( but cannot connect to webGUi or Privoxy. I have the LAN network set to Everything is working fine using Network Type: Bridge.
  3. 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.
  4. 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 on virbr0.IPv4. Registering new address record for fe80::42:dfff:fef8:a351 on docker0.*. Registering new address record for on docker0.IPv4. Registering new address record for 2600:5501:c14:1fa:428d:5cff:fe08:a280 on br0.*. Registering new address record for on br0.IPv4. Registering new address record for fe80::428d:5cff:fe07:a280 on bond0.*.
  5. 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: 2018-03-31 14:45:34,766 (14934930f700) : DEBUG (networking:166) - Requesting '' 2018-03-31 14:45:49,798 (14934930f700) : ERROR (networking:219) - Error opening URL '' 2018-03-31 14:45:49,799 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: 2018-03-31 14:45:49,804 (14934930f700) : DEBUG (networking:166) - Requesting '' 2018-03-31 14:46:04,836 (14934930f700) : ERROR (networking:219) - Error opening URL '' 2018-03-31 14:46:04,837 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: 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 '' 2018-03-31 14:46:20,021 (14934930f700) : ERROR (networking:219) - Error opening URL '' 2018-03-31 14:46:20,021 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: 2018-03-31 14:46:20,027 (14934930f700) : DEBUG (networking:166) - Requesting '' 2018-03-31 14:46:35,061 (14934930f700) : ERROR (networking:219) - Error opening URL '' 2018-03-31 14:46:35,062 (14934930f700) : INFO (__init__:1472) - Error fetching JSON from The Movie Database: Any help or guidance greatly appreciated. Plex Media Server Logs_2018-03-31_14-51-21.zip
  6. So just following up on this thread. Powered down the server and re-seated all the power and SAS cables. I ran SMART short and long tests on both Disk 6 and 7 and they passed. Decided to re-add Disk 7 to the array. It's now rebuilding and so far no errors or issues. I'll be replacing the SAS cable this week when the replacement cable shows up just to be sure.
  7. I guess my question centered around running Disk 6 through a full read which I assumed happened during a parity check.
  8. Thank you for the suggestions. I'm in the process of doing a parity check again to verify Disk 6 that had tons of errors. Also taking your suggestion and looking at files on the simulated disk. So far all the newer files are fine and parity check is 50% done with no errors. I suspect this was either a cable, controller, or (less likely) heat issue that caused the crash and kicked the disk. I'll report back with my continued results.
  9. Don't have a spare mini-SAS cable, but just ordered one. I shutdown and re-seated all cables and power to the drives and booted up again. Disk 6 is no longer seeing errors, but I'm guessing it only resets the counter to 0 on reboot. Should I run a parity check while Disk 7 is disabled to see if Disk 6 is still having issues?
  10. Came home from vacation to find my unRAID server in a tizzy. Not sure if it overheated or just had a brain f-rt. It was locked up - no network, no drives accessible, no web mgmt accessible and spewing the follow errors on console screen (couldn't capture the text): Upon restarting the server, I have one disk disabled and one disk showing errors. Array is started and is accessible, but I'm afraid to write data until I get this figured out. Grabbed a diagnostic and attached here. Wondering if anyone sees something I don't. Just starting the troubleshooting process and wondering if I should focus on Disk 6 or 7 first. teraserver-diagnostics-20180219-0923.zip Any advice would be greatly appreciated. One disk failure, I feel comfortable recovering from, but TWO... UGH! I'm a little worried.
  11. 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; 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; 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 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; }
  12. 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.
  13. 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' -auSOMEONE@gmail.com -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' -auSOMEONE@gmail.com -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 = mta = sendmail action = sendmail-whois[name=letsencrypt, dest=SOMEONE@gmail.com] 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.
  14. I had these same error messages in my docker.log which ended up filling completely: level=error msg="Handler for GET /v1.30/version returned error: client is newer than server (client API version: 1.30, server API version: 1.24)" I narrowed it down by trial and error to the Glances docker. I haven't found a solution yet, but I'd suggest disabling the Glances docker for now.