[Support] binhex - SABnzbdVPN


Recommended Posts

Hello, 

 

Only recently joined as I'm in the process of migrating from Synology to unRaid. I wanted to firstly say many thanks for all of your work on this fantastic programme, it has been running perfectly for several weeks on my Synology once I got it set up after reading this forum. 

 

Today however I have updated my DSM to the latest pushed OS version (6.2.3-25426) and after a restart SabnzbdVPN is throwing up the following error;

Quote

2020-05-28 18:14:29,360 DEBG 'start-script' stdout output:

Thu May 28 18:14:29 2020 ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such device (errno=19)

Thu May 28 18:14:29 2020 Exiting due to fatal error

 

I've tried;

*Replacing the configuration file from NordVPN, 

*Deleting all files and the docker image followed by a complete fresh reinstall, 

*Logged into NordVPN directly to ensure that there are no issues with my account, 

*Checked that NordVPN has no issues, 

*Tried another configuration file for another NordVPN server location,

*Double checked all parameters / variables within the docker image (these have not been touched since initial setup). 

*Read the linked sabnzbdvpn documentation. 

 

Unfortunately however I am still receiving the same error message and nothing seems to work. Any help would be greatly appreciated. 

 

 

***Update***

After endless Googling I find a page with the following details, which worked (I have know idea what I've just done following the below, but I'm hoping it hasn't made me system vulnerable);

 

Check if you have the tun module installed:

❯ lsmod | grep tun

 

If the result comes out empty, try installing it:

❯ insmod /lib/modules/tun.ko

 

Now let’s make sure the tun.ko module works as expected:

❯ mkdir /dev/net

❯ mknod /dev/net/tun c 10 200

❯ chmod 600 /dev/net/tun

❯ cat /dev/net/tun

 

If the result of the cat command was "File descriptor in bad state", it means the module has been correctly installed.

 

The module installation needs to be made persistent otherwise on every Synology restart, you’ll have to repeat the insmod command.

 

Create the following file to run on every system boot:

❯ cat <<EOF > /usr/local/etc/rc.d/tun.sh #!/bin/sh -e

 

insmod /lib/modules/tun.ko EOF

 

Make the script executable:

❯ chmod a+x /usr/local/etc/rc.d/tun.sh

 

Reboot your Synology NAS or execute the script manually once. Done!

 

Edited by Mike12421
Solution found
Link to comment
  • 4 weeks later...

I've been getting this error lately:

 

Server news.newsdemon.com uses an untrusted certificate [Certificate hostname mismatch: the server hostname is not listed in the certificate. This is a server issue.] - Wiki: https://sabnzbd.org/certificate-errors

 

I can't seem to figure this one out.   I'm using NordVPN and have tried different config files. In my OpenVPN folder, there is ...udp.ovpn, .crt, and .key files along with the credentials.conf file.  

 

I checked the server here: and it looks as though the certificates are good.  Hoping someone has some insight on this.

Thanks.

Link to comment
5 hours ago, chizll said:

I can't seem to figure this one out.   I'm using NordVPN and have tried different config files. In my OpenVPN folder, there is ...udp.ovpn, .crt, and .key files along with the credentials.conf file.  

i very much doubt the issue is related to the vpn, it looks like its a root certificate that needs updating in the image, i will push an update out and hopefully this should resolve your issue, look out for a new image in about an hour.

Link to comment
10 minutes ago, binhex said:

i very much doubt the issue is related to the vpn, it looks like its a root certificate that needs updating in the image, i will push an update out and hopefully this should resolve your issue, look out for a new image in about an hour.

Ok, thank you!

Link to comment

Hi, 

 

Unfortunately I've been getting the following error a couple of times a day for the past few weeks;

 

Server News.newsgroup.Ninja uses an untrusted certificate [Certificate hostname mismatch: the server hostname is not listed in the certificate. This is a server issue.] - Wiki: https://sabnzbd.org/certificate-errors

 

I thought it would just go away on its own and I thought it had after you addressed the certificate issue above, however its just happened again. 

 

Any advice would be greatly appreciated. 

Link to comment

Hi eki eki eki patang, I hope you're well.

 

I wonder if you'd be able to assist me with an issue that I am having please. I have installed SABNZBDVPN and have set up the VPN configuration and it appears to be set up ok and the docker starts fine. The issue I am having is the WebUI doesn't load at all for me when activated. When I turn off the VPN within the settings the WebUI loads just fine. I have tried this with 2 separate VPN's and neither work. I also tried my access on my friends server who has the exacts same set up as me and it worked just fine for him.

 

I also downloaded binhex DelugeVPN and I am also having the same issue with that too.

 

I wondered if you may know what might be the cause of this?

Link to comment
19 hours ago, Mike12421 said:

Hi, 

 

Unfortunately I've been getting the following error a couple of times a day for the past few weeks;

 

Server News.newsgroup.Ninja uses an untrusted certificate [Certificate hostname mismatch: the server hostname is not listed in the certificate. This is a server issue.] - Wiki: https://sabnzbd.org/certificate-errors

 

I thought it would just go away on its own and I thought it had after you addressed the certificate issue above, however its just happened again. 

 

Any advice would be greatly appreciated. 

This issue still persists on my end.  I don't think it' has been addressed yet

Link to comment
3 minutes ago, chizll said:

This issue still persists on my end.  I don't think it' has been addressed yet

Hi, 

 

Thanks for the update......I thought it might have been just my setup. 

 

I have three usenet providers so it hasn't had a massive impact on me up to now, but I am thinking about dropping Newsgroup.ninja. 

 

Regards. 

Link to comment
2 hours ago, chizll said:

This issue still persists on my end.  I don't think it' has been addressed yet

i think you will find the issue persists on newsgroup ninja's end, the cert they use does not match their server name, so your connection is no longer secured correctly and is potentially susceptible to a 'man in the middle' attack. this image is fully up to date so should include the latest root and intermediate CA certs.

Link to comment
2 hours ago, binhex said:

i think you will find the issue persists on newsgroup ninja's end, the cert they use does not match their server name, so your connection is no longer secured correctly and is potentially susceptible to a 'man in the middle' attack. this image is fully up to date so should include the latest root and intermediate CA certs.

This issue was happening to me with newsdemon.  I find it interesting that it's two different servers.   Thanks for your help.

Link to comment
2 hours ago, binhex said:

i think you will find the issue persists on newsgroup ninja's end, the cert they use does not match their server name, so your connection is no longer secured correctly and is potentially susceptible to a 'man in the middle' attack. this image is fully up to date so should include the latest root and intermediate CA certs.

I've checked newsdemon's certificate at https://www.appelboor.com/cgi-bin/check_newsserver.py?server=news.newsdemon.com

but it says passed.   I will contact newsdemon and see what they say.

Link to comment
9 hours ago, binhex said:

i think you will find the issue persists on newsgroup ninja's end, the cert they use does not match their server name, so your connection is no longer secured correctly and is potentially susceptible to a 'man in the middle' attack. this image is fully up to date so should include the latest root and intermediate CA certs.

 

Many thanks for replying. 

 

I've just emailed Newsgroup.ninja regarding the issue, hopefully I'll have something to report shortly. 

Link to comment

Hello, 

 

I sent this email to Ninja;

 

Quote

To whom it may concern, 

 

I utilise several usenet providers, however recently Newsgroup.ninja has been giving the following error in my usenet downloader, please advise;

 

"Server News.newsgroup.Ninja uses an untrusted certificate [Certificate hostname mismatch: the server hostname is not listed in the certificate. This is a server issue.]"

 

.....and just received this reply back;

 

Quote

Hello,

After further review, it appears your newsreader may be having issues with the SSL connections used. A few things to try:

- If you're specifying a cipher on your setup page, change the cipher to AES-128/AES-256, if available, or leave the option blank.
- Verify that you are using the latest stable release of your newsreader.
- Some newsreaders may not have been updated to support the latest versions of SSL/TLS and will be incompatible as they are no longer deemed secure by today's standards.

Should the issue persist, please provide the following information for further review:
- What region are you connecting from?
- What ISP are you using?
- What newsreader and version were you using when the issue occurred, and on what operating system?
- If the option to set your "Certificate Verification" can be lowered, does lowering it assist?

If you have any further questions or concerns, feel free to reply and we will be happy to help.

Regards,
Newsgroup Ninja Support

 

Link to comment

Hello, please can someone help me. I am using SABNZBDVPN and although it is connecting fine in my Unraid docker, I am unable to load the WEB UI. It started working for me last weekend but has all of a sudden stopped again. I have rebooted my router and my server but nothing seems to be fixing it. All of my settings are fine in terms of getting it working and it is still downloading fine. I just can't access the WEB UI. Please if anyone knows what the issue might be I'd be very grateful.

Link to comment
On 7/3/2020 at 12:55 PM, GaryBellars said:

Hello, please can someone help me. I am using SABNZBDVPN and although it is connecting fine in my Unraid docker, I am unable to load the WEB UI. It started working for me last weekend but has all of a sudden stopped again. I have rebooted my router and my server but nothing seems to be fixing it. All of my settings are fine in terms of getting it working and it is still downloading fine. I just can't access the WEB UI. Please if anyone knows what the issue might be I'd be very grateful.

Same for this and DelugeVPN.  Working but can't access the WebUI.  Logs aren't showing anything unusual that I can see, just started happening. I've restarted the Docker service as well as the UnRaid server.  Thanks!

Link to comment
On 7/3/2020 at 5:55 PM, GaryBellars said:

Hello, please can someone help me. I am using SABNZBDVPN and although it is connecting fine in my Unraid docker, I am unable to load the WEB UI. It started working for me last weekend but has all of a sudden stopped again. I have rebooted my router and my server but nothing seems to be fixing it. All of my settings are fine in terms of getting it working and it is still downloading fine. I just can't access the WEB UI. Please if anyone knows what the issue might be I'd be very grateful.

your issue will be most probably vpn provider related, please do the following:-

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

Edited by binhex
Link to comment
On 7/5/2020 at 3:43 AM, ChaOConnor said:

Same for this and DelugeVPN.  Working but can't access the WebUI.  Logs aren't showing anything unusual that I can see, just started happening. I've restarted the Docker service as well as the UnRaid server.  Thanks!

your issue will be most probably vpn provider related, please do the following:-

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

Edited by binhex
Link to comment

Hi Binhex. Thank you for this. Here is my log file. I have added the word REMOVED where my log in details were.

 

Created by...

___.   .__       .__                   

\_ |__ |__| ____ |  |__   ____ ___  ___

| __ \|  |/    \|  |  \_/ __ \\  \/  /

| \_\ \  |   |  \   Y  \  ___/ >    <

|___  /__|___|  /___|  /\___  >__/\_ \

     \/        \/     \/     \/      \/

   https://hub.docker.com/u/binhex/

 

2020-07-06 04:56:04.126566 [info] System information Linux e4eb53a2c9fd 5.7.2-Unraid #1 SMP Sun Jun 21 18:16:37 CDT 2020 x86_64 GNU/Linux

2020-07-06 04:56:04.192644 [info] OS_ARCH defined as 'x86-64'

2020-07-06 04:56:04.246015 [info] PUID defined as '99'

2020-07-06 04:56:04.351144 [info] PGID defined as '100'

2020-07-06 04:56:04.459407 [info] UMASK defined as '000'

2020-07-06 04:56:04.500538 [info] Permissions already set for volume mappings

2020-07-06 04:56:04.550519 [info] VPN_ENABLED defined as 'yes'

2020-07-06 04:56:04.615175 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Netherlands.ovpn

2020-07-06 04:56:04.701461 [info] VPN remote line defined as 'remote nl.privateinternetaccess.com 1198'

2020-07-06 04:56:04.745791 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'

2020-07-06 04:56:04.788390 [info] VPN_PORT defined as '1198'

2020-07-06 04:56:04.837589 [info] VPN_PROTOCOL defined as 'udp'

2020-07-06 04:56:04.878887 [info] VPN_DEVICE_TYPE defined as 'tun0'

2020-07-06 04:56:04.922109 [info] VPN_PROV defined as 'pia'

2020-07-06 04:56:04.965798 [info] LAN_NETWORK defined as '192.168.1.0/24'

2020-07-06 04:56:05.009887 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1'

2020-07-06 04:56:05.052964 [info] VPN_USER defined as ‘REMOVED’

2020-07-06 04:56:05.095193 [info] VPN_PASS defined as 'REMOVED'

2020-07-06 04:56:05.140393 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)

2020-07-06 04:56:05.186123 [info] ENABLE_PRIVOXY defined as 'yes'

2020-07-06 04:56:05.227887 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports

2020-07-06 04:56:05.323299 [info] Deleting files in /tmp (non recursive)...

2020-07-06 04:56:05.365813 [info] Starting Supervisor...

2020-07-06 04:56:05,961 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing

2020-07-06 04:56:05,961 INFO Set uid to user 0 succeeded

2020-07-06 04:56:05,966 INFO supervisord started with pid 6

2020-07-06 04:56:06,969 INFO spawned: 'start-script' with pid 164

2020-07-06 04:56:06,972 INFO spawned: 'watchdog-script' with pid 165

2020-07-06 04:56:06,973 INFO reaped unknown pid 7 (exit status 0)

2020-07-06 04:56:06,986 DEBG 'start-script' stdout output:

[info] VPN is enabled, beginning configuration of VPN

[debug] Environment variables defined as follows

ADDITIONAL_PORTS=

APPLICATION=sabnzbd

BASH=/bin/bash

 

2020-07-06 04:56:06,986 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2020-07-06 04:56:06,986 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2020-07-06 04:56:06,987 DEBG 'start-script' stdout output:

BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath

BASH_ALIASES=()

BASH_ARGC=()

BASH_ARGV=()

BASH_CMDS=()

BASH_LINENO=([0]="0")

BASH_SOURCE=([0]="/root/start.sh")

BASH_VERSINFO=([0]="5" [1]="0" [2]="16" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu")

BASH_VERSION='5.0.16(1)-release'

DEBUG=true

DIRSTACK=()

ENABLE_PRIVOXY=yes

EUID=0

GROUPS=()

HOME=/home/nobody

HOSTNAME=e4eb53a2c9fd

HOSTTYPE=x86_64

HOST_OS=Unraid

IFS=$' \t\n'

LANG=en_GB.UTF-8

LAN_NETWORK=192.168.1.0/24

MACHTYPE=x86_64-pc-linux-gnu

NAME_SERVERS=209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1

OPTERR=1

OPTIND=1

OSTYPE=linux-gnu

OS_ARCH=x86-64

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

PGID=100

PIPESTATUS=([0]="0")

PPID=6

PS4='+ '

PUID=99

PWD=/

SHELL=/bin/bash

SHELLOPTS=braceexpand:hashall:interactive-comments

SHLVL=1

STRICT_PORT_FORWARD=yes

SUPERVISOR_ENABLED=1

SUPERVISOR_GROUP_NAME=start-script

SUPERVISOR_PROCESS_NAME=start-script

TERM=xterm

TZ=America/Los_Angeles

UID=0

UMASK=000

VPN_CONFIG=/config/openvpn/Netherlands.ovpn

VPN_DEVICE_TYPE=tun0

VPN_ENABLED=yes

VPN_OPTIONS=

VPN_PASS=Nf2pz6pGV7

VPN_PORT=1198

VPN_PROTOCOL=udp

VPN_PROV=pia

VPN_REMOTE=nl.privateinternetaccess.com

VPN_USER=REMOVED

_='[debug] Environment variables defined as follows'

[debug] Directory listing of files in /config/openvpn as follows

 

2020-07-06 04:56:06,998 DEBG 'start-script' stdout output:

total 16

drwxrwxr-x 1 nobody users  126 Jul  6 04:56 .

drwxrwxr-x 1 nobody users  198 Jul  6 04:56 ..

-rwxrwxr-x 1 nobody users 2025 Oct 22  2019 ca.rsa.2048.crt

-rwxrwxr-x 1 nobody users   20 Jul  5 08:53 credentials.conf

-rwxrwxr-x 1 nobody users  869 Oct 22  2019 crl.rsa.2048.pem

-rwxrwxr-x 1 nobody users 3165 Jul  6 04:56 Netherlands.ovpn

 

2020-07-06 04:56:07,078 DEBG 'start-script' stdout output:

[debug] Contents of ovpn file /config/openvpn/Netherlands.ovpn as follows...

 

2020-07-06 04:56:07,079 DEBG 'start-script' stdout output:

remote nl.privateinternetaccess.com 1198

client

dev tun

proto udp

resolv-retry infinite

nobind

persist-key

cipher aes-128-cbc

auth sha1

tls-client

remote-cert-tls server

 

auth-user-pass credentials.conf

compress

verb 1

<crl-verify>

-----BEGIN X509 CRL-----

MIICWDCCAUAwDQYJKoZIhvcNAQENBQAwgegxCzAJBgNVBAYTAlVTMQswCQYDVQQI

EwJDQTETMBEGA1UEBxMKTG9zQW5nZWxlczEgMB4GA1UEChMXUHJpdmF0ZSBJbnRl

cm5ldCBBY2Nlc3MxIDAeBgNVBAsTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAw

HgYDVQQDExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UEKRMXUHJpdmF0

ZSBJbnRlcm5ldCBBY2Nlc3MxLzAtBgkqhkiG9w0BCQEWIHNlY3VyZUBwcml2YXRl

aW50ZXJuZXRhY2Nlc3MuY29tFw0xNjA3MDgxOTAwNDZaFw0zNjA3MDMxOTAwNDZa

MCYwEQIBARcMMTYwNzA4MTkwMDQ2MBECAQYXDDE2MDcwODE5MDA0NjANBgkqhkiG

9w0BAQ0FAAOCAQEAQZo9X97ci8EcPYu/uK2HB152OZbeZCINmYyluLDOdcSvg6B5

jI+ffKN3laDvczsG6CxmY3jNyc79XVpEYUnq4rT3FfveW1+Ralf+Vf38HdpwB8EW

B4hZlQ205+21CALLvZvR8HcPxC9KEnev1mU46wkTiov0EKc+EdRxkj5yMgv0V2Re

ze7AP+NQ9ykvDScH4eYCsmufNpIjBLhpLE2cuZZXBLcPhuRzVoU3l7A9lvzG9mjA

5YijHJGHNjlWFqyrn1CfYS6koa4TGEPngBoAziWRbDGdhEgJABHrpoaFYaL61zqy

MR6jC0K2ps9qyZAN74LEBedEfK7tBOzWMwr58A==

-----END X509 CRL-----

</crl-verify>

 

<ca>

-----BEGIN CERTIFICATE-----

MIIFqzCCBJOgAwIBAgIJAKZ7D5Yv87qDMA0GCSqGSIb3DQEBDQUAMIHoMQswCQYD

VQQGEwJVUzELMAkGA1UECBMCQ0ExEzARBgNVBAcTCkxvc0FuZ2VsZXMxIDAeBgNV

BAoTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMSAwHgYDVQQLExdQcml2YXRlIElu

dGVybmV0IEFjY2VzczEgMB4GA1UEAxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3Mx

IDAeBgNVBCkTF1ByaXZhdGUgSW50ZXJuZXQgQWNjZXNzMS8wLQYJKoZIhvcNAQkB

FiBzZWN1cmVAcHJpdmF0ZWludGVybmV0YWNjZXNzLmNvbTAeFw0xNDA0MTcxNzM1

MThaFw0zNDA0MTIxNzM1MThaMIHoMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex

EzARBgNVBAcTCkxvc0FuZ2VsZXMxIDAeBgNVBAoTF1ByaXZhdGUgSW50ZXJuZXQg

QWNjZXNzMSAwHgYDVQQLExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4GA1UE

AxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3MxIDAeBgNVBCkTF1ByaXZhdGUgSW50

ZXJuZXQgQWNjZXNzMS8wLQYJKoZIhvcNAQkBFiBzZWN1cmVAcHJpdmF0ZWludGVy

bmV0YWNjZXNzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAPXD

L1L9tX6DGf36liA7UBTy5I869z0UVo3lImfOs/GSiFKPtInlesP65577nd7UNzzX

lH/P/CnFPdBWlLp5ze3HRBCc/Avgr5CdMRkEsySL5GHBZsx6w2cayQ2EcRhVTwWp

cdldeNO+pPr9rIgPrtXqT4SWViTQRBeGM8CDxAyTopTsobjSiYZCF9Ta1gunl0G/

8Vfp+SXfYCC+ZzWvP+L1pFhPRqzQQ8k+wMZIovObK1s+nlwPaLyayzw9a8sUnvWB

/5rGPdIYnQWPgoNlLN9HpSmsAcw2z8DXI9pIxbr74cb3/HSfuYGOLkRqrOk6h4RC

OfuWoTrZup1uEOn+fw8CAwEAAaOCAVQwggFQMB0GA1UdDgQWBBQv63nQ/pJAt5tL

y8VJcbHe22ZOsjCCAR8GA1UdIwSCARYwggESgBQv63nQ/pJAt5tLy8VJcbHe22ZO

sqGB7qSB6zCB6DELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRMwEQYDVQQHEwpM

b3NBbmdlbGVzMSAwHgYDVQQKExdQcml2YXRlIEludGVybmV0IEFjY2VzczEgMB4G

A1UECxMXUHJpdmF0ZSBJbnRlcm5ldCBBY2Nlc3MxIDAeBgNVBAMTF1ByaXZhdGUg

SW50ZXJuZXQgQWNjZXNzMSAwHgYDVQQpExdQcml2YXRlIEludGVybmV0IEFjY2Vz

czEvMC0GCSqGSIb3DQEJARYgc2VjdXJlQHByaXZhdGVpbnRlcm5ldGFjY2Vzcy5j

b22CCQCmew+WL/O6gzAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBDQUAA4IBAQAn

a5PgrtxfwTumD4+3/SYvwoD66cB8IcK//h1mCzAduU8KgUXocLx7QgJWo9lnZ8xU

ryXvWab2usg4fqk7FPi00bED4f4qVQFVfGfPZIH9QQ7/48bPM9RyfzImZWUCenK3

7pdw4Bvgoys2rHLHbGen7f28knT2j/cbMxd78tQc20TIObGjo8+ISTRclSTRBtyC

GohseKYpTS9himFERpUgNtefvYHbn70mIOzfOJFTVqfrptf9jXa9N8Mpy3ayfodz

1wiqdteqFXkTYoSDctgKMiZ6GdocK9nMroQipIQtpnwd4yBDWIyC6Bvlkrq5TQUt

YDQ8z9v+DMO6iwyIDRiU

-----END CERTIFICATE-----

</ca>

 

disable-occ

 

2020-07-06 04:56:07,109 DEBG 'start-script' stdout output:

[info] Default route for container is 172.17.0.1

 

2020-07-06 04:56:07,114 DEBG 'start-script' stdout output:

[info] Adding 209.222.18.222 to /etc/resolv.conf

 

2020-07-06 04:56:07,119 DEBG 'start-script' stdout output:

[info] Adding 84.200.69.80 to /etc/resolv.conf

 

2020-07-06 04:56:07,124 DEBG 'start-script' stdout output:

[info] Adding 37.235.1.174 to /etc/resolv.conf

 

2020-07-06 04:56:07,128 DEBG 'start-script' stdout output:

[info] Adding 1.1.1.1 to /etc/resolv.conf

 

2020-07-06 04:56:07,133 DEBG 'start-script' stdout output:

[info] Adding 209.222.18.218 to /etc/resolv.conf

 

2020-07-06 04:56:07,138 DEBG 'start-script' stdout output:

[info] Adding 37.235.1.177 to /etc/resolv.conf

 

2020-07-06 04:56:07,143 DEBG 'start-script' stdout output:

[info] Adding 84.200.70.40 to /etc/resolv.conf

 

2020-07-06 04:56:07,149 DEBG 'start-script' stdout output:

[info] Adding 1.0.0.1 to /etc/resolv.conf

 

2020-07-06 04:56:07,227 DEBG 'start-script' stdout output:

[info] Attempting to load iptable_mangle module...

 

2020-07-06 04:56:07,229 DEBG 'start-script' stderr output:

modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/5.7.2-Unraid

 

2020-07-06 04:56:07,229 DEBG 'start-script' stdout output:

[warn] Unable to load iptable_mangle module using modprobe, trying insmod...

 

2020-07-06 04:56:07,231 DEBG 'start-script' stderr output:

insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory

 

2020-07-06 04:56:07,231 DEBG 'start-script' stdout output:

[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN

[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'

[info] Synology users: Please attempt to load the module by executing the following on your host: 'insmod /lib/modules/iptable_mangle.ko'

[debug] Show name servers defined for container

 

2020-07-06 04:56:07,232 DEBG 'start-script' stdout output:

nameserver 209.222.18.222

nameserver 84.200.69.80

nameserver 37.235.1.174

nameserver 1.1.1.1

nameserver 209.222.18.218

nameserver 37.235.1.177

nameserver 84.200.70.40

nameserver 1.0.0.1

 

2020-07-06 04:56:07,232 DEBG 'start-script' stdout output:

[debug] Show name resolution for VPN endpoint nl.privateinternetaccess.com

 

2020-07-06 04:56:07,268 DEBG 'start-script' stdout output:

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 24697

;; flags: qr rd ra ; QUERY: 1, ANSWER: 21, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;; nl.privateinternetaccess.com. IN A

 

;; ANSWER SECTION:

nl.privateinternetaccess.com. 300 IN CNAME nl.regions.cluster.piaservers.net.

nl.regions.cluster.piaservers.net. 120 IN A 109.201.154.202

nl.regions.cluster.piaservers.net. 120 IN A 109.201.154.141

nl.regions.cluster.piaservers.net. 120 IN A 46.166.137.242

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.222

nl.regions.cluster.piaservers.net. 120 IN A 46.166.188.226

nl.regions.cluster.piaservers.net. 120 IN A 46.166.188.203

nl.regions.cluster.piaservers.net. 120 IN A 46.166.138.145

nl.regions.cluster.piaservers.net. 120 IN A 46.166.137.227

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.208

nl.regions.cluster.piaservers.net. 120 IN A 109.201.154.178

nl.regions.cluster.piaservers.net. 120 IN A 46.166.188.206

nl.regions.cluster.piaservers.net. 120 IN A 46.166.186.221

nl.regions.cluster.piaservers.net. 120 IN A 46.166.138.166

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.203

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.186

nl.regions.cluster.piaservers.net. 120 IN A 46.166.188.244

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.230

nl.regions.cluster.piaservers.net. 120 IN A 46.166.188.219

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.191

nl.regions.cluster.piaservers.net. 120 IN A 46.166.190.187

 

;; AUTHORITY SECTION:

 

;; ADDITIONAL SECTION:

 

;; Query time: 33 msec

;; SERVER: 84.200.69.80

;; WHEN: Mon Jul  6 04:56:07 2020

;; MSG SIZE  rcvd: 413

 

2020-07-06 04:56:07,269 DEBG 'start-script' stdout output:

[debug] Show contents of hosts file

 

2020-07-06 04:56:07,270 DEBG 'start-script' stdout output:

127.0.0.1 localhost

::1 localhost ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

172.17.0.2 e4eb53a2c9fd

46.166.137.227 nl.privateinternetaccess.com

 

2020-07-06 04:56:07,277 DEBG 'start-script' stdout output:

[debug] Docker interface defined as eth0

 

2020-07-06 04:56:07,282 DEBG 'start-script' stdout output:

[debug] Docker IP defined as 172.17.0.2

 

2020-07-06 04:56:07,288 DEBG 'start-script' stdout output:

[debug] Docker netmask defined as 255.255.0.0

 

2020-07-06 04:56:07,302 DEBG 'start-script' stdout output:

[info] Docker network defined as    172.17.0.0/16

 

2020-07-06 04:56:07,307 DEBG 'start-script' stdout output:

[info] Adding 192.168.1.0/24 as route via docker eth0

 

2020-07-06 04:56:07,308 DEBG 'start-script' stdout output:

[info] ip route defined as follows...

--------------------

 

2020-07-06 04:56:07,310 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.1.0/24 via 172.17.0.1 dev eth0

 

2020-07-06 04:56:07,310 DEBG 'start-script' stdout output:

--------------------

[debug] Modules currently loaded for kernel

 

2020-07-06 04:56:07,314 DEBG 'start-script' stdout output:

Module                  Size  Used by

tun                    40960  0

nvidia_uvm           1024000  6

xt_nat                 16384  8

veth                   24576  0

xt_MASQUERADE          16384  9

iptable_filter         16384  1

iptable_nat            16384  1

nf_nat                 36864  3 xt_nat,iptable_nat,xt_MASQUERADE

ip_tables              28672  2 iptable_filter,iptable_nat

xfs                   671744  6

md_mod                 49152  6

it87                   45056  0

hwmon_vid              16384  1 it87

bonding               114688  0

nvidia_drm             40960  0

nvidia_modeset       1101824  1 nvidia_drm

nvidia              20381696  662 nvidia_uvm,nvidia_modeset

intel_uncore          118784  0

kvm_intel             208896  0

drm_kms_helper        151552  1 nvidia_drm

kvm                   397312  1 kvm_intel

drm                   360448  3 drm_kms_helper,nvidia_drm

intel_cstate           16384  0

coretemp               16384  0

mxm_wmi                16384  0

backlight              16384  1 drm

syscopyarea            16384  1 drm_kms_helper

sysfillrect            16384  1 drm_kms_helper

sysimgblt              16384  1 drm_kms_helper

fb_sys_fops            16384  1 drm_kms_helper

intel_powerclamp       16384  0

wmi                    24576  1 mxm_wmi

agpgart                32768  1 drm

i7core_edac            28672  0

ahci                   40960  8

i2c_i801               24576  0

i2c_core               45056  4 drm_kms_helper,nvidia,i2c_i801,drm

libahci                28672  1 ahci

crc32c_intel           24576  2

pata_jmicron           16384  0

e1000e                180224  0

acpi_cpufreq           16384  0

button                 16384  0

 

2020-07-06 04:56:07,396 DEBG 'start-script' stdout output:

[info] iptables defined as follows...

--------------------

 

2020-07-06 04:56:07,398 DEBG 'start-script' stdout output:

-P INPUT DROP

-P FORWARD DROP

-P OUTPUT DROP

-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT

-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -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 -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT

-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT

-A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT

-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -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

 

2020-07-06 04:56:07,400 DEBG 'start-script' stdout output:

--------------------

 

2020-07-06 04:56:07,402 DEBG 'start-script' stdout output:

[debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'pia' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE 'nl.privateinternetaccess.com' --setenv APPLICATION 'sabnzbd' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --remote 46.166.137.227 1198 udp --remote 46.166.137.242 1198 udp --remote 46.166.138.145 1198 udp --remote 46.166.138.166 1198 udp --remote 46.166.186.221 1198 udp --remote 46.166.188.203 1198 udp --remote 46.166.188.206 1198 udp --remote 46.166.188.219 1198 udp --remote 46.166.188.226 1198 udp --remote 46.166.188.244 1198 udp --remote 46.166.190.186 1198 udp --remote 46.166.190.187 1198 udp --remote 46.166.190.191 1198 udp --remote 46.166.190.203 1198 udp --remote 46.166.190.208 1198 udp --remote 46.166.190.222 1198 udp --remote 46.166.190.230 1198 udp --remote 109.201.154.141 1198 udp --remote 109.201.154.178 1198 udp --remote 109.201.154.202 1198 udp --remote-random --keepalive 10 60 --setenv STRICT_PORT_FORWARD 'yes' --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/Netherlands.ovpn'

[info] Starting OpenVPN...

 

2020-07-06 04:56:07,571 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:07 2020 WARNING: file 'credentials.conf' is group or others accessible

Mon Jul  6 04:56:07 2020 OpenVPN 2.4.9 [git:makepkg/9b0dafca6c50b8bb+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 20 2020

Mon Jul  6 04:56:07 2020 library versions: OpenSSL 1.1.1g  21 Apr 2020, LZO 2.10

 

2020-07-06 04:56:07,573 DEBG 'start-script' stdout output:

[info] OpenVPN started

 

2020-07-06 04:56:07,573 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:07 2020 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

 

2020-07-06 04:56:07,578 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:07 2020 CRL: loaded 1 CRLs from file [[INLINE]]

 

2020-07-06 04:56:07,578 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:07 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]46.166.137.242:1198

Mon Jul  6 04:56:07 2020 UDP link local: (not bound)

Mon Jul  6 04:56:07 2020 UDP link remote: [AF_INET]46.166.137.242:1198

 

2020-07-06 04:56:07,697 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:07 2020 [3d0f5c751846edb686acc3a0d71e6b21] Peer Connection Initiated with [AF_INET]46.166.137.242:1198

 

2020-07-06 04:56:08,835 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:08 2020 TUN/TAP device tun0 opened

Mon Jul  6 04:56:08 2020 /usr/bin/ip link set dev tun0 up mtu 1500

 

2020-07-06 04:56:08,837 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:08 2020 /usr/bin/ip addr add dev tun0 local 10.74.10.6 peer 10.74.10.5

 

2020-07-06 04:56:08,839 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:08 2020 /root/openvpnup.sh tun0 1500 1558 10.74.10.6 10.74.10.5 init

 

2020-07-06 04:56:08,846 DEBG 'start-script' stdout output:

[debug] Waiting for valid IP address from tunnel...

 

2020-07-06 04:56:08,851 DEBG 'start-script' stdout output:

Mon Jul  6 04:56:08 2020 Initialization Sequence Completed

 

2020-07-06 04:56:08,973 DEBG 'start-script' stdout output:

[debug] Valid IP address from tunnel acquired '10.74.10.6'

 

2020-07-06 04:56:08,974 DEBG 'start-script' stdout output:

[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

 

2020-07-06 04:56:08,975 DEBG 'start-script' stdout output:

[info] Checking we can resolve name 'www.google.com' to address...

 

2020-07-06 04:56:09,007 DEBG 'start-script' stdout output:

[info] DNS operational, we can resolve name 'www.google.com' to address '172.217.168.228'

 

2020-07-06 04:56:09,010 DEBG 'start-script' stdout output:

[info] Application does not require external IP address, skipping external IP address detection

 

2020-07-06 04:56:09,021 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:56:09,034 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:56:09,043 DEBG 'watchdog-script' stdout output:

[info] SABnzbd not running

 

2020-07-06 04:56:09,053 DEBG 'watchdog-script' stdout output:

[info] Privoxy not running

 

2020-07-06 04:56:09,053 DEBG 'watchdog-script' stdout output:

[info] Attempting to start SABnzbd...

 

2020-07-06 04:56:10,594 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process started

[info] Waiting for SABnzbd process to start listening on port 8080...

 

2020-07-06 04:56:10,823 DEBG 'watchdog-script' stdout output:

[info] SABnzbd process is listening on port 8080

 

2020-07-06 04:56:10,837 DEBG 'watchdog-script' stdout output:

[info] Attempting to start Privoxy...

 

2020-07-06 04:56:11,863 DEBG 'watchdog-script' stdout output:

[info] Privoxy process started

[info] Waiting for Privoxy process to start listening on port 8118...

 

2020-07-06 04:56:11,870 DEBG 'watchdog-script' stdout output:

[info] Privoxy process listening on port 8118

 

2020-07-06 04:56:11,870 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:56:41,876 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:56:41,886 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:56:41,902 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:57:11,910 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:57:11,922 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:57:11,943 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:57:41,950 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:57:41,959 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:57:41,977 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:58:11,985 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:58:11,999 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:58:12,019 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:58:42,028 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:58:42,039 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:58:42,057 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:59:12,066 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:59:12,079 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:59:12,102 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 04:59:42,110 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 04:59:42,123 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 04:59:42,144 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:00:12,161 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:00:12,173 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:00:12,203 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:00:42,215 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:00:42,229 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:00:42,248 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:01:12,258 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:01:12,269 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:01:12,288 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:01:42,299 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:01:42,311 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:01:42,332 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:02:12,341 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:02:12,355 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:02:12,378 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:02:42,387 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:02:42,399 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:02:42,420 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:03:12,429 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:03:12,440 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:03:12,462 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:03:42,471 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:03:42,484 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:03:42,503 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:04:12,511 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:04:12,525 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:04:12,546 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:04:42,555 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:04:42,568 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:04:42,587 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:05:12,594 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:05:12,606 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:05:12,623 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:05:42,632 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:05:42,646 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:05:42,666 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:06:12,676 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:06:12,689 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:06:12,710 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:06:42,721 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:06:42,731 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:06:42,751 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:07:12,760 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:07:12,774 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:07:12,797 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:07:42,806 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:07:42,819 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:07:42,837 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:08:12,846 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:08:12,859 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:08:12,877 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:08:42,886 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:08:42,900 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:08:42,922 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:09:12,929 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:09:12,939 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:09:12,960 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:09:42,967 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:09:42,979 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:09:42,998 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:10:13,007 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:10:13,019 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:10:13,042 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:10:43,051 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:10:43,066 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:10:43,087 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:11:13,096 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:11:13,111 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:11:13,132 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:11:43,141 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:11:43,154 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:11:43,175 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:12:13,184 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:12:13,197 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:12:13,217 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:12:43,227 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:12:43,239 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:12:43,259 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:13:13,266 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:13:13,280 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:13:13,302 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:13:43,311 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:13:43,325 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:13:43,348 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:14:13,358 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:14:13,371 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:14:13,392 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:14:43,402 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:14:43,414 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:14:43,437 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:15:13,446 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:15:13,460 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:15:13,481 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:15:43,491 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:15:43,503 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:15:43,525 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:16:13,535 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:16:13,548 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:16:13,570 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:16:43,579 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:16:43,593 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:16:43,614 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:17:13,623 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:17:13,636 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:17:13,658 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:17:43,667 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:17:43,680 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:17:43,701 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:18:13,710 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:18:13,723 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:18:13,744 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:18:43,753 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:18:43,768 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:18:43,784 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

2020-07-06 05:19:13,794 DEBG 'watchdog-script' stdout output:

[debug] Waiting for iptables chain policies to be in place...

 

2020-07-06 05:19:13,807 DEBG 'watchdog-script' stdout output:

[debug] iptables chain policies are in place

 

2020-07-06 05:19:13,829 DEBG 'watchdog-script' stdout output:

[debug] VPN IP is 10.74.10.6

 

Link to comment
15 minutes ago, GaryBellars said:

Hi Binhex. Thank you for this. Here is my log file. I have added the word REMOVED where my log in details were.

that looks like a successful start to me, what is the ip address of the client you are using to access sabnzbd web ui?

Link to comment

 

5 hours ago, binhex said:

your issue will be most probably vpn provider related, please do the following:-

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

 Thank you!  It was the modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/4.19.107-Unraid error.  That made me re-look at my configs.  When I had restored this container it was from a previous backup that had the wrong LAN_NETWORK defined.  Interestingly though, if I manually ran the modprobe iptable_mangle command, I could access the WebUI even though I had the wrong LAN_NETWORK defined.  But I corrected it the proper way.  Thanks!

Link to comment

 

3 hours ago, binhex said:

then thats your problem, you have lan_network defined as:-

2020-07-06 04:56:04.965798 [info] LAN_NETWORK defined as '192.168.1.0/24'

 

read Q4 here on how to set it correctly:-

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

The IP for my Server on my router is 192.168.0.91. So when you say client do you mean my VPN or my Router? I have included my network settings as a screen shot. 

Screenshot 2020-07-06 at 17.02.53.png

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.