ATEglauer

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

ATEglauer's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I'm getting a warning message in my log every 30 minutes (I'm using the latest ( ? ) docker image as of 3 days ago). 2021-02-11 18:08:37,353 DEBG 'watchdog-script' stdout output: [warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed I found a post for DelugeVPN that had the same issue almost a year ago that was resolved per this post: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/page/243/?tab=comments#comment-857506 @binhex I'm assuming a similar cause and fix can be made or is this something on my end?
  2. I have no idea, really, but when I tried to change server hardware on my system, the new system didn't see any of my array drives - they were 3TB and mostly 4TB drives. I switched back to my original server hardware and still, no drives were seen by unraid. They did exist, but couldn't be read. (I later discovered the backplane in my new hardware couldn't read drives over 2TB.) It seemed the new hardware changed the partition table for my array drives. I used GDISK to recreate the GPT (partition table) and then all drives were back to normal. A big relief for me at the time! Perhaps try that and see if the partition tables on the drives can be restored. I am a beginner at this stuff and was pretty nervous with messing with partitions on the drives, but in the end I didn't loose any data - only some sleep until I used GDISK! Armand
  3. I don't really know what is or might be going on for you, but I had a similar issue. Here is my similar post: https://forums.plex.tv/discussion/308232/why-would-tv-episodes-not-play-from-a-remote-client#latest Maybe that thread (and probably the link to another forum post) will provide you an answer/explanation; I didn't really understand it, but the solution worked for me! Since that post, I have switched to the Docker version and things have remained fine for me and remote clients; I didn't need to change permissions after switching from the plugin to the docker version.
  4. DOH! .... I got caught up in configuring it through rtorrent.rc and it didn't dawn on me to set it up through the UI (after all, the comments in the .rc file says to disable it!). Anyway, all seems good again. Thanks!
  5. I've followed the above instructions and things are working OK with only one issue. Can I no longer use the move completed downloads option in rtorrent.rc? I had disabled it in settings in the UI, but completed downloads are no longer moved to a different directory. I have tried adding these lines to rtorrent.rc, as it worked with the earlier versions: execute = {/bin/bash,-c,mkdir -p /data/2-downloaded} system.method.set_key = event.download.finished,move_complete,"execute=mv,-u,$d.get_base_path=,/data/2-downloaded/;d.set_directory=/data/2-downloaded/" So, I dug around a bit and found the following in the Wiki for common tasks for rTorrent: execute = {/bin/bash,-c,mkdir -p /data/2-downloaded} method.insert = d.get_finished_dir,simple,"cat=~/2-downloaded/,$d.get_custom1=" method.set_key = event.download.finished,move_complete,"execute=mkdir,-p,$d.get_finished_dir=;execute=cp,-R,$d.get_base_path=,$d.get_finished_dir=" This also doesn't seem to work, , but I am not sure I added the the completed downloads folder (/data/2-downloaded/) properly. Can anyone shed light on how I am best to move completed downloads?
  6. Yes, it seems to be working here too.... thanks to binhex for the quick update!