21 minutes ago, Matrix said:

All ports are unchanged, privoxy set to no and not used anyway, vpn is custom on openvpn, strict port forward set to no and vpn input/output ports left blank. Nameservers are default to container install. Container is not use by any other for connection, only radarr and sonarr to download torrents with it.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

@Matrix another question whilst you get the log, the obfuscated IP address for the 'Server' in your screenshot, if you do a IP lookup of that IP address does it match the VPN Endpoint you are connecting to?.

22 minutes ago, binhex said:

@Matrix another question whilst you get the log, the obfuscated IP address for the 'Server' in your screenshot, if you do a IP lookup of that IP address does it match the VPN Endpoint you are connecting to?.

I will try to get the logs when I am off work. But for the IP it is the one assigned to my VPN. It is actually a static Torguard.net VPN IP with 44203 port forwarded. 

 

I did remotely just run a packet capture for that port on my pfsense box and it is trying to send an receive packets from that port number on my static vpn ip

2 minutes ago, Matrix said:

But for the IP it is the one assigned to my VPN. It is actually a static Torguard.net VPN IP with 44203 port forwarded. 

OK that makes sense to me, so for obvious reasons I have to permit outgoing and incoming traffic to the VPN endpoint in order to establish the VPN tunnel in the first place, and thus iptables permit this.

 

qBittorrent is a very chatty Bittorrent client and it will communicate on all adapters by default, including the LAN adapter, and as the VPN endpoints have to be open qBittorrent may (not always) attempt to connect to the VPN endpoint over the LAN, obviously it would fail as the VPN endpoint is not a Bittorrent client.

 

But i hear you cry, can't you simply tie qBittorrent down to use just the tunnel adapter?, well yes you can and i do exactly this by editing the configuration file before qBittorrent starts, but it appears qBittorrent does not always (looks to be random) pick this setting up straight away, leading to this approx. 1 second delay before switching to talk only on the tunnel adapter (as defined in the config file), so i can only assume this is a bug in qBittorrent - it should be reading the configuration and binding to the adapter BEFORE attempting any communication.
 

In any case, this in my opinion is NOT an IP leak, your VPN provider already knows your ISP assigned IP address by this point and obviously a lot more besides, you are not talking to another Bittorrent client so there has been no peer to peer communication taking place and thus the risk is extremely low (in my opinion it's zero).

1 hour ago, binhex said:

OK that makes sense to me, so for obvious reasons I have to permit outgoing and incoming traffic to the VPN endpoint in order to establish the VPN tunnel in the first place, and thus iptables permit this.

 

qBittorrent is a very chatty Bittorrent client and it will communicate on all adapters by default, including the LAN adapter, and as the VPN endpoints have to be open qBittorrent may (not always) attempt to connect to the VPN endpoint over the LAN, obviously it would fail as the VPN endpoint is not a Bittorrent client.

 

But i hear you cry, can't you simply tie qBittorrent down to use just the tunnel adapter?, well yes you can and i do exactly this by editing the configuration file before qBittorrent starts, but it appears qBittorrent does not always (looks to be random) pick this setting up straight away, leading to this approx. 1 second delay before switching to talk only on the tunnel adapter (as defined in the config file), so i can only assume this is a bug in qBittorrent - it should be reading the configuration and binding to the adapter BEFORE attempting any communication.
 

In any case, this in my opinion is NOT an IP leak, your VPN provider already knows your ISP assigned IP address by this point and obviously a lot more besides, you are not talking to another Bittorrent client so there has been no peer to peer communication taking place and thus the risk is extremely low (in my opinion it's zero).

Thank you for looking into this. I also am not worried about it. Some of my trackers do not permit multiple IPs for seeding and have never complained or gave errors for it.  

 

I did explicitly block for 44203 on my firewall and got a kernel panic within 10 mins. Never had one before, could be a coincidence but the timing tho. I was not at home so I had the wife hard reset.

So I am having an issue with the VPN part. every so often my CPU will get peged on a few cores and all my dockers lock up. i found if I turn off the VPN part of this it works like it should. i am using PIA Wireguard. qbit cmd run.txtsupervisord.logunraid-diagnostics-20240611-2049.zip

On 5/1/2024 at 5:16 AM, binhex said:

 

Looks like a PIA issue with the CRL inline in the ovpn files being malformed, see here:- https://github.com/binhex/arch-qbittorrentvpn/issues/233#issuecomment-2088192316

I have contacted my VPN provider "AirVPN" and they are asking me to do the following.

 

It doesn't seem the same problem, because there's no OpenSSL log entries complaining about a certificate problem.  Can you increase OpenVPN verbosity, just in case? Try "--verb 4" on OpenVPN options (or "verb 4" on the configuration file). Default verbosity level (1) should print anyway the certificate critical error, as it happens with PIA, so we suspect this is a different case.

 

Just not sure how to do this any insight would be great!

8 hours ago, WickedLlama said:

It doesn't seem the same problem, because there's no OpenSSL log entries complaining about a certificate problem.

it most probably isn't, the CRL issue is PIA VPN provider related only.

 

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

5 hours ago, binhex said:

it most probably isn't, the CRL issue is PIA VPN provider related only.

 

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Let me know if you need anything else.

command.txt supervisord.log

2 minutes ago, WickedLlama said:

Let me know if you need anything else.

command.txt 1.34 kB · 0 downloads supervisord.log 52.47 kB · 0 downloads

from your log:-

[UNDEF] Inactivity timeout (--ping-restart), restarting

 

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

5 hours ago, binhex said:

from your log:-

[UNDEF] Inactivity timeout (--ping-restart), restarting

 

Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

 

Thank you for that!!  It was my fault had Ad-guard was blocking my VPN connection.  Thank you for the quick support.  Next time I will be sure to just post as it looks like my problem started around the same time everyone had openvpn problems.

Hi,

 

I just got started with binhex-qbittorrentvpn and set up everything, however, the PIA Wireguard Config file is not being generated.

Any help is appreciated.

 

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="Australia/Sydney"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="MikeUnraid"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'='redacted'
  -e 'VPN_PASS'='redacted'
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='wireguard'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='yes'
  -e 'ENABLE_PRIVOXY'='yes'
  -e 'ENABLE_STARTUP_SCRIPTS'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.0.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8080:8080/tcp'
  -p '8118:8118/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn'

c74ca0b50da3a1edd458fbc80315b5498a1f3eeeb06d226f8394f3f863ade687

The command finished successfully!

2 hours ago, somemike said:

however, the PIA Wireguard Config file is not being generated.

are you sure?, so there is no file /config/wireguard/wg0.conf right?

On 6/14/2024 at 6:21 PM, binhex said:

are you sure?, so there is no file /config/wireguard/wg0.conf right?

Yeah, I'm looking at appdata/binhex-qbittorrentvpn/wireguard

Edited June 20, 20242 yr by somemike

Hey, I'm having issues getting to the webGUI for the binhex-qbittorentvpn docker.  If i set VPN_ENABLED to 'no', it works, but obviously I want the VPN.  My logs are below, I don't see any discernible errors, it seems like it just....  stop.... when trying to set up the VPN.  Appreciate any help.

 

 

 

supervisorord.txt qbittorentvpn docker run.txt

2 hours ago, CrazyHalfling said:

Appreciate any help.

From your logs-

Quote

[info] ProtonVPN username 'USERNAME' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...

I’m guessing that this combined with the strict port forwarding setting is causing the container to fail to start. Try adding the +pmp suffix after your vpn user name.

Edited June 19, 20242 yr by wgstarks
Typo

20 minutes ago, wgstarks said:

From your logs-

I’m guessing that this combined with the strict port forwarding setting is causing the container to fail to start. Try adding the +pmp suffix after your vpn user name.

that was exactly it... I feel dumb for not trying that, but thought it was optional.  Thanks!

On 6/14/2024 at 6:21 PM, binhex said:

are you sure?, so there is no file /config/wireguard/wg0.conf right?

supervisord.log

 

There's also another user with the same issue on git

https://github.com/binhex/arch-qbittorrentvpn/issues/243

Edited June 20, 20242 yr by somemike

1 hour ago, somemike said:

supervisord.log 20.11 kB · 1 download

 

There's also another user with the same issue on git

https://github.com/binhex/arch-qbittorrentvpn/issues/243

From your log-

Quote

[warn] Unable to successfully download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken'
[info] 1 retries left
[info] Retrying in 10 secs...

 

 

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q29.

 

1 hour ago, wgstarks said:

From your log-

 

 

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q29.

 

Yep, but the initial issue here is that /config/wireguard/wg0.conf is not being automatically generated as it should be

5 hours ago, somemike said:

Yep, but the initial issue here is that /config/wireguard/wg0.conf is not being automatically generated as it should be

Looking at your logs i see the failure to get the token from 'https://www.privateinternetaccess.com/gtoken/generateToken', this will then prevent the script from going further to generate the wg0.conf file. 

 

Main causes of this are:-

1. PIA intermittent failure - Yes this is a thing sadly, leaving the container to retry should result in success.
2. Firewall block - Check you are not blocking www.privateinternetaccess.com on your router/firewall
3. DNS issues - Try setting NAME_SERVERS to have a value of 1.1.1.1

Hello BinHex,

 

I been using Unraid for roughly 2-3 years now but starting to get into dockers other than plex.  So i use your QbittorrentVPN, everything it setup but when i try to download ANYTHING from iptorrents it just tells me torrent download failed even in manual adding.  what am i doing wrong? iv done the setup correctly from what the videos iv seen said. im missing something.  I tried downloading a ubuntu iso from google and that worked fine, but i cant download anything from iptorrents.

 

Hello, I'm trying to figure out if I have an issue with the container or with my VPN provider. It runs fine for about 12 hours or so, then connection is lost, logs shows DNS issues:

 

2024-06-25 16:04:57,656 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100    49    0     0  100    49      0    960 --:--:-- --:--:-- --:--:--   980
2024-06-26 03:31:15,879 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...

2024-06-26 03:31:31,005 DEBG 'start-script' stdout output:
[info] Sending 'down' command to WireGuard due to dns failure...

Then it ends up in a loop, trying to get the interface up again but due to DNS issues it shuts down the interface, repeat. Restarting the container dosnt help, so far the only fix I've found is to go to ovpn.com (my vpn provider) and create a new config/keypair to add to the wg0.conf file. Then it works... for another 12 hours or so. This kinda feels like an issue on their end? But I dont have this issue on my phone or other devices using the official wireguard client and config file from them.

 

EDIT: Added a sanitized version of my supervisord.log

 

 

EDIT2: Contacted the VPN provider that confirmed this is probably an issue on their end. This issue can be ignored.

 

 

Edited June 26, 20242 yr by Ollebro

Hello everyone.

I am currently trying to get the Docker binhex-qbittorrentvpn running.

I use https://www.perfect-privacy.com as VPN. The protocol here runs via openVPN

I have left all settings of the container at default except the VPN login data.

VPN_ENABLED -> YES

VPN_PROV -> custom

VPN_CLIENT -> openvpn

Then I inserted my login data.

 

Then downloaded the current ovpn files from my provider and inserted "amsterdam" into the openvpn folder of qbittorrent as a test

when i look at the logs now i get the following error.

 

 

here is the supervisord.log

 

Quote

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2024-06-26 12:11:35.822000 [info] Host is running unRAID
2024-06-26 12:11:35.846839 [info] System information Linux ecf8c3011dae 6.1.49-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 x86_64 GNU/Linux
2024-06-26 12:11:35.872982 [info] PUID defined as '99'
2024-06-26 12:11:35.901736 [info] PGID defined as '100'
2024-06-26 12:11:35.947805 [info] UMASK defined as '000'
2024-06-26 12:11:35.973496 [info] Permissions already set for '/config'
2024-06-26 12:11:36.000871 [info] Deleting files in /tmp (non recursive)...
2024-06-26 12:11:36.036981 [info] VPN_ENABLED defined as 'yes'
2024-06-26 12:11:36.064380 [info] VPN_CLIENT defined as 'openvpn'
2024-06-26 12:11:36.091059 [info] VPN_PROV defined as 'custom'
2024-06-26 12:11:36.123600 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Amsterdam.ovpn
2024-06-26 12:11:36.265796 [info] VPN remote server(s) defined as '95.168.167.236,95.168.167.236,95.168.167.236,95.211.95.233,95.211.95.233,95.211.95.233,95.211.95.244,95.211.95.244,95.211.95.244,37.48.94.1,37.48.94.1,37.48.94.1,'
2024-06-26 12:11:36.289915 [info] VPN remote port(s) defined as '44,443,4433,44,443,4433,44,443,4433,44,443,4433,'
2024-06-26 12:11:36.313980 [info] VPN remote protcol(s) defined as 'udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,udp,'
2024-06-26 12:11:36.340857 [info] VPN_DEVICE_TYPE defined as 'tun0'
2024-06-26 12:11:36.367450 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
2024-06-26 12:11:36.683643 [info] LAN_NETWORK defined as '192.168.178.0/24'
2024-06-26 12:11:36.715589 [info] LAN_NETWORK exported as '192.168.178.0/24'
2024-06-26 12:11:36.741665 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2024-06-26 12:11:36.767871 [info] VPN_USER defined as 'XXXXXXXXX'
2024-06-26 12:11:36.794785 [info] VPN_PASS defined as 'XXXXXXXXX'
2024-06-26 12:11:36.821323 [info] ENABLE_PRIVOXY defined as 'no'
2024-06-26 12:11:36.849486 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports
2024-06-26 12:11:36.875962 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports
2024-06-26 12:11:36.902452 [info] ENABLE_STARTUP_SCRIPTS defined as 'no'
2024-06-26 12:11:36.928716 [info] WEBUI_PORT defined as '8080'
2024-06-26 12:11:36.958433 [info] Starting Supervisor...
2024-06-26 12:11:37,141 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing
2024-06-26 12:11:37,142 INFO Set uid to user 0 succeeded
2024-06-26 12:11:37,144 INFO supervisord started with pid 7
2024-06-26 12:11:38,147 INFO spawned: 'start-script' with pid 556
2024-06-26 12:11:38,148 INFO spawned: 'watchdog-script' with pid 557
2024-06-26 12:11:38,149 INFO reaped unknown pid 8 (exit status 0)
2024-06-26 12:11:38,151 DEBG 'start-script' stdout output:
[info] VPN is enabled, beginning configuration of VPN

2024-06-26 12:11:38,152 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-06-26 12:11:38,152 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-06-26 12:11:38,188 DEBG 'start-script' stdout output:
[info] Adding 84.200.69.80 to /etc/resolv.conf

2024-06-26 12:11:38,190 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.174 to /etc/resolv.conf

2024-06-26 12:11:38,192 DEBG 'start-script' stdout output:
[info] Adding 1.1.1.1 to /etc/resolv.conf

2024-06-26 12:11:38,193 DEBG 'start-script' stdout output:
[info] Adding 37.235.1.177 to /etc/resolv.conf

2024-06-26 12:11:38,195 DEBG 'start-script' stdout output:
[info] Adding 84.200.70.40 to /etc/resolv.conf

2024-06-26 12:11:38,197 DEBG 'start-script' stdout output:
[info] Adding 1.0.0.1 to /etc/resolv.conf

2024-06-26 12:11:38,378 DEBG 'start-script' stdout output:
[info] Adding 192.168.178.0/24 as route via adapter eth0

2024-06-26 12:11:38,380 DEBG 'start-script' stdout output:
[info] ip route defined as follows...
--------------------

2024-06-26 12:11:38,381 DEBG 'start-script' stdout output:
default via 172.17.0.1 dev eth0
172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2
192.168.178.0/24 via 172.17.0.1 dev eth0

2024-06-26 12:11:38,382 DEBG 'start-script' stdout output:
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
local 172.17.0.2 dev eth0 table local proto kernel scope host src 172.17.0.2
broadcast 172.17.255.255 dev eth0 table local proto kernel scope link src 172.17.0.2
fd17::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via fd17::1 dev eth0 metric 1024 pref medium
local ::1 dev lo table local proto kernel metric 0 pref medium
local fd17::242:ac11:2 dev eth0 table local proto kernel metric 0 pref medium
local fe80::42:acff:fe11:2 dev eth0 table local proto kernel metric 0 pref medium
multicast ff00::/8 dev eth0 table local proto kernel metric 256 pref medium

2024-06-26 12:11:38,382 DEBG 'start-script' stdout output:
--------------------

2024-06-26 12:11:38,386 DEBG 'start-script' stdout output:
iptable_mangle         16384  1
ip_tables              28672  3 iptable_filter,iptable_nat,iptable_mangle
x_tables               45056  17 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,nft_compat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark

2024-06-26 12:11:38,386 DEBG 'start-script' stdout output:
[info] iptable_mangle support detected, adding fwmark for tables

2024-06-26 12:11:38,507 DEBG 'start-script' stdout output:
[info] iptables defined as follows...
--------------------

2024-06-26 12:11:38,509 DEBG 'start-script' stdout output:
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.168.167.236/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.233/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 95.211.95.244/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -s 37.48.94.1/32 -i eth0 -j ACCEPT
-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -i eth0 -p udp -m udp --dport 8080 -j ACCEPT
-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i tun0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.168.167.236/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.233/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 95.211.95.244/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -d 37.48.94.1/32 -o eth0 -j ACCEPT
-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT
-A OUTPUT -o eth0 -p udp -m udp --sport 8080 -j ACCEPT
-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -o tun0 -j ACCEPT

2024-06-26 12:11:38,510 DEBG 'start-script' stdout output:
--------------------

2024-06-26 12:11:38,510 DEBG 'start-script' stdout output:
[info] Starting OpenVPN (non daemonised)...

2024-06-26 12:11:38,518 DEBG 'start-script' stdout output:
Options error: Unrecognized option or missing or extra parameter(s) in /config/openvpn/Amsterdam.ovpn:222: register-dns (2.6.10)
Use --help for more information.

Furthermore, I cannot call up webui. I assume that this is related to the error!

What have I overlooked here? What would I have to change or set to get the container to run?

I would be very happy about a help

Best regards

Smoky

 

 

Edited June 26, 20242 yr by Smoky93