Burizado

Members
  • Content Count

    104
  • Joined

  • Last visited

Community Reputation

18 Good

About Burizado

  • Rank
    Member

Recent Profile Visitors

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

  1. 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?
  2. 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 n
  3. 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.
  4. 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 w
  5. 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
  6. 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.
  7. 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.
  8. 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
  9. 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 wor
  10. 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'.
  11. Just curious, how do you go about rolling back to the previous version? I looked through the Github and Dockerhub for the information, but not finding it.
  12. Sorry for the barrage of questions. I also setup my Windows 10 VM to use the DelugeVPN connection by setting it up according to Spaceinvader's video. Is there a way to route the VM through the DelugeVPN with this new update? I was not sure if I needed to add a port to the 'ADDITIONAL_PORTS' var and if so what port. Image from Internet Options > Connections tab > LAN settings inside my Win 10 VM.
  13. I ran the manual force update. I am not seeing the 'ADDITIONAL_PORTS' var in the docker config in unRAID, but I did see it in the logs when I started Deulge. Do we need to add it manually in the unRAID config for the docker, or specify it in the 'Extra Parameters' section?
  14. Is this only for the new updated Deluge setup? I was trying to use 'localhost' before I updated Deluge and I get an error, but when I specify the IP 192.168.0.178 it tests good. I understand what you are saying about it being inefficient, and would like to make it more so. The screens show my setup in Radarr. It doesn't show in the bottom option in the download client setup, but I don't have 'Use SSL' checked.
  15. Thank you for your continued work on this docker! If I am understanding correctly, I will need to add the port for the WebUI of the other dockers that are using my Deluge docker VPN (Privoxy?) into the 'ADDITIONAL_PORTS' variable, correct? So if I am running your Jackett (9117), Radarr (7878), and Sonarr (8989) dockers as different ports on the same IP I would add the ports these are on into the variable separated by a comma (9117,7878,8989).