bull

If the creator wanted to hook up on discord or Facebook messenger id be more than happy to go through things on my stack with them to try and figure out a cause to get thus thing figured out for others

It seems to just be a issue for new adopters if you look through this thread you folks that have had it a while seem to not be affected

Same and it's a shame some recent issue broke this plugin

Frankly the lack of even a response forced me to go to a different monitor system that actually works... the never populating servers but getting the token is a issue that needs addressing .. till then tautulli it is..

after a long time of things running right i now cannot log into the webui the only error in the log i find that corresponds to this is 2025-09-28 13:59:23,469 DEBG 'start-script' stderr output: insmod: ERROR: could not load module /lib/modules/iptable_mangle.ko: No such file or directory so any ideals? how to repair this issue? found somthing saying to add this to the /boot/config/go file "# force iptable mangle module to load (required for *vpn dockers) /sbin/modprobe iptable_mangle" tried it and it seemed to solve the issue

Installed Get token Infinite search Delete token Get new token Infinite search Uninstall Reinstall Get token Infinite search Done this multiple time yes have plexpass yes remote is on and working Any advice?

solved ... changed some things and got it working again ..not sure which was the solve but its working again

so my webui access just died didnt change anything that i know off and the container seems to be running right heres the log text error warn system array login -A OUTPUT -o eth0 -p udp -m udp --sport 8112 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.187.0/24 -o eth0 -p tcp -m tcp --sport 58846 -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-01-14 23:31:28,045 DEBG 'start-script' stdout output: -------------------- 2024-01-14 23:31:28,046 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2024-01-14 23:31:28,060 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 2024-01-14 23:31:28 Note: '--allow-compression' is not set to 'no', disabling data channel offload. 2024-01-14 23:31:28,060 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 WARNING: file 'credentials.conf' is group or others accessible 2024-01-14 23:31:28 OpenVPN 2.6.7 [git:makepkg/53c9033317b3b8fd+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on Nov 9 2023 2024-01-14 23:31:28 library versions: OpenSSL 3.1.4 24 Oct 2023, LZO 2.10 2024-01-14 23:31:28 DCO version: N/A 2024-01-14 23:31:28,060 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 WARNING: --ping should normally be used with --ping-restart or --ping-exit 2024-01-14 23:31:28 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-01-14 23:31:28,061 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 TCP/UDP: Preserving recently used remote address: [AF_INET]37.19.213.177:1194 2024-01-14 23:31:28,061 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 Socket Buffers: R=[212992->212992] S=[212992->212992] 2024-01-14 23:31:28 UDPv4 link local: (not bound) 2024-01-14 23:31:28 UDPv4 link remote: [AF_INET]37.19.213.177:1194 2024-01-14 23:31:28,082 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 TLS: Initial packet from [AF_INET]37.19.213.177:1194, sid=2e5cd5aa 6b23777b 2024-01-14 23:31:28,133 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 VERIFY OK: depth=2, C=PA, O=NordVPN, CN=NordVPN Root CA 2024-01-14 23:31:28,133 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 VERIFY OK: depth=1, O=NordVPN, CN=NordVPN CA8 2024-01-14 23:31:28 VERIFY KU OK 2024-01-14 23:31:28 Validating certificate extended key usage 2024-01-14 23:31:28 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication 2024-01-14 23:31:28 VERIFY EKU OK 2024-01-14 23:31:28 VERIFY X509NAME OK: CN=ca1472.nordvpn.com 2024-01-14 23:31:28 VERIFY OK: depth=0, CN=ca1472.nordvpn.com 2024-01-14 23:31:28,157 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 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-01-14 23:31:28 [ca1472.nordvpn.com] Peer Connection Initiated with [AF_INET]37.19.213.177:1194 2024-01-14 23:31:28 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 2024-01-14 23:31:28 TLS: tls_multi_process: initial untrusted session promoted to trusted 2024-01-14 23:31:28,758 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 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.8.2.1,topology subnet,ping 60,ping-restart 180,ifconfig 10.8.2.6 255.255.255.0,peer-id 0,cipher AES-256-GCM' 2024-01-14 23:31:28 OPTIONS IMPORT: --ifconfig/up options modified 2024-01-14 23:31:28 OPTIONS IMPORT: route options modified 2024-01-14 23:31:28 OPTIONS IMPORT: route-related options modified 2024-01-14 23:31:28 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 2024-01-14 23:31:28,759 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 net_route_v4_best_gw query: dst 0.0.0.0 2024-01-14 23:31:28 net_route_v4_best_gw result: via 172.17.0.1 dev eth0 2024-01-14 23:31:28 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=02:42:ac:11:00:05 2024-01-14 23:31:28 TUN/TAP device tun0 opened 2024-01-14 23:31:28,759 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 net_iface_mtu_set: mtu 1500 for tun0 2024-01-14 23:31:28 net_iface_up: set tun0 up 2024-01-14 23:31:28 net_addr_v4_add: 10.8.2.6/24 dev tun0 2024-01-14 23:31:28 /root/openvpnup.sh tun0 1500 0 10.8.2.6 255.255.255.0 init 2024-01-14 23:31:28,763 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 net_route_v4_add: 37.19.213.177/32 via 172.17.0.1 dev [NULL] table 0 metric -1 2024-01-14 23:31:28,763 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 net_route_v4_add: 0.0.0.0/1 via 10.8.2.1 dev [NULL] table 0 metric -1 2024-01-14 23:31:28 net_route_v4_add: 128.0.0.0/1 via 10.8.2.1 dev [NULL] table 0 metric -1 2024-01-14 23:31:28,763 DEBG 'start-script' stdout output: 2024-01-14 23:31:28 Initialization Sequence Completed 2024-01-14 23:31:28 Data Channel: cipher 'AES-256-GCM', peer-id: 0, compression: 'stub' 2024-01-14 23:31:28 Timers: ping 60, ping-restart 180 2024-01-14 23:31:28 Protocol options: explicit-exit-notify 1 2024-01-14 23:31:30,017 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-01-14 23:31:38,139 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 86.48.15.71 2024-01-14 23:31:38,141 DEBG 'start-script' stdout output: [info] VPN provider 'custom' not supported for automatic port forwarding, skipping incoming port assignment 2024-01-14 23:31:44,906 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.8.2.6 different, marking for reconfigure 2024-01-14 23:31:44,911 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2024-01-14 23:31:44,915 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2024-01-14 23:31:44,916 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2024-01-14 23:31:45,188 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.7.3.6' [info] Deluge key 'listen_interface' will have a new value '10.8.2.6' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-01-14 23:31:45,370 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2024-01-14 23:31:45,526 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'eba75c33395746b2952178b39c519a54' [info] Deluge key 'default_daemon' will have a new value 'eba75c33395746b2952178b39c519a54' [info] Writing changes to Deluge config file '/config/web.conf'... 2024-01-14 23:31:45,558 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2024-01-14 23:31:45,874 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2024-01-14 23:31:47,477 DEBG 'watchdog-script' stderr output: <Deferred at 0x154bc57ea810 current result: None> 2024-01-14 23:31:47,530 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2024-01-14 23:31:47,531 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2024-01-14 23:31:47,531 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started

So I'm having issues with wiregaurd on 6.11.5 also tried reverting to 6.11.4 So I set up wiregaurd and a peer do the port forwarding tried several of my ddns service addresses Seems nothing I do can I get wiregaurd to work ..I had it working once long ago then it went for a poop and so I started using TeamViewer to access from remote.. this is becoming a pain in the butt So can anyone help me solve this issue? Wiregaurd turns on but no handshake happens

so I came across a weird little thing so I decided to run 2 instances of deluge for my own organizational ease and to try and get more download per hour ( not sure its going to work but worth a try. Essentially movies through one tv shows through the other) now the issue I came to find is if I try to open two windows in firefox each with a separate gui for each of the deluge instances ( both are working downloading and operating fine ), it instantly logs out the other one. I tried it with private browsing sessions thinking maybe it was a cookie thing, Still same effect. Had another user who has multiple instances try this aswell and he had the same result. He tried with 2 different browser (chrome and braver) and it didnt kick him out of the other .. Something maybe to look into or maybe a setting that needs to be changed somewhere?

so installed via spaceinvaders video but the docker stalls at starting mariadb any help?