Search found 3 matches
- July 1st, 2025, 8:03 pm
- Forum: General Help
- Topic: Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
- Replies: 4
- Views: 6201
Re: Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
For anyone that finds this post in the future here is how I fixed this using the suggestions above. Because I am running the docker container in kubernetes, sharing a local disk between multiple pods such as sabnzbd and sonarr/radarr is difficult. While there are RWX pods in Longhorn and other such ...
- June 30th, 2025, 3:35 pm
- Forum: General Help
- Topic: Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
- Replies: 4
- Views: 6201
Re: Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
Hi Brahiewahiewa, Thanks for the reply. I will for sure look into my NFS - I am using TrueNAS Scale so would expect it to be configured reasonably out of the box. The reason I have avoided putting the complete on a local disk is my Sonarr / Radarr and other such media apps are not able to see said l...
- June 29th, 2025, 8:07 pm
- Forum: General Help
- Topic: Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
- Replies: 4
- Views: 6201
Lost Connection to SABnzbd - Unable to Determine the Cause [k3s Kubernetes, NFS]
I am having an issue where my sabnzbd frequently shows this disconnect message on the web interface. This also lines up with the app not taking API requests. It can last for 15 - 90 seconds. No rhyme or reason that I can see. I usually run this workload in a k3s Kubernetes cluster. The container has...