Xed

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by Xed

  1. 4 hours ago, supawiz6991 said:

    Small Update: Updated the plugin to version 2022.08.02a. Still experiencing the problem where when I try to use the production option it still tries to download 515.57 instead of 515.65.01 and fails with: Can't download Nvidia Driver Package v515.57.

     

    Same problem, I selected to download 515.57 from the Available Versions section and it appears to have worked but I have not rebooted yet. 

     

    Switching back to v515.65.01, it keeps throwing CHECKSUM ERROR and "Can't download Nvidia Driver Package v515.57".

    • Thanks 1
  2. I have been using Tdarr AIO to reencode my libraries, first Movies, and now TV library. I did not notice this with the Movies but with Plex, every TV episode that gets converted to H.265 shows up a "new episode" based upon sorting by "By Last Epsiode Date Added", I guess because the file timestamp that is getting written for the re-encoded H.265 file has been updated.

     

    Is there any way to preserve the timestamp in Tdarr from the original H.264 file? It is very hard to track new TV show releases because every few minutes there is an older show that has since been assigned a new timestamp and now Plex thinks it is new again?

  3. On 10/30/2020 at 10:40 AM, clowrym said:

    interessting, I'm having no issues with the latest....not sure what is different with your set up compared to mine.....

    Network type with what used to work (custom docker network - per Spaceinvader One video - Reverse proxy with LetsEncrypt) using "docker network create <name of network>" and choosing that as specific network causes the Docker to fail to bind a listening port on the correct network. I fiddled around with it until I tried "Bridge" as the network type for the docker and then it came up. So I am staying with 2.14 until a solution becomes obvious.

  4. On 10/30/2020 at 11:38 PM, Mechman293homelab said:

    Thanks for the work around. I too am having the "Connection Refused" issue on the latest update.

    Do you happen to be using a custom docker network (e.g. custom : proxynet), like with LetsEncrypt instead of the default "bridge"? This is the reason why the network does not come up properly with 3.0. I have tinkered around with this some more and choosing Network type = Bridge allows the docker to start-up correctly with a network.

     

    I don't have a solution to this if I want the Docker to be on the correct network for external access...

  5. So I am relatively new to Unraid but not new to Linux. I am frequently using SSH to do things that I find more efficient on command-line.

     

    Today I had a power failure and the server rebooted. After the reboot, or at least by the time the array was restarted, all my configurations were wiped, including command "history". So this tells me that root login is on tmpfs?

     

    How can I setup some preferences to survive either a reboot or shutdown/startup of the array?