• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About drsparks68

  • Rank


  • Gender

Recent Profile Visitors

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

  1. Is there any indication that this project is still active? Looks like @testdasi hasn't logged in since October.
  2. I spent 2 days trying to figure out why none of my Plex content would play, until I realized this. The change could have used a little more announcing.
  3. Trying out PhotoPrism and attempting to import photos but I don't have an "import" button in the library tab...just Index, Copy and Logs. I have the import folder mapped to a folder on my array and have populated it with sample images, and have even tried running Docker Safe New Perms, but still no import button. What am I missing?
  4. Now it seems that Fail2Ban isn't working at all...or at least none of the default jails flagged this traffic and banned the source IP (and there were over 600 lines of it in the NGINX access.log):
  5. Hello all, I am trying to configure f2b for permanent bans. I have started the container with "--cap-add=NET_ADMIN" and have set the bantime to "-1" for each jail (as noted under "Jail Options" at https://www.fail2ban.org/wiki/index.php/MANUAL_0_8). I am able to see IP's being detected: 2020-03-30 22:04:20,572 fail2ban.filter [392]: INFO [nginx-botsearch] Found - 2020-03-30 22:04:20 2020-03-31 06:46:10,028 fail2ban.filter [386]: INFO [nginx-botsearch] Found - 2020-03-31 06:46:09 2020-03-31 09:29:25,
  6. It ended up being bad memory for me. Once I removed the bad stick the machine check events went away.
  7. I'm hitting this as well. I spent days looking at my internet connection and DNS to figure out what's going on. At least now I have an idea what the culprit is. Have you opened a bug on the Github page (https://github.com/linuxserver/docker-plex/issues)? That may be the best way to get a response.
  8. Hermy65, Looking at the issue on the LS github (https://github.com/linuxserver/docker-mylar/issues/33) there is a suggestion that running the following in the container directly will mitigate the issue, at least temporarily: pip uninstall requests pip install requests I just tried it and it allowed all of the pending comics to be successfully post-processed.
  9. Yeah, I'm running into this as well in addition to the cache folder (appdata\mylar\mylar\cache) filling up with a bunch of folders with names like "mylar_mP29Lt". It completely filled up my cache drive and caused a couple of other containers to stop working until I deleted them all. That was yesterday. Today the cache drive (500GB SSD) is half full again.
  10. I had no idea that setting was there. Got it working after I removed it. Thanks!
  11. Assuming that subfolder support would mean that an app like Ubooquity would be supported (it's URL string is http://<IP>:2202/ubooquity/admin)?
  12. Anyone? I keep getting this message and Google doesn't seem to be any help whatsoever. Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged
  13. I've been getting machine check events and am looking to troubleshoot the issue. I have mcelog installed through Nerd Tools, but when I run 'mcelog', I get the following error: "mcelog: ERROR: AMD Processor family 21: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported" I've searched on how to install the edac_mce_amd module but haven't found any good instructions yet. Anyone know how to install it so I can troubleshoot my server issues? Many thanks
  14. So, I've been following this guide to set up MariaDB/Nextcloud/Let's Encrypt. Things were working well until I got to the point that I created a file to put into the LE App data folder (/config/nginx/site-confs/nextcloud). Since then, I've been getting the following error in my LE docker log, over and over: nginx: [emerg] the size 10485760 of shared memory zone "SSL" conflicts with already declared size 52428800 in /config/nginx/site-confs/nextcloud:20 When I set the LE container up, I set it to use a subdomain only (my nextcloud instance) and it has created the certs