Dyon Posted June 14, 2023 Author Share Posted June 14, 2023 15 minutes ago, Alex.b said: Hello, I'm triying to set JackettVPN, I'm using wireguard config file from Windscribe. If I set : VPN_ENABLED = Yes VPN_TYPE = wireguard Container starts, but log window closes itself and I can't access to the webui. If I disable the VPN env, everything works. Log : 2023-06-14 21:12:55.737948 [INFO] VPN_ENABLED defined as 'yes' 2023-06-14 21:12:55.754927 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-06-14 21:12:55.770428 [INFO] LEGACY_IPTABLES is set to '' 2023-06-14 21:12:55.786107 [INFO] Not making any changes to iptables version 2023-06-14 21:12:55.801926 [INFO] VPN_TYPE defined as 'wireguard' 2023-06-14 21:12:55.821946 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf dos2unix: converting file /config/wireguard/wg0.conf to Unix format... 2023-06-14 21:12:55.841793 [INFO] VPN remote line defined as 'censured.windscribe.com:1194' 2023-06-14 21:12:55.858427 [INFO] VPN_REMOTE defined as 'censured.windscribe.com' 2023-06-14 21:12:55.875519 [INFO] VPN_PORT defined as '1194' 2023-06-14 21:12:55.890937 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-06-14 21:12:55.906661 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-06-14 21:12:55.923476 [INFO] LAN_NETWORK defined as '192.168.1.0/24' 2023-06-14 21:12:55.940121 [INFO] NAME_SERVERS defined as '9.9.9.9,149.112.112.112' 2023-06-14 21:12:55.957011 [INFO] Adding 9.9.9.9 to resolv.conf 2023-06-14 21:12:55.973795 [INFO] Adding 149.112.112.112 to resolv.conf 2023-06-14 21:12:55.989324 [INFO] Starting WireGuard... Warning: `/config/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add censured/32 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 Error: IPv6 is disabled on nexthop device. [#] resolvconf -d wg0 -f [#] ip link delete dev wg0 That's odd. The windows continuously closing because it is probably unable to connect to the HEALTH_CHECK_HOST. I've pushed an update to the container which adds RESTART_CONTAINER. Update the container and add the new variable. This will prevent the container from restarting To add this variable, edit the container and add this variable: Add another Path, Port, Variable, Label or Device > Config Type: Variable > Name: RESTART_CONTAINER > Key: RESTART_CONTAINER > Value: 0 > Default Value: 0 > Description: (empty) > Display: Always > Required: No > Password Mask: no After changing this, start the container, open the console and please check if you can run the command `ping one.one.one.one`. Quote Link to comment
Alex.b Posted June 14, 2023 Share Posted June 14, 2023 Hello, thank you for your answer ! I added the variable and updated the container. Unfortunately, this message is blinking (it seems restart despite the variable) : Error response from daemon: Container 3925e4163c8ff69855243123aec1064 is restarting, wait until the container is running Quote Link to comment
Dyon Posted June 14, 2023 Author Share Posted June 14, 2023 (edited) 16 minutes ago, Alex.b said: Hello, thank you for your answer ! I added the variable and updated the container. Unfortunately, this message is blinking (it seems restart despite the variable) : Error response from daemon: Container 3925e4163c8ff69855243123aec1064 is restarting, wait until the container is running Try removing the container, maybe that works And than add it again Edited June 14, 2023 by Dyon Quote Link to comment
Alex.b Posted June 14, 2023 Share Posted June 14, 2023 17 minutes ago, Dyon said: Try removing the container, maybe that works And than add it again Same behaviour (I also deleted jackvpn appdata folder, and put again the wg0.conf file) docker run -d --name='jackettvpn' --net='bridge' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Sparta" -e HOST_CONTAINERNAME="jackettvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_TYPE'='wireguard' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'WEBUI_PASSWORD'='' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'PUID'='99' -e 'PGID'='100' -e 'RESTART_CONTAINER '='0' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'UMASK'='002' -e 'HEALTH_CHECK_HOST'='one.one.one.one' -e 'HEALTH_CHECK_INTERVAL'='300' -e 'HEALTH_CHECK_SILENT'='1' -e 'ADDITIONAL_PORTS'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9117]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/DyonR/docker-templates/master/Icons/jackettvpn/jackettvpn-icon.png' -p '9117:9117/tcp' -v '':'/blackhole':'rw' -v '/mnt/user/appdata/jackettvpn':'/config':'rw' --restart unless-stopped 'dyonr/jackettvpn' f6602c7f3fe865dd4b973f371b78df57ebec5463b... Quote Link to comment
Dyon Posted June 14, 2023 Author Share Posted June 14, 2023 18 minutes ago, Alex.b said: Same behaviour (I also deleted jackvpn appdata folder, and put again the wg0.conf file) docker run -d --name='jackettvpn' --net='bridge' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Sparta" -e HOST_CONTAINERNAME="jackettvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_TYPE'='wireguard' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'WEBUI_PASSWORD'='' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'PUID'='99' -e 'PGID'='100' -e 'RESTART_CONTAINER '='0' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'UMASK'='002' -e 'HEALTH_CHECK_HOST'='one.one.one.one' -e 'HEALTH_CHECK_INTERVAL'='300' -e 'HEALTH_CHECK_SILENT'='1' -e 'ADDITIONAL_PORTS'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9117]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/DyonR/docker-templates/master/Icons/jackettvpn/jackettvpn-icon.png' -p '9117:9117/tcp' -v '':'/blackhole':'rw' -v '/mnt/user/appdata/jackettvpn':'/config':'rw' --restart unless-stopped 'dyonr/jackettvpn' f6602c7f3fe865dd4b973f371b78df57ebec5463b... Don't see anything wrong with the docker run command. Perhaps it is the Wireguard file itself. Please download a wireguard client for your PC and see if connecting works properly that way. https://www.wireguard.com/install/ Quote Link to comment
Alex.b Posted June 14, 2023 Share Posted June 14, 2023 (edited) Yes, it works without a hitch. Edited June 14, 2023 by Alex.b Quote Link to comment
ArxKnight Posted June 28, 2023 Share Posted June 28, 2023 (edited) Hi, I have re-installed this app due to an issue not allowing me to update it and now it doesn't seem to connect to the VPN correctly, can anyone help with this as I am unsure what is causing the error. The username and password are correct. LOGS: Spoiler dos2unix: converting file /config/openvpn/uk2202.nordvpn.com.tcp443.ovpn to Unix format... 2023-06-28 21:49:38.464915 [INFO] VPN_ENABLED defined as 'yes' 2023-06-28 21:49:38.480412 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-06-28 21:49:38.493399 [INFO] LEGACY_IPTABLES is set to '' 2023-06-28 21:49:38.507408 [INFO] Not making any changes to iptables version 2023-06-28 21:49:38.520807 [INFO] VPN_TYPE defined as 'openvpn' 2023-06-28 21:49:38.538548 [INFO] OpenVPN config file is found at /config/openvpn/uk2202.nordvpn.com.tcp443.ovpn 2023-06-28 21:49:38.559158 [INFO] VPN remote line defined as '178.159.3.180 443' 2023-06-28 21:49:38.575673 [INFO] VPN_REMOTE defined as '178.159.3.180' 2023-06-28 21:49:38.590134 [INFO] VPN_PORT defined as '443' 2023-06-28 21:49:38.605878 [INFO] VPN_PROTOCOL defined as 'tcp' 2023-06-28 21:49:38.621709 [INFO] VPN_DEVICE_TYPE defined as 'tun0' 2023-06-28 21:49:38.637091 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-06-28 21:49:38.651622 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-06-28 21:49:38.665716 [INFO] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2023-06-28 21:49:38.680253 [INFO] Adding 1.1.1.1 to resolv.conf 2023-06-28 21:49:38.694331 [INFO] Adding 1.0.0.1 to resolv.conf 2023-06-28 21:49:38.707960 [INFO] Starting OpenVPN... 2023-06-28 21:49:38 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2023-06-28 21:49:38 WARNING: file 'credentials.conf' is group or others accessible 2023-06-28 21:49:38 OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021 2023-06-28 21:49:38 library versions: OpenSSL 1.1.1n 15 Mar 2022, LZO 2.10 2023-06-28 21:49:38 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2023-06-28 21:49:38 NOTE: --fast-io is disabled since we are not using UDP 2023-06-28 21:49:38 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-28 21:49:38 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-28 21:49:38 TCP/UDP: Preserving recently used remote address: [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 Socket Buffers: R=[87380->87380] S=[65536->65536] 2023-06-28 21:49:38 Attempting to establish TCP connection with [AF_INET]178.159.3.180:443 [nonblock] 2023-06-28 21:49:38 TCP connection established with [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 TCP_CLIENT link local: (not bound) 2023-06-28 21:49:38 TCP_CLIENT link remote: [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 TLS: Initial packet from [AF_INET]178.159.3.180:443, sid=8dd9f8c9 ec50125c 2023-06-28 21:49:38 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA 2023-06-28 21:49:38 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8 2023-06-28 21:49:38 VERIFY KU OK 2023-06-28 21:49:38 Validating certificate extended key usage 2023-06-28 21:49:38 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2023-06-28 21:49:38 VERIFY EKU OK 2023-06-28 21:49:38 VERIFY OK: depth=0, CN=uk2202.nordvpn.com 2023-06-28 21:49:38 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA 2023-06-28 21:49:38 [uk2202.nordvpn.com] Peer Connection Initiated with [AF_INET]178.159.3.180:443 2023-06-28 21:49:40 SENT CONTROL [uk2202.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-28 21:49:45 SENT CONTROL [uk2202.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-28 21:49:45 AUTH: Received control message: AUTH_FAILED 2023-06-28 21:49:45 SIGTERM[soft,auth-failure] received, process exiting Edited June 28, 2023 by ArxKnight Quote Link to comment
Dyon Posted June 28, 2023 Author Share Posted June 28, 2023 46 minutes ago, ArxKnight said: Hi, I have re-installed this app due to an issue not allowing me to update it and now it doesn't seem to connect to the VPN correctly, can anyone help with this as I am unsure what is causing the error. The username and password are correct. LOGS: Hide contents dos2unix: converting file /config/openvpn/uk2202.nordvpn.com.tcp443.ovpn to Unix format... 2023-06-28 21:49:38.464915 [INFO] VPN_ENABLED defined as 'yes' 2023-06-28 21:49:38.480412 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-06-28 21:49:38.493399 [INFO] LEGACY_IPTABLES is set to '' 2023-06-28 21:49:38.507408 [INFO] Not making any changes to iptables version 2023-06-28 21:49:38.520807 [INFO] VPN_TYPE defined as 'openvpn' 2023-06-28 21:49:38.538548 [INFO] OpenVPN config file is found at /config/openvpn/uk2202.nordvpn.com.tcp443.ovpn 2023-06-28 21:49:38.559158 [INFO] VPN remote line defined as '178.159.3.180 443' 2023-06-28 21:49:38.575673 [INFO] VPN_REMOTE defined as '178.159.3.180' 2023-06-28 21:49:38.590134 [INFO] VPN_PORT defined as '443' 2023-06-28 21:49:38.605878 [INFO] VPN_PROTOCOL defined as 'tcp' 2023-06-28 21:49:38.621709 [INFO] VPN_DEVICE_TYPE defined as 'tun0' 2023-06-28 21:49:38.637091 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-06-28 21:49:38.651622 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-06-28 21:49:38.665716 [INFO] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2023-06-28 21:49:38.680253 [INFO] Adding 1.1.1.1 to resolv.conf 2023-06-28 21:49:38.694331 [INFO] Adding 1.0.0.1 to resolv.conf 2023-06-28 21:49:38.707960 [INFO] Starting OpenVPN... 2023-06-28 21:49:38 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2023-06-28 21:49:38 WARNING: file 'credentials.conf' is group or others accessible 2023-06-28 21:49:38 OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021 2023-06-28 21:49:38 library versions: OpenSSL 1.1.1n 15 Mar 2022, LZO 2.10 2023-06-28 21:49:38 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2023-06-28 21:49:38 NOTE: --fast-io is disabled since we are not using UDP 2023-06-28 21:49:38 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-28 21:49:38 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2023-06-28 21:49:38 TCP/UDP: Preserving recently used remote address: [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 Socket Buffers: R=[87380->87380] S=[65536->65536] 2023-06-28 21:49:38 Attempting to establish TCP connection with [AF_INET]178.159.3.180:443 [nonblock] 2023-06-28 21:49:38 TCP connection established with [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 TCP_CLIENT link local: (not bound) 2023-06-28 21:49:38 TCP_CLIENT link remote: [AF_INET]178.159.3.180:443 2023-06-28 21:49:38 TLS: Initial packet from [AF_INET]178.159.3.180:443, sid=8dd9f8c9 ec50125c 2023-06-28 21:49:38 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA 2023-06-28 21:49:38 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8 2023-06-28 21:49:38 VERIFY KU OK 2023-06-28 21:49:38 Validating certificate extended key usage 2023-06-28 21:49:38 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2023-06-28 21:49:38 VERIFY EKU OK 2023-06-28 21:49:38 VERIFY OK: depth=0, CN=uk2202.nordvpn.com 2023-06-28 21:49:38 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA 2023-06-28 21:49:38 [uk2202.nordvpn.com] Peer Connection Initiated with [AF_INET]178.159.3.180:443 2023-06-28 21:49:40 SENT CONTROL [uk2202.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-28 21:49:45 SENT CONTROL [uk2202.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2023-06-28 21:49:45 AUTH: Received control message: AUTH_FAILED 2023-06-28 21:49:45 SIGTERM[soft,auth-failure] received, process exiting I know you mentioned that you are sure that the username and password are right, but this line in the log really means it could not be anything else: 2023-06-28 21:49:45 AUTH: Received control message: AUTH_FAILED Please check again your NordVPN dashbord under the option Setup NordVPN manually; https://my.nordaccount.com/dashboard/nordvpn/ This guide is for Android, but the process of obtaining the NordPVN credentials are the same. 1 Quote Link to comment
ArxKnight Posted June 28, 2023 Share Posted June 28, 2023 5 minutes ago, Dyon said: I know you mentioned that you are sure that the username and password are right, but this line in the log really means it could not be anything else: 2023-06-28 21:49:45 AUTH: Received control message: AUTH_FAILED Please check again your NordVPN dashbord under the option Setup NordVPN manually; https://my.nordaccount.com/dashboard/nordvpn/ This guide is for Android, but the process of obtaining the NordPVN credentials are the same. Yes thank you, I was trying my normal login rather than using the manual setup username and password. Thanks Quote Link to comment
azzkickr Posted July 19, 2023 Share Posted July 19, 2023 I'm also unable to get it to work. After enabling wireguard, the log file is not updated anything, the log and console windows disappear immediately. I have tried the wg0.conf file on another machine, works flawlessly. I can't even tell you anything more as there is nothing in the logs... Quote Link to comment
azzkickr Posted July 20, 2023 Share Posted July 20, 2023 6 hours ago, jhonsteve1122 said: Issues with accessing your server File Browser and an uncooperative Wireguard are your current challenges. Your wg0.conf file is functional on a different system, but the lack of logs on your device makes the problem-solving process intricate My file browser is fine, maybe I was not clear enough. So let me rephrase. 1. After installation I have run the docker with wg off, it started normally, log file was created and filled with usual stuff. 2. I have copied the wg0.conf file to wireguard directory. Enabled wireguard in docker config. 3. The docker starts, shows up as running, but every attempt to click on logs or console here: [picture attached] the pop up windows immediately disappears. When I click on the "Logs" button at the right time, the window shows a ton of quickly scrolling text (like linux boot) and then immediately closes. 4. The log file jackettvpn created in step one is not updated, the file modification time does not change and nothing is being added. Therefore it is difficult for me to diagnose. Is there any way to make the docker not restart (I did follow the Dyon's instruction from a few posts up) or to force it to log everything somewhere, so I can actually find out what's wrong with it? Thanks Quote Link to comment
azzkickr Posted July 20, 2023 Share Posted July 20, 2023 ok, I ran docker update --restart=no jackettvpn and I was able to pull this [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.6.0.14/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 Error: IPv6 is disabled on nexthop device. [#] resolvconf -d wg0 -f [#] ip link delete dev wg0 dos2unix: converting file /config/wireguard/wg0.conf to Unix format... Warning: `/config/wireguard/wg0.conf' is world accessible [#] ip link add wg0 type wireguard [#] wg setconf wg0 /dev/fd/63 [#] ip -4 address add 10.6.0.14/24 dev wg0 [#] ip link set mtu 1420 up dev wg0 [#] resolvconf -a wg0 -m 0 -x [#] wg set wg0 fwmark 51820 [#] ip -6 route add ::/0 dev wg0 table 51820 Error: IPv6 is disabled on nexthop device. [#] resolvconf -d wg0 -f [#] ip link delete dev wg0 2023-07-20 15:40:12.946123 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:12.987235 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:13.041482 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:13.079474 [INFO] Not making any changes to iptables version 2023-07-20 15:40:13.122723 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:13.172875 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:13.224638 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:13.262943 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:13.308949 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:13.363519 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:13.397795 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:13.444095 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:13.481143 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:13.522578 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:13.583798 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:13.621964 [INFO] Starting WireGuard... 2023-07-20 15:40:27.456979 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:27.495986 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:27.529427 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:27.570345 [INFO] Not making any changes to iptables version 2023-07-20 15:40:27.604935 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:27.657478 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:27.705489 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:27.748991 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:27.786596 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:27.826672 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:27.859728 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:27.899063 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:27.952981 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:27.996475 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:28.043966 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:28.077873 [INFO] Starting WireGuard... 2023-07-20 15:40:47.124586 [INFO] VPN_ENABLED defined as 'yes' 2023-07-20 15:40:47.162833 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-20 15:40:47.199465 [INFO] LEGACY_IPTABLES is set to '' 2023-07-20 15:40:47.231396 [INFO] Not making any changes to iptables version 2023-07-20 15:40:47.265764 [INFO] VPN_TYPE defined as 'wireguard' 2023-07-20 15:40:47.329410 [INFO] WireGuard config file is found at /config/wireguard/wg0.conf 2023-07-20 15:40:47.376947 [INFO] VPN remote line defined as 'redacted.url:51820' 2023-07-20 15:40:47.417351 [INFO] VPN_REMOTE defined as 'redacted.url' 2023-07-20 15:40:47.454613 [INFO] VPN_PORT defined as '51820' 2023-07-20 15:40:47.490609 [INFO] VPN_PROTOCOL set as 'udp', since WireGuard is always udp. 2023-07-20 15:40:47.524309 [INFO] VPN_DEVICE_TYPE set as 'wg0', since WireGuard will always be wg0. 2023-07-20 15:40:47.562895 [INFO] LAN_NETWORK defined as '192.168.0.0/24' 2023-07-20 15:40:47.600653 [INFO] NAME_SERVERS defined as '1.1.1.1,1.0.0.1' 2023-07-20 15:40:47.640980 [INFO] Adding 1.1.1.1 to resolv.conf 2023-07-20 15:40:47.681245 [INFO] Adding 1.0.0.1 to resolv.conf 2023-07-20 15:40:47.714688 [INFO] Starting WireGuard... My run command is this: docker run -d --name='jackettvpn' --net='br0' --ip='192.168.0.201' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Badger" -e HOST_CONTAINERNAME="jackettvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_TYPE'='wireguard' -e 'VPN_USERNAME'='' -e 'VPN_PASSWORD'='' -e 'WEBUI_PASSWORD'='redacted' -e 'LAN_NETWORK'='192.168.0.0/24' -e 'TCP_PORT_9117'='9117' -e 'PUID'='99' -e 'PGID'='100' -e 'RESTART_CONTAINER'='0' -e 'NAME_SERVERS'='1.1.1.1,1.0.0.1' -e 'UMASK'='002' -e 'HEALTH_CHECK_HOST'='one.one.one.one' -e 'HEALTH_CHECK_INTERVAL'='300' -e 'HEALTH_CHECK_SILENT'='1' -e 'ADDITIONAL_PORTS'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:9117]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/DyonR/docker-templates/master/Icons/jackettvpn/jackettvpn-icon.png' -v '':'/blackhole':'rw' -v '/mnt/user/appdata/jackettvpn':'/config':'rw' --restart unless-stopped 'dyonr/jackettvpn' ec51c7bbd7d2b160ecd390a2f93f080fb0f41285572dfd556d82bcd1d5b43a0c The behaviour. root@Badger:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ec51c7bbd7d2 dyonr/jackettvpn "/bin/bash /etc/open…" 4 minutes ago Restarting (2) 18 seconds ago jackettvpn And I get a timeout trying to log on to 192.168.0.201:9117 This is the contents of /mnt/user/appdata/jackettvpn/Jackett/Logs/log.txt root@Badger:/mnt/user/appdata/jackettvpn/Jackett/Logs# cat log.txt 07-20 00:31:32 Info Starting Jackett v0.21.491 07-20 00:31:33 Info Environment version: 6.0.20 (/opt/Jackett/) 07-20 00:31:33 Info OS version: Unix 6.1.38.0 (64bit OS) (64bit process) 07-20 00:31:33 Info Jackett variant: CoreLinuxAmdx64 07-20 00:31:33 Info File /etc/issue: Debian GNU/Linux 11 \n \l 07-20 00:31:33 Info Running in Docker: Yes (image build: unknown) 07-20 00:31:33 Info ThreadPool MaxThreads: 32767 workerThreads, 1000 completionPortThreads 07-20 00:31:33 Info App config/log directory: /config/Jackett 07-20 00:31:33 Info Using proxy: Disabled 07-20 00:31:33 Info Using FlareSolverr: No 07-20 00:31:33 Info Using HTTP Client: HttpWebClient2 07-20 00:31:33 Info Loading Native indexers ... 07-20 00:31:33 Info Loaded 75 Native indexers. 07-20 00:31:33 Info Loading Cardigann indexers from: /config/cardigann/definitions/, /etc/xdg/cardigan/definitions/, /opt/Jackett/Definitions 07-20 00:31:35 Info Loaded 520 Cardigann indexers. 07-20 00:31:35 Info Loaded 595 indexers in total 07-20 00:31:35 Info Adding aggregate indexer ('all' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:public' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:private' indexer) ... 07-20 00:31:35 Info Adding filter indexer ('type:semi-public' indexer) ... 07-20 00:31:35 Warn No XML encryptor configured. Key {ea18d026-1121-4fd4-a659-cb2665990748} may be persisted to storage in unencrypted form. 07-20 00:31:35 Info Jackett startup finished in 4.308 s Hosting environment: Production Content root path: /opt/Jackett/Content Now listening on: http://[::]:9117 Application started. Press Ctrl+C to shut down. Quote Link to comment
Dyon Posted July 20, 2023 Author Share Posted July 20, 2023 Can confirm issues with WireGuard for unknown reason. However, I am sad to inform that due personal circumstances and shifts in interests I will not be updating the container in a timely manner. Even though I prefer WireGuard over OpenVPN, for now I sadly would need to recommend using OpenVPN, that one works fine. Quote Link to comment
azzkickr Posted July 22, 2023 Share Posted July 22, 2023 On 7/20/2023 at 6:28 PM, Dyon said: Can confirm issues with WireGuard for unknown reason. However, I am sad to inform that due personal circumstances and shifts in interests I will not be updating the container in a timely manner. Even though I prefer WireGuard over OpenVPN, for now I sadly would need to recommend using OpenVPN, that one works fine. Thanks mate, luckily I run both ovpn and wg on that host, so I'll use ovpn. Cheers! Quote Link to comment
azzkickr Posted July 22, 2023 Share Posted July 22, 2023 On 7/20/2023 at 6:28 PM, Dyon said: Can confirm issues with WireGuard for unknown reason. However, I am sad to inform that due personal circumstances and shifts in interests I will not be updating the container in a timely manner. Even though I prefer WireGuard over OpenVPN, for now I sadly would need to recommend using OpenVPN, that one works fine. Nope, it's not that. When I use openvpn I get pretty much the same result. No matter if I set the network to br0 with manual IP or bridge I get this: 2023-07-22 01:59:12.952067 [INFO] VPN_ENABLED defined as 'yes' 2023-07-22 01:59:12.993899 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-22 01:59:13.027176 [INFO] LEGACY_IPTABLES is set to '' 2023-07-22 01:59:13.059809 [INFO] Not making any changes to iptables version 2023-07-22 01:59:13.095296 [INFO] VPN_TYPE defined as 'openvpn' 2023-07-22 01:59:13.145227 [INFO] OpenVPN config file is found at /config/openvpn/vpn.ovpn 2023-07-22 01:59:13.787129 [INFO] VPN_ENABLED defined as 'yes' 2023-07-22 01:59:13.827101 [INFO] The container is currently running iptables v1.8.7 (nf_tables). 2023-07-22 01:59:13.861508 [INFO] LEGACY_IPTABLES is set to '' 2023-07-22 01:59:13.897722 [INFO] Not making any changes to iptables version 2023-07-22 01:59:13.932693 [INFO] VPN_TYPE defined as 'openvpn' 2023-07-22 01:59:13.979816 [INFO] OpenVPN config file is found at /config/openvpn/vpn.ovpn Nothing in the jackett log Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.