DeepSee

Under my default values you can see one of the two 209.x.x.x ip address (I deleted them in the value field) However on Binhex's Github those two ip address have been removed. Not sure why mine still has it with it being up to date. I have had his delugevpn since Jan 2021 so maybe just wasn't removed for my updated but others have downloaded a version that never had them listed?? But i noticed that this morning before i decided to try and remove them. Not sure but if you don't have them I have no idea what to try. Binhex thanks for everything you do. Your time and energy keeps the community going.

I think we have the same problem check out my post above and see if it works for you.

After a couple of years of having delugevpn, jackett, radarr, and sonarr all work together (except the tightening of the IP table thing a while back) earlier this month I could not get Sonarr and Radarr to search for any movies while using the proxy option back to my delugevpn. So after some troubleshooting I turned off proxy in sonarr and radarr and works as advertised, however I have proxy set up in jacket and I don't have any problems connecting. I found someone with this issue on the github support and they had to delete the two 209.x.x.x ip address on the "named server variable". I just did the same thing and now I can proxy my sonarr and radarr back to the deluge vpn docker. Since everything is back to working like it has for the last couple of years who would like to explain to me why those two IP address were not allowing two out of the three programs to proxy through delugevpn? And do I need those ip address for any reason? Also, I've read places since jackett is proxy through delugevpn there is no real reason to have sonarr and radarr also proxy, if that is true can someone verify that? I looked up the first ip and it was located in New Jersey but didn't look up the second one that I had to delete. by the way i use express vpn if that matters.

I started having this issue about two weeks ago when I updated deluge. What do you mean by removing the 209.x IPs? I am having this issue and the only way to keep radar working is to not use proxy.

I updated to the latest to version today and I kept getting the same log error over and over: 2023-02-07 13:13:43,642 DEBG 'start-script' stdout output: Options error: Unrecognized option or missing or extra parameter(s) in /config/openvpn/my_expressvpn_usa_-_washington_dc_udp.ovpn:20: keysize (2.6.0) Use --help for more information. I was not able to access the Web UI. I first tried a couple different end points by changing the ovpn file. That did not work. I then rolled back the docker 2.1.1-3-01 and it worked fine. I didn't want too to settle for that after some reading on here I just put a # in front of "keysize 256" to comment it out. And it works fine not sure if that will be something we will have to adjust in future updates. If someone is smarter on me and can explain why it is doing this on this version I am always looking to understand how things work. I just wanted to have a simple post in case someone else has this issue as well with the latest update. Credit to krazykraz01, jchase222, carnivorebrah, Kaonashi for posting and pointing me in the right direction. My log file seems to have a different error then theirs but the fix is the same.

Woke up this morning to find my parity disk disabled. I ran a short SMART test with no errors. I ran an extended SMART test and got a read fail. I attached the SMART results what am I looking at. Got a replacement drive coming tomorrow but is this drive usable? Smart test.pdf

I appreciate the work around and you giving me some options. I’ll admit I’ve only been Unraid since the beginning of the year. There does seem to be a lot of work around for features people want/need, guess that is part of the fun when it comes Linux. I’ll have to get smart and start looking at an editing that config file. Thanks for the help, however, if there is a chance for feature like this to be added into the UI I would use it for sure.

Yes the problem with this method is that your are using your array, either preferably your cache drive or your main drives. If I am having problems with my system that could render my log files useless (let’s say my cache drive is failing). I don’t want to have to use Unraid to retrieve those log files. Same reason I do not use the main array to back up a copy of my app data or my flash drive.

Is this still the only work around to get the array status notifications to not send at 1220am? With the possibility of the settings reverting back….

I am familiar with using the flash drive to back up the log file in order to survive a shutdown. I am also familiar with syslog server in order to save the log file off the system. But I do not have another system that is on 24/7 to back the log file up to, and I don’t want to mess with the UNRAID flash saving to it constantly. What I would like to see is an option to use a unassigned drive to store log files on. I have plenty of small hard drives laying around that would be ideal for a back up. I currently use two unassigned drives in order to back up my app data and other important data. One is formatted as a NTFS and the other as a FAT32 (no real reason for the difference). If I need that data, I take the unassigned hard drive out of the system and I plug it into my desktop via a sata to USB adapter and pull the data off of it. I would love to hear from the experts, I am sure I am missing something, or over thinking it. Thanks for everything you guys do.

Following

I know this is old. Anyone ever figure this out? Same issue. I have the dynamix schedules plugin set for 7am but I get the health check every morning at 1220am.