Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

10 Good

About PeterB

  • Rank
    Advanced Member
  • Birthday 12/16/1953


  • Gender
  • Location
    Tagum City, Philippines

Recent Profile Visitors

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

  1. Great! Many thanks - all good now.
  2. This update has messed up the display of available disk bays in the Dashboard display. Slot number is too low, LED is too high.
  3. Thanks for that. I can get the configuration interface to come up in the web client, but not in my thin client (running v2.1.1.dev7501). Perhaps I need to find a 2.0.4 thin client for Linux Mint.
  4. Yes, it is possible - I don't actually use the /data directory. I have three separate folders, on three different shares, for leeching torrents, completed torrents and post-processed torrents, like this (simply create new container paths):
  5. If you look in the delugevpn logfile, I think you'll find that it has filled up with many occurrences of I'm hoping that Binhex will eliminate these errors by building the docker with the previous version of Python.
  6. Take a look at the 'downgrade' utility - available on AUR.
  7. Would it be unreasonable to force the docker to build with Python 3.7, for the time-being? Progress on deluge v2.04 appears to be slow, so I would suspect that we are stuck with v2.03 for a little while.
  8. This problem has affected every release since 2.0.3-1-08. I suggest that you roll back to that version.
  9. Have you recently updated your deluge docker container to one which includes deluge v2? If so, CouchPotato does not implement the new V2 deluge interface. You have to set CouchPotato to use the 'Black hole' protocol and use the AutoAdd plugin in Deluge. I've been working like this for months.
  10. See my post above - try reverting to 2.0.3-1-08 of the docker.
  11. Reverting to 2.0.3-1-08 appears to have fixed the problem.
  12. I've noticed, over the last couple of days, my unRAID server running at 99% memory usage and the UI becoming unresponsive. Yesterday I rebooted the whole server but, 24 hours later, I'm seeing the same problem. Now I discover that if I restart DelugeVPN, the memory usage drops back down to less than 30%, but then creeps up again. Looking in deluge logs, I see repeating series of entries including the line mentioned above: As far as I'm aware, deluge has been at v2.03 for a few months now, so how come this has just started happening?
  13. My Linux Mint client reports 2.0.3-2-201906121747-ubuntu18.04.1
  14. Your LAN_NETWORK is set to yet you're trying to access 192.168.100.*. Change your LAN_NETWORK to
  15. Weird - I wonder why it's stopped working, then?