Burizado

Members
  • Posts

    109
  • Joined

  • Last visited

Recent Profile Visitors

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

Burizado's Achievements

Apprentice

Apprentice (3/14)

18

Reputation

  1. Don't downloads go to the device you are downloading them on? Like if I was traveling and wanted to download episodes/movies, they would go onto the tablet/phone I am taking with me, not the Plex server. Am I wrong in my thinking here?
  2. Thanks! Yeah, I spun up a test Radarr to see how it works, and saw all the Indexers start appearing in Radarr. So it seems Radarr/Sonarr/Lidarr will use the Indexers defined in their individual apps, but the Indexers are managed by Prowlarr. I like that there is more control over each Indexers individual settings with this setup, and you only have to manage them in 1 app (Prowlarr). Since I have 5 apps to manage the Indexers for it makes it nice to be all in one spot.
  3. Firstly, thanks for all your hard work on all your dockers Binhex. I just installed this Docker and I am trying to understand how it works with Deluge and other the *ARR dockers. If I wanted to use this as my main Indexer, do I need to set anything up in Sonarr/Radarr? Currently I have Jackett setup in each of the applications as the only Indexer. Do I just delete that in Sonarr/Radarr, and have Prowlarr setup as 'Full Sync' for both applications? My Sonarr and Radarr dockers are also connected to my Trakt lists as well as my Plex docker. So when new content is added to Sonarr/Radarr via my Trakt lists does Prowlarr just know to look for the missing content? I guess I'm not understanding how Prowlarr would know to search for the missing content without a connection setup in Sonarr/Radarr, unless it is via the 'Full Sync' connection and it is always looking for changes in those applications (i.e. new content added or missing content found). So then in my Sonarr/Radarr dockers I would just have the download client, Trakt list, and Plex as my defined connections I am thinking.
  4. Same here. I don't use the docker much (setup as a secondary media docker). I started it after updating, and when I open the WebUI I just get a page with 'Forbidden'. I rolled back to 4.6.4.0-3-01 and the WebUI loads fine. I didn't see any errors in the log with version 4.6.6.0-1-01 or latest. Not a huge issue for me since as I mentioned this is a secondary docker I have just to test out other media library front ends. Plex is my main media front end. I just wanted to post that I see a similar issue and heads up if anyone else has a similar issue.
  5. Nope. Working fine for me. I am using one of the CA endpoints FYI.
  6. Do you have a link to the download? I am assuming this is only if you are using the ovpn files and not using Wireguard?
  7. Is anyone else seeing any issues with queued up torrents disappearing? I am noticing this happening every morning when checking my downloads. I did some testing and it seems when Deluge restarts (this occurs everyday due to my nightly backup) it seems to loose all the torrents queued up. Any torrents that have started at least a little download are not removed. Only torrents that have not started downloading anything. I just noticed this happening after updating Deluge. I was using the new version with the proxy updates from a few weeks ago successfully, and only noticed this after updating late last week sometime. For reference in my setup I am using 2 Radarr containers, 1 for normal content, and the other exclusively for 2160p content. I do this to keep both versions of a single movie, but in separate directories and libraries in Plex. I don't think the issue is with these applications as I see this occur for both Radarr instances and for Sonarr as well, and they only disappear when Deluge is restarted not Radarr, Sonarr, or Jackett. Radarr, Sonarr, and Jackett are all setup using Deluge as the privoxy.
  8. The SpaceInvader video did not delete the port variable. I'm not sure if that makes a difference. I know it is contrary to what the instructions specify.
  9. It is not accurate because some, like myself, have privoxy working successfully with the Deluge upgrade. You have to make some changes to the settings namely adding your network range to the 'Ignored Addresses' but it does work. I agree there are some bugs, and I do see the privoxy restarting in the logs as well, but that does not mean it is not working. I am also hoping for a fix for any bugs, and Binhex has posted that they are being worked on (at least the ones that can be replicated). Adding captures of my setup to hopefully help anyone that needs to get privoxy working. Deluge Docker Settings: Radarr Settings: Sonarr Settings: Jackett Settings:
  10. This is not accurate. I have everything still running under the privoxy setup. The change that is needed though is you need to add your network IP range into the 'Ignored Addresses' parameter in Radarr/Sonarr. There is not an option in Jackett for this that I found. For reference I tested the new setup routing Jackett/Radarr/Sonarr through Deluge but Radarr and Sonarr are unable to communicate with containers outside the VPN, mainly Plex in may case. I did not want to run my Plex container through Deluge, but I am assuming it might work if you did that. Also I run 2 containers of Radarr and the new setup did not like having 2 of the same container running through Deluge.
  11. My solution to this is to keep running the privoxy until a solution is developed. You can do this with the new version of Deluge, you just need to add your network IP range to the 'Ignored Addresses' parameter in Radarr/Sonarr.
  12. I see the same in my logs and I am setup to use the privoxy in Deluge, with Radarr/Sonarr/Jackett all setup to use it. I am assuming they are using it but I don't know of a way to test if they are actually using it. I think Jackett is the only container that truely is going outside my network as Radarr and Sonarr I think just connect within my network.
  13. This is the reason I decided not to run my Radarr/Sonarr/Jackett directly through my DelugeVPN container and continue to use the privoxy within the applications. You can still do this you just need to add your network to the 'Ignored Addresses' parameter in the Proxy section of the app. There are details some posts above that I found helpful, but I can post screens if needed. Another reason I am not running them directly through the VPN container is I saw an issue when running 2 versions of Radarr with this setup. I think because the internal port on my 2nd Radarr is still 7878 in the application settings even though the WEBUI container port is 7879. Overall I would like to run the containers without the potential leaks described that pushed this update/fix but as long as I can stay on an updated version and still have everything working I am happy. I say that until a potential leak causes a major issue of course. 😄
  14. I got it to work thanks to Spaceinvader's Video and the VPN FAQ Instructions Q24 at the bottom. Essentially I followed the video, added the 'ADDITIONAL_PORTS' variable, and then just updated the settings inside Radarr for example to be 'localhost' for Download Clients (Deluge) and Indexers (Jackett). One thing I am noticing is that the containers I change will not connect to Plex Media Server any more. This makes sense since all the dockers using the VPN have an IP address outside my network now, when I use 'curl ifconfig.io' in their consoles. For those that have this setup working, do you have an issue with containers not connecting to others not using the VPN? This is my setup for Plex in Radarr, under the Connect settings. I could route my Plex container through the VPN but then I am guessing anything I direct play will go out through the VPN and back to my TV.
  15. Yes! I think I stumbled on it too, then I came here and saw your post. I remember SpaceinvaderOne had a video similar to what was being described and found the video you linked. Putting that together with the steps in Q24 on the VPN FAQ doc helped too. What's not mentioned in the video or FAQ is I had to change my downloader entry in Radarr to 'localhost'.