heisenberg815

I figured out my problem, it had to do with the bad CIDR notation being in the sabnzbd.ini file. I don't think the updated LAN_NETWORK was making it into the local_ranges variable in the ini file for some reason. When I manually edited the ini file and put in the correct CIDR notation it worked fine. Hope that helps others if they are having similar issue.

Thank you, I corrected what I think you were referring to and restarted. I have pasted a new file with what I think is the correct CIDR notation and I am still getting the same error. The reason I had the LAN_NETWORK defined as I did was because my delugevpn docker works with the 192.168.0.1/24 notation even though it isn't correct. supervisord1.log

Having similar issue as others with not being able to connect to webui on my local network. I run the binhex-delugevpn container and have no issues connecting to the webui for that container. I added my tailscale network to the container's local network and tried connecting from a machine running tailscale and one not running tailscale but got the same "External internet access denied - https://sabnzbd.org/access-denied" message on both. Attaching requested files, appreciate your help. command execution file.txt supervisord.log

I have attached another log file showing another disk read error for disk 1. I also re-ran the extended SMART self-test for disk 1 so hopefully that provides more information. Could the cables and connections go bad without me being inside the case or touching the connections? My server has been running for years with no disk problems other than normal disk failure on occasion but maybe I should be proactively changing out cables? tower-diagnostics-20231029-0925.zip

Thanks for the response. I have disabled the autofan plugin so hopefully that will clean up the log. I am also re-running the extended self-test. I have disabled all my dockers and started backing up the disk using midnight commander to copy the data on that disk to a USB backup drive. I will re-post the log tomorrow and hopefully that will be enough time to give some clarity in the syslog.

Hi, I am running unraid version 6.12.2. Over the last few days I have started receiving notifications that errors have been found with my server. When I go to my fix common problems plug-in it says my disk 1 has read errors. I ran an extended self-test for the disk and attached the full diagnostics log here. Is disk 1 toast or can it be repaired? Should I just swap out the drive to be sure? Note that the drive that is failing is the exact same drive as my parity drive, installed at the exact same time so should I be worried about losing the parity drive too? Appreciate any guidance on what steps to take to protect and repair the system. Regards, Mike tower-diagnostics-20231028-0927.zip

Hi all, I am getting an error in Fix Common Problems plugin letting me know that my rootfs is almost full. I have followed the recommendations to attach my diagnostics log and to run the listing of what folders are taking up space in memory, the output of which I have attached as a text file as well. It seems to be pointing to Prowlarr but am not 100% sure and would appreciate your help diagnosing and fixing. Thanks in advance for any help provided. tower-diagnostics-20230326-0946.zip RAM folder list.txt