• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

5unny's Achievements


Newbie (1/14)



  1. 145 doesn't seem to work for me still have the same issue
  2. Not currently, I can't get it to run for long enough before I get locked out. Is it worth rolling back to an earlier version or a way to run the instruction/actions, it's been around 5 days since the last reboot with the docker running. Would you mind sharing your workflow? Not experienced any issues bar this since running unraid, this one is just annoying!
  3. Thanks for the tip, I rolled it back but still seem to have an issue where it drops off and I can't get back in without rebooting. Wondering if its an issue related to Unraid. Been through the logs and noticed 2 errors but not sure if they are directly related; Nov 28 17:29:13 Server kernel: CPU: 2 PID: 3756 Comm: deluge-web Not tainted 4.14.26-unRAID #1 and; Server nginx: 2018/12/02 [error] 1878#1878: *693231 upstream timed out (110: Connection timed out) while reading response header from upstream, client:, server: , request: "POST /plugins/dynamix.docker.manager/include/Events.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "", referrer: ""
  4. I have a strange issue with my Deluge container, initially once it is running it will operate fine but after a period I can't access the webui or restart/stop the container. The only method I've found to get it running again is by rebooting unraid but the same issue will occur after a period of time. No idea what the cause is, used to work fine with no issues but struggling to get past this, any ideas what it could be?
  5. I need some help! I've been using unraid for a year now and its been great but recently come across this across this error (appearing on all linuxserver.io dockers) - 'Error: Error while pulling image: Get https://index.docker.io/v1/repositories/linuxserver/plex/images: dial tcp: lookup index.docker.io: connection timed out' I'm not experiencing any net issues and it recognises an update is required across all of my containers but gives the same error. Any help would be great. Thanks