voicelex

Hi, I just noticed that about 2 weeks ago Tautulli stopped logging my activity - I've seen it miss things before but this seems permanent. When I have an active stream is shows my user as "Local." The device I am streaming from (Shield) is logged in and I have tried clearing the data of the app and signing in again to no avail. I have tried re-authenticating the server in the Tautulli settings and fetching a new token multiple times. I can not edit the user named "Local" and it does not show up in the history anywhere - it only shows active streams. Any advice is welcomed, thank you!

Thanks @JorgeB, this was my first NVME drive - are they really that short lived? I didn't expect using it as a cache drive and for the usual Plex related dockers would be that hard on it - certainly less than using it as a windows OS drive.. Oh well, glad to hear this is likely the issue, I needed a bigger one anyway!

I woke up to a new error message today: "Warning [SERENITY] - Cache pool BTRFS missing device(s)" and found my cache drive (NVME) to be missing. A reboot didn't fix it so I shut it down, checked the BIOS and found the drive was still recognized by the mobo at the very least. When I powered back up I saw "critical media error" flash by during boot but once in the UI, the drive was magically available again to mount as the cache drive. After mounting I was greeted with "Unmountable: No file system" and stopped there. I saw this guide but am looking for input before I begin going down an unfamiliar path. I've attached my syslog and the SMART report for the drive with the following seeming to be the highlight: SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode Syslog had many iterations of this with different sector numbers: kernel: print_req_error: critical medium error, dev nvme0n1, sector 272 Is this drive dead or is it simply that the filesystem has suddenly been corrupted? I do run a weekly cache appdata backup on Mondays at 3am, but the initial error message came around midnight. I'm hoping my backup is intact. Thanks for any help, I've been running Unraid for a while now but like many, just keep learning as I go along. I appreciate your patience. WDC_WDS256G1X0C-00ENX0_174264804634-20210201-1844.txt syslog.txt

Good to know. So is this known to cause issues with download speeds in deluge over a vpn connection? Just seems more likely to be a deluge issue? Since I wasn't having the issue on 6.8.3 until the deluge update that broke it entirely and was temporarily fixed by the :test branch, but has since been resolved in the newest docker image.

Can you be more specific? This appears to be the latest stable version and I've not had any other issues with it. Is there a known issue with 6.8.3 and this docker?

Hello, I've been scanning through the last several pages but can't seem to figure out what wrong on my end. My speeds have been so slow for a few weeks now and even after migrating from the :test image I had used as a temporary fix to the newest one via update just now, I am still either not being connected to very busy torrents or getting terrible speeds. Any help would be appreciated, thanks for all your work binhex and other devs! Unraid 6.8.3 latest binhex-delugevpn ExpressVPN with a .ovpn file and credentials.conf Happy to post logs but the only flags I'm seeing are just depreciated features relating to OVPN 2.6 and cipher options

@dzyuba86, thanks for the insight, that make sense. Now what I'm wondering is; how to use pfblocker to create whole home domain-level blocking rules without disrupting my VPN connection in deluge on my unraid box! I love the abilities of pfblocker but they don't seem to work without forcing all DNS through pfsesnse via port 53. Probably a question that exceeds the limits of this thread but I'm sure I'll figure it out eventually. Thanks for your help!

So strange, I've never changed them but did recently make a mod to my PFsense router but over a week ago and didn't have any issues with deluge until today. I'll try changing them. *EDIT Ok, so I turned off the rules I was using to enable pfblocker for domain-level site blocking on my pfsense router and that seemed to have worked! I'm just confused as to why it was working fine until now.

I'm using ExpressVPN and have no issue logging in with their app right now. Below is the most recent log after restarting the docker and it going through the same routine as before then getting to this: 2020-07-27 14:02:03.436684 [info] Starting Supervisor... 2020-07-27 14:02:03,558 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2020-07-27 14:02:03,558 INFO Set uid to user 0 succeeded 2020-07-27 14:02:03,560 INFO supervisord started with pid 7 2020-07-27 14:02:04,563 INFO spawned: 'start-script' with pid 172 2020-07-27 14:02:04,566 INFO spawned: 'watchdog-script' with pid 173 2020-07-27 14:02:04,566 INFO reaped unknown pid 8 (exit status 0) 2020-07-27 14:02:04,571 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2020-07-27 14:02:04,571 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-07-27 14:02:04,572 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-07-27 14:02:04,630 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2020-07-27 14:02:04,633 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2020-07-27 14:02:04,635 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2020-07-27 14:02:04,638 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2020-07-27 14:02:04,640 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2020-07-27 14:02:04,643 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2020-07-27 14:02:04,645 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2020-07-27 14:02:04,647 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2020-07-27 14:02:04,650 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2020-07-27 14:04:04,774 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:06:04,911 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:08:10,046 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:10:15,179 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:12:20,310 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:14:25,447 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:16:30,574 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:18:35,713 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:20:40,852 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:22:45,987 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:24:51,119 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:26:56,243 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 14:27:01,247 DEBG 'start-script' stdout output: [crit] 'XXXX.XXXX.com' cannot be resolved, possible DNS issues, exiting... 2020-07-27 14:27:01,247 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140337127370656 for <Subprocess at 140337127631648 with name start-script in state RUNNING> (stderr)> 2020-07-27 14:27:01,247 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140337127370704 for <Subprocess at 140337127631648 with name start-script in state RUNNING> (stdout)> 2020-07-27 14:27:01,247 INFO exited: start-script (exit status 1; not expected) 2020-07-27 14:27:01,247 DEBG received SIGCHLD indicating a child quit

Thanks @dzyuba86, as far as I can tell no IP addresses have changed on the server. I haven't modified anything for a while, I'm wondering if something happened during an update this morning (how can I tell if it was updated)? I checked my vpn login/pass and those are fine then updated the .ovpn file and the .crt and .key files. No luck. Any other logs I can provide that might show what's going on?

All of a sudden today I am unable to access the webUI and the other dockers I have that route through DelugeVPN won't open either. Here is the log after a full system reboot 2020-07-27 13:11:08.073496 [info] System information Linux da35d62395cd 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2020-07-27 13:11:08.299559 [info] OS_ARCH defined as 'x86-64' 2020-07-27 13:11:08.409419 [info] PUID defined as '99' 2020-07-27 13:11:08.557573 [info] PGID defined as '100' 2020-07-27 13:11:08.629505 [info] UMASK defined as '000' 2020-07-27 13:11:08.661207 [info] Permissions already set for volume mappings 2020-07-27 13:11:08.710061 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info' 2020-07-27 13:11:08.731967 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info' 2020-07-27 13:11:08.759573 [info] VPN_ENABLED defined as 'yes' 2020-07-27 13:11:08.793587 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/REMOVED PERSONAL INFO.ovpn 2020-07-27 13:11:08.835643 [info] VPN remote line defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:08.858853 [info] VPN_REMOTE defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:08.883133 [info] VPN_PORT defined as '1195' 2020-07-27 13:11:08.928603 [warn] VPN_PROTOCOL not found in /config/openvpn/REMOVED PERSONAL INFO, assuming udp 2020-07-27 13:11:08.952788 [info] VPN_DEVICE_TYPE defined as 'tun0' 2020-07-27 13:11:08.974123 [info] VPN_PROV defined as 'custom' 2020-07-27 13:11:09.005118 [info] LAN_NETWORK defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:09.037213 [info] NAME_SERVERS defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:09.091583 [info] VPN_USER defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:09.125526 [info] VPN_PASS defined as 'REMOVED PERSONAL INFO' 2020-07-27 13:11:09.147223 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2020-07-27 13:11:09.168214 [info] ENABLE_PRIVOXY defined as 'yes' 2020-07-27 13:11:09.191541 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports 2020-07-27 13:11:09.275026 [info] Deleting files in /tmp (non recursive)... 2020-07-27 13:11:09.296517 [info] Starting Supervisor... 2020-07-27 13:11:10,253 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2020-07-27 13:11:10,253 INFO Set uid to user 0 succeeded 2020-07-27 13:11:10,285 INFO supervisord started with pid 11 2020-07-27 13:11:11,286 INFO spawned: 'start-script' with pid 176 2020-07-27 13:11:11,287 INFO spawned: 'watchdog-script' with pid 177 2020-07-27 13:11:11,288 INFO reaped unknown pid 12 (exit status 0) 2020-07-27 13:11:11,297 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2020-07-27 13:11:11,297 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-07-27 13:11:11,297 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-07-27 13:11:11,444 DEBG 'start-script' stdout output: [info] Default route for container is REMOVED PERSONAL INFO 2020-07-27 13:11:11,447 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,452 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,467 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,473 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,480 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,487 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,504 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:11:11,511 DEBG 'start-script' stdout output: [info] Adding REMOVED PERSONAL INFO to /etc/resolv.conf 2020-07-27 13:13:11,641 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 13:15:11,766 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error 2020-07-27 13:17:16,888 DEBG 'start-script' stderr output: Error: error sending query: Could not send or receive, because of network error

I'll try replacing the cable and see how it goes. I usually see one new error every time I reboot or have some larger docker updates. I'll swap and report back.

Hello, I've been using unraid for 2 years now and while I feel like I've learned a lot, I still feel very in the dark when it comes to drive health. I've been slowly getting an error or two for a while now and the number has added up. This is me ending my procrastination to figure it out. I've noticed these errors can be caused by a bad connection but I haven't opened the box in a long while. Happy to try swapping cables but in the meantime, I've attached my diagnostics file in the hope that I can be pointed towards some resources or given some advice on what to do. serenity-diagnostics-20191228-1404.zip

Wow, so strange! I tried manually mapping the static IP even though the device wasn't listed in the DHCP leases and it worked! It shows as online and now my misbehaving dockers are working. Anyone know why that is and is there a way to be sure that all my unRAID server traffic is going through pfSense rather than being bridged from the WAN plugged into the quad NIC (that pfsense is setup to use)?

Howdy, I'm working on setting up pfSense as a VM on my server with a dedicated quad-port NIC as the WAN in and LAN out. I am able to connect to the server via it's assigned IP and it has internet access, however, it is not showing under the list of DHCP leases in the pfSense webGUI. I want to be sure that the server is behind the pfSense VM so that I might control my entire network - especially the unRAID box. Here's a visualization of my setup. I have the quad-nic that the VM is using removed from unRAID via the "append vfio-pci.ids=xxxxx" statement both in OS and OS GUI mode. I've changed the Network Settings to disable Bonding & Bridging. All dockers are running in Bridge mode (they don't seem to work in host mode - could someone explain the difference?) except Plex which is in host mode and is working fine LAN access. I've also noticed that although deluge is working, Radarr is not - the webGUI will load but it seems to have no WAN access. Thanks for any advice, please let me know if I can provide more information.