Sabnzb Stopping The Internet


Badboy

Recommended Posts

Hi,

For some strange reason as soon as I turn Sabnzb (linuxserver version) on it shuts the internet down. It has been setup the same way for a long time.

Own ip address - connected to Nordvpn.  Still does it with Nordvpn off.  It is acting like a firewall is kicking in but not seeing any blockage for it.

 

Have a ASUS Router RT-Ac5300 on Merlin Firmware - Firmware is up to date. 

 

In the router logs I found this.  I know it's related to Nord, not sure fully what it means.

Sep  6 01:57:04 ovpn-client1[17461]: TLS: tls_process: killed expiring key
Sep  6 01:57:04 ovpn-client1[17461]: VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA
Sep  6 01:57:04 ovpn-client1[17461]: VERIFY OK: depth=1, C=PA, O=NordVPN, CN=NordVPN CA5
Sep  6 01:57:04 ovpn-client1[17461]: VERIFY KU OK
Sep  6 01:57:04 ovpn-client1[17461]: Validating certificate extended key usage
Sep  6 01:57:04 ovpn-client1[17461]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sep  6 01:57:04 ovpn-client1[17461]: VERIFY EKU OK
Sep  6 01:57:04 ovpn-client1[17461]: VERIFY OK: depth=0, CN=ca1014.nordvpn.com
Sep  6 01:57:05 ovpn-client1[17461]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sep  6 01:57:05 ovpn-client1[17461]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sep  6 01:57:05 ovpn-client1[17461]: Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Sep  6 01:57:26 syslog: WLCEVENTD wlceventd_proc_event(420): eth3: Auth 30:FD:38:C9:BB:32, status: 0, reason: d11 RC reserved (0)
Sep  6 01:57:26 syslog: WLCEVENTD wlceventd_proc_event(430): eth3: ReAssoc 30:FD:38:C9:BB:32, status: 0, reason: d11 RC reserved (0)
Sep  6 01:57:26 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc 30:FD:38:C9:BB:32, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Sep  6 01:57:26 syslog: WLCEVENTD wlceventd_proc_event(401): eth2: Disassoc 30:FD:38:C9:BB:32, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)

 

Any ideas?

 

Thanks

Link to comment
  • 2 weeks later...

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.