• Posts

  • Joined

  • Last visited

jmmrly's Achievements


Newbie (1/14)



  1. Would it be possible to add an option to Force update all containers, even if there isn't an update? My docker file keeps slowly filling up, and force updating all my dockers resets that.
  2. It looks like the settings within plex for limiting upload are for plex pass users only, which i'm not. On the docker page about docker run reference, I can't see anything to do with network limiting, only setting different networks and limiting cpu etc. Could you please help point me in the right direction? Thanks
  3. Hey, I have an issue where, if enough people are streaming my Plex, my network slugs down when reaching my network upload max. I'd like to limit the Plex Docker container to a lower network upload speed. Is this possible?
  4. After waiting a while, the drives are actually going to sleep. It's just misleading seeing all the little reads. The revert to 6.9.1 looks to of solved it, thanks
  5. Unfortunately this didn't work, i'm still getting lots of little reads on every drive.
  6. Hey, The past few days i've noticed all my drives were awake, when they usually aren't as it's mainly plex media on my drives and they spin up when being streamed. Even the parity drive is being kept awake. I don't think i've changed anything but i've been running unraid for years without issue, and suddenly past few days they're all being kept awake. I'm noticing very small reads every 30seconds or so on all drives. Ignore the errors in the logs about github being unreachable etc as there's currently a world-wide site downage
  7. Hmm. I'm only using SWAG as it runs a couple of wordpress sites as well as running proxy. This is my proxy config; server { listen 443 ssl; listen [::]:443 ssl; server_name plex.*; include /config/nginx/ssl.conf; client_max_body_size 0; proxy_redirect off; proxy_buffering off; location / { include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_app; set $upstream_port 32400; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Plex-Client-Identifier $http_x_plex_client_identifier; proxy_set_header X-Plex-Device $http_x_plex_device; proxy_set_header X-Plex-Device-Name $http_x_plex_device_name; proxy_set_header X-Plex-Platform $http_x_plex_platform; proxy_set_header X-Plex-Platform-Version $http_x_plex_platform_version; proxy_set_header X-Plex-Product $http_x_plex_product; proxy_set_header X-Plex-Token $http_x_plex_token; proxy_set_header X-Plex-Version $http_x_plex_version; proxy_set_header X-Plex-Nocache $http_x_plex_nocache; proxy_set_header X-Plex-Provides $http_x_plex_provides; proxy_set_header X-Plex-Device-Vendor $http_x_plex_device_vendor; proxy_set_header X-Plex-Model $http_x_plex_model; } } and all I get is this;
  8. Hey, I've added plex into my SWAG reverse proxy docker, and added my SWAG certs within network settings of plex, and also my plex domain name in there. When I access, I just get the plex logo and nothing else. Is this as expected or should I be able to login?
  9. Yeah looks to be sorted now, very strange.
  10. Hi, I updated a plugin and now my GUI seems to be screwed. I can't click on anything apart from the tabs, dashboard, plugins etc. On f12 i'm seeing some warnings for the following file; /usr/local/emhttp/plugins/dynamix/include/PageBuilder.php : syntax error, unexpected '=' in Unknown on line 13 in : syntax error, unexpected '$' in Unknown on line 17 in I'm running Unraid 6.9
  11. I have the exact same issue. I thought the docker was borked when accesing on chrome but trying another browser worked. Even chromium edge worked.
  12. It's only been on for about half a year. What can be the cause? It's sat in a desktop case with 4 other drives. Is it the vibrations causing it or just a naff drive?
  13. Running an extended SMART test has showed up more errors. Not looking too healthy. ST8000DM004-2CX188_ZCT2HVKT-20201128-2142.txt
  14. I got a warning about a 'Report Uncorrect' On my parity drive. I've never seen this before and the drive isn't that old, it's about half a year old. I've attached the smart log. Should I be concerned? ST8000DM004-2CX188_ZCT2HVKT-20201128-1403.txt
  15. Solved my own question by just doing it, and yes it works Only 10 min downtime for 150gb ish