Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

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. That's odd! As I understand it, that has to be a problem with the VPN tunnel being established. If the VPN is down, all connections are disabled. Why that should change between the two releases is a puzzle. I would try re-configuring all the docker/container settings - particularly those around the VPN. Sorry, I'm lazy to go back through your posts - is there anything odd at all in the container log relating to the VPN? Yes, I'm using PIA, currently on the Czech endpoint.
  2. I didn't have to alter any docker configuration, and the web UI works fine. Have you tried clearing browser cache, etc.
  3. Indeed, I have been using deluge v2 for just over a week, and it is running just fine. The thin client is working well - but I do run Linux for my desktop. I like all the new features - a welcome upgrade! I also use the CouchPotato docker and have it set to use Black hole to upload torrent/magnet files to deluge - it does everything I need.
  4. I'm not using Black Hole but, since the deluge interface from CouchPotato no longer works with deluge v2, I have set CP to use the BH method of sending magnet/torrent files to deluge V2. Simply configure the 'AutoAdd' plugin in deluge to find the magnet/torrent files.
  5. I've just noticed that my deluge wasn't reporting any transfers. Test active port was failing too. I restarted the container, everything is back running. I found this: in the log. I'm guessing that it all stopped at: 2019-06-26 09:11:29,128 DEBG 'watchdog-script' stderr output: Unhandled Error
  6. All plugins will have to be modified/re-written for the new application interface, and converted for Python v3.7
  7. The new deluge release adds a number of facilities over v1, which had been untouched for some years now, and improves performance considerably. I, for one, am extremely happy to have v2 available. Clearly, the system interface has changed and caused many incompatibilities - I'm happy to have a workaround for CouchPotato. The other major drawback at the moment is that the Windows version is not yet complete, so those who use Windows on their desktop don't have a thin client available (but the webUI should be good).
  8. Well, for the time being, I have set CP to use Black hole as the downloader, and configured 'AutoAdd' in Deluge. That seems to be working but I had to enable 'Magnet File' in the CP Black hole downloader section. Obviously, you have to have the same path added in both containers so that they share a folder for writing/reading the torrent/magnet files. I recommend this for anyone who wishes to retain CouchPotato while moving to the updated deluge.
  9. The v1.3 gui/console is not compatible with the v2.03 daemon, so no surprise that doesn't work. The v2.03 console (thin client) works well with the v2.03 daemon - again, shouldn't be a surprise. However, if you run your desktop computer on Windows, you're out of luck because the v2.03 conversion to Windows isn't complete yet. For me, the web gui and/or the thin client work well for me on my Linux Mint desktop. My big problem is the couchpotato/deluge v2.03 incompatibility.
  10. Thanks for your effort on this, but I still get "Connection failed. Check logs for details" when I click on the 'Test Deluge' button in 'Settings -> Downloaders'. I look in the logs and I don't see anything relating to the problem.
  11. Okay - it would be a shame to loose CP. I still cannot accept the fact that sonarr/radarr enforce one movie per directory. Using .mkv containers eliminates the need and fs overhead. Yes, I found the radarr and sonarr issues that you identified. I did try forcing deluge to create a new ssl certificate, but that wasn't the issue.
  12. Upgrade to the deluge v2.03 version appears to have completed without major incident. I did take a prior copy of the deluge appdata folder, but it wasn't needed. Deluge v2 doesn't appear to have hit the mint/ubuntu repositories yet, so I went to the deluge ppa to upgrade my thin client. All working well! Edit: One oddity to report. I have the scheduler enabled, and everything I'd done with upgrade and testing had been during a 'slow speed' period. I noticed that, while uploads had been running, I hadn't seen any download activity - downloads only started running when I set the current schedule period to 'high speed'. After that, I set back to 'low speed' and downloads continued running. Oh, and others have reported, I don't seem to be able to get the CouchPotato connection to Deluge working (from the Binhex CP docker).
  13. If you read the release notes for deluge v2, you will see that v1 plugins will need to be modified/re-written.
  14. Okay, got it now - was being stupid!