radiation.syrup

Members
  • Posts

    4
  • Joined

  • Last visited

radiation.syrup's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Ah ha, of course! Yes, I switched back to Deluge 1.3.15 for compatibility reasons. I'll give the new version ago. Thanks!
  2. The repository is binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04
  3. Thanks for getting back to me so soon! Unfortunately, that doesn't seem to be the issue. I have the key (not name) set to 'VPN_CLIENT' and the value set to 'wireguard', but the container still fails with the same error. 2020-10-21 06:47:01.678693 [info] System information Linux xxxx 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2020-10-21 06:47:01.696537 [info] PUID defined as '99' 2020-10-21 06:47:01.715871 [info] PGID defined as '100' 2020-10-21 06:47:02.009384 [info] UMASK defined as '000' 2020-10-21 06:47:02.026586 [info] Permissions already set for volume mappings 2020-10-21 06:47:02.046493 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-10-21 06:47:02.009384 [info] UMASK defined as '000' 2020-10-21 06:47:02.026586 [info] Permissions already set for volume mappings 2020-10-21 06:47:02.046493 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2020-10-21 06:47:02.064229 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2020-10-21 06:47:02.082173 [info] VPN_ENABLED defined as 'yes' 2020-10-21 06:47:02.104528 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting...
  4. Hi Binhex, I'm having a bit of difficulty using wireguard (with mullvad). I've managed to get the container working with openvpn by following this post: But I've had no success when I switch from openvpn to wireguard. So far I've tried the following: Enable privileged, change 'VPN_CLIENT' to 'wireguard', and append extra parameter --sysctl="net.ipv4.conf.all.src_valid_mark=1" Generate and copy my wireguard configuration file to /wireguard/, which I rename to 'wg0.conf' (although I doubt that matters). I implemented some of the suggestions you made in earlier posts, so my conf file looks something like [Interface] PrivateKey = <private key> Address = x.x.x.x/32,xxxx:xxxx:xxxx:xxxx::x:xxxx/128 [Peer] PublicKey = <public key> AllowedIPs = 0.0.0.0/0 Endpoint = y.y.y.y:zzzzz Since I'm using wireguard, I shouldn't need the openvpn files. However, if I remove the files in /openvpn/, the container almost immediately fails: 2020-10-20 21:49:51.578271 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting... If I include the openvpn config files, the container starts successfully. However, I can easily verify (by using https://ipleak.net/ and setting the wireguard/openvpn configs to different regions) that the container is just using openvpn, not wireguard. Is there something else I can do to force the container to use wireguard instead?