Jorgen

Members
  • Content Count

    216
  • Joined

  • Last visited

Community Reputation

35 Good

1 Follower

About Jorgen

  • Rank
    Member
  • Birthday 02/04/1976

Converted

  • Gender
    Male
  • Location
    Manly, Australia

Recent Profile Visitors

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

  1. Hmm that doesn’t seem right. PIA themselves have published scripts to use with wireguard outside their app: https://www.privateinternetaccess.com/helpdesk/kb/articles/manual-connection-and-port-forwarding-scripts Sent from my iPhone using Tapatalk
  2. I don’t have a solution for you, but many of us are using wireguard and PIA in binhex’s excellent VPN enabled containers. Maybe you could look into the script he’s using to get the required settings? Or even set up a container and copy the wg config file? Sent from my iPhone using Tapatalk
  3. It’s static. Can’t remember what the default one is, but you can change it to whichever supported endpoint you wish and it should persist from that point. Sent from my iPhone using Tapatalk
  4. That’s how it works when binding the network. Sent from my iPhone using Tapatalk
  5. From a few posts up. But you’re probably better off in the long run to try to get sonarr v3 working with the seed box. Sent from my iPhone using Tapatalk
  6. [mention]strykn [/mention] [mention]nowhere99 [/mention] did you see the pinned post at the top of this thread and followed the instructions? Edit: Sorry! The post is pinned to the delugeVPN thread, see here: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=951973
  7. Yes, using tar from the command line. Here’s an example: https://www.linux.org/threads/list-tar-contents-only-first-level-then-subdirectory-extract.10491/ Sent from my iPhone using Tapatalk
  8. Sounds like your routing Sonarr et al through the DelugeVPN container network? In that case, you should NOT use the proxy settings in Sonarr. It's one or the other, not both. You should also add the SABnzbd ports to VPN_OUTPUT_PORTS environment variable. Because Sonarr running INSIDE the DelugeVPN container network, needs to be allowed to talk OUT to the SAB ports running outside the DelugeVPN network. This is explained in Q27 here https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Of course, if you are not routing the apps through the DelugeVPN network t
  9. Sonarr is supposed to remove the torrent from Deluge after it reaches the defined ratio, but I never got that to work either. AutoRemovePlus plugin is the way to go in my opinion. The most likely reason the egg isn't accepted for you is that the Python version in this container was recently updated to 3.9. If you have the 3.8 egg in the plugin folder already, simple rename it to 3.9 (see below) and restart the container: AutoRemovePlus-2.0.0-py3.9.egg If you don't have it, download the 3.8 version from here: https://forum.deluge-torrent.org/viewtopic.php?f=9
  10. Thanks, hardcoding "/watch" made it work again, of course. Just for my understanding though, am I misinterpreting the table on the hooks page? I'm using post_watch_folder_processing.sh
  11. Hi Djoss, I've been running this container for a looooong time without any problems, using the automatic watch folder workflow and a post_watch_folder_processing script to stop the container after processing if the watch folder is empty. Sometime during the last few months (maybe longer) the script has stopped working as intended, with this in the log: [autovideoconverter] Conversion ended successfully. [autovideoconverter] Removed /watch/moviename.mkv'. [autovideoconverter] Watch folder '/watch' processing terminated. [autovideoconverter] Executing post watch folder processing h
  12. ok, there was a bug in the container updates yesterday in regards to wireguard. Try forcing an update now and see if it fixes it, binhex pushed a fix a few hours ago.
  13. In Jackett proxy config you should use the 172.17.x.x IP of the DelugeVPN container. I think this also assumes that both Jackett and DelugeVPN containers are using the same docker network, which is bridge by default:
  14. No terminal command required, it's shown on the docker page in unraid: One thing to keep in mind if you go down this route (pun intended) is that the docker IP is dynamcially assigned and could change on restart of containers or the unraid server. If things always start in the same order it probably won't, but just be aware of it if things suddenly stops working again.
  15. Ah, interesting. Could you share a screenshot of the Jacket proxy settings? Is that a 172.x.x.x IP?