-
[Support] binhex - SABnzbdVPN
Hey guys, i have problem. I want to use binhex-sabnzbdvpn with his built in VPN. The network type is bridge and I'm using nordvpn. I filled in the right credentials, uploaded the right udp.opvpn (checked it more than 5 times), STRICT_PORT_FORWARD is set to "NO" and ENABLE_PRIVOXY is set to "YES". When I'm activating the VPN, i have no access to the WebUI, when I'm deactivating it, I have access. Can someone telling me what I'm doing wrong? Yesterday it worked for a short time but now it stopped working out of a sudden. 2024-10-04 06:31:49 VERIFY KU OK 2024-10-04 06:31:49 Validating certificate extended key usage 2024-10-04 06:31:49 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2024-10-04 06:31:49 VERIFY EKU OK 2024-10-04 06:31:49 VERIFY X509NAME OK: CN=ch223.nordvpn.com 2024-10-04 06:31:49 VERIFY OK: depth=0, CN=ch223.nordvpn.com 2024-10-04 06:31:49,869 DEBG 'start-script' stdout output: 2024-10-04 06:31:49 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 2024-10-04 06:31:49 [ch223.nordvpn.com] Peer Connection Initiated with [AF_INET]185.156.175.123:1194 2024-10-04 06:31:49 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 2024-10-04 06:31:49,869 DEBG 'start-script' stdout output: 2024-10-04 06:31:49 TLS: tls_multi_process: initial untrusted session promoted to trusted 2024-10-04 06:31:50,958 DEBG 'start-script' stdout output: 2024-10-04 06:31:50 SENT CONTROL [ch223.nordvpn.com]: 'PUSH_REQUEST' (status=1) 2024-10-04 06:31:50 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 103.86.96.100,dhcp-option DNS 103.86.99.100,explicit-exit-notify,comp-lzo no,route-gateway 10.100.0.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.100.0.2 255.255.255.0,peer-id 2,cipher AES-256-GCM' 2024-10-04 06:31:50,959 DEBG 'start-script' stdout output: 2024-10-04 06:31:50 OPTIONS IMPORT: --ifconfig/up options modified 2024-10-04 06:31:50 OPTIONS IMPORT: route options modified 2024-10-04 06:31:50 OPTIONS IMPORT: route-related options modified 2024-10-04 06:31:50 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 2024-10-04 06:31:50 net_route_v4_best_gw query: dst 0.0.0.0 2024-10-04 06:31:50 net_route_v4_best_gw result: via 172.17.0.1 dev eth0 2024-10-04 06:31:50 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:02 2024-10-04 06:31:50 TUN/TAP device tun0 opened 2024-10-04 06:31:50 net_iface_mtu_set: mtu 1500 for tun0 2024-10-04 06:31:50 net_iface_up: set tun0 up 2024-10-04 06:31:50 net_addr_v4_add: 10.100.0.2/24 dev tun0 2024-10-04 06:31:50,960 DEBG 'start-script' stdout output: 2024-10-04 06:31:50 /root/openvpnup.sh tun0 1500 0 10.100.0.2 255.255.255.0 init 2024-10-04 06:31:50,967 DEBG 'start-script' stdout output: 2024-10-04 06:31:50 net_route_v4_add: 185.156.175.123/32 via 172.17.0.1 dev [NULL] table 0 metric -1 2024-10-04 06:31:50,968 DEBG 'start-script' stdout output: 2024-10-04 06:31:50 net_route_v4_add: 0.0.0.0/1 via 10.100.0.1 dev [NULL] table 0 metric -1 2024-10-04 06:31:50 net_route_v4_add: 128.0.0.0/1 via 10.100.0.1 dev [NULL] table 0 metric -1 2024-10-04 06:31:50 Initialization Sequence Completed 2024-10-04 06:31:50 Data Channel: cipher 'AES-256-GCM', peer-id: 2, compression: 'stub' 2024-10-04 06:31:50 Timers: ping 60, ping-restart 180 2024-10-04 06:31:50 Protocol options: explicit-exit-notify 1 2024-10-04 06:31:50,974 DEBG 'start-script' stdout output: [debug] Waiting for valid VPN gateway IP addresses from tunnel... [debug] Waiting for valid VPN adapter IP addresses from tunnel... 2024-10-04 06:31:51,998 DEBG 'start-script' stdout output: [debug] Valid local IP address from tunnel acquired '10.100.0.2' 2024-10-04 06:31:51,999 DEBG 'start-script' stdout output: [debug] Valid gateway IP address from tunnel acquired '' [debug] Checking we can resolve name 'www.google.com' to address... 2024-10-04 06:31:52,008 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2024-10-04 06:31:52,045 DEBG 'start-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '142.250.185.132' 2024-10-04 06:31:52,046 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-10-04 06:31:52,048 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '192.0.0.88' 2024-10-04 06:31:52,211 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 194.15.111.220 2024-10-04 06:31:52,211 DEBG 'start-script' stdout output: [info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment 2024-10-04 06:31:52,252 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2024-10-04 06:31:52,254 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2024-10-04 06:31:52,256 DEBG 'watchdog-script' stdout output: [info] SABnzbd not running 2024-10-04 06:31:52,257 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2024-10-04 06:31:52,257 DEBG 'watchdog-script' stdout output: [info] Attempting to start SABnzbd... 2024-10-04 06:31:52,649 DEBG 'watchdog-script' stdout output: [info] SABnzbd process started [info] Waiting for SABnzbd process to start listening on port 8080... 2024-10-04 06:31:52,868 DEBG 'watchdog-script' stdout output: [info] SABnzbd process is listening on port 8080 2024-10-04 06:31:52,869 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2024-10-04 06:31:53,878 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2024-10-04 06:31:53,886 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118 2024-10-04 06:31:53,886 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.100.0.2 2024-10-04 06:32:23,894 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2024-10-04 06:32:23,936 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '192.0.0.88' 2024-10-04 06:32:23,937 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2024-10-04 06:32:23,945 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2024-10-04 06:32:23,955 DEBG 'watchdog-script' stdout output: [debug] VPN IP is 10.100.0.2
-
[PLUGIN] GPU Statistics
Thanks, that was exactly what fixed my issue too.
-
[PLUGIN] GPU Statistics
- [PLUGIN] GPU Statistics
Here is the result: Time = Fri, 12 Apr 2024 17:59:00 +0200 {"00:02.0":{"clock":0,"fan":"N\/A","memclock":"N\/A","memutil":"N\/A","memused":"N\/A","power":"0W","powermax":"N\/A","rxutil":"N\/A","txutil":"N\/A","temp":"N\/A","tempmax":"N\/A","util":"0%","vendor":"Intel","name":"Alder Lake-S GT1 [UHD Graphics 730]","3drender":"0%","blitter":"0%","interrupts":1,"powerutil":"0%","video":"0%","videnh":"0%","vfio":false,"vfiochk":false,"vfiochkid":"0000:00:02.0","panel":1}}Chriss_93 started following [PLUGIN] GPU Statistics- [PLUGIN] GPU Statistics
My Gpu Stats are closing right after I've opened them. Everything is up to date, only Unraid is on 6.12.8 because I tried if it is working when I go back. It shows me, that the "Gpu not available bound to Vfio or in use in a VM" I have no VM running and it is not bound in VFIO. Is there a workaround to get this fixed? I reinstalled everything more than once but the issue still exists. - [PLUGIN] GPU Statistics
Chriss_93
Members
-
Joined
-
Last visited