tdunks

Did anyone manage to find a fix for the timeout issues with SWAG? I am still getting timeouts on large files or updates

I cant seem to get three containers to proxy through no matter what I do - these are my secondary sonarr/radarr containers and my plex container. On the dashboard all three state that they are unavailable and that SWAG can not reach them at http://[containername]:[port]. I have tried manually editing the configs to direct at the ip and port without any variables with no luck. I can't figure out what is going on here. All of the dockers except plex are on the dockerlocal network with plex having a host network. The normal sonarr and radarr containers work flawlessly.

I have three St8000as002 drives that have started having this issue too but this fix did not work. All three have the exact same number of read errors only during parity checks and always near the end. I am not sure if there is another issue at work as well.

Both letsencrypt and Organizr updated today and one of which broke the organizr auth included in letsencrypt (SWAG). It just gives a 500 error now on any page that has auth enabled. Does anyone have a potential fix?

Both letsencrypt and Organizr updated today and one of which broke the organizr auth included in letsencrypt (SWAG). It just gives a 500 error now on any page that has auth enabled. Does anyone have a potential fix?

I cant seem to get the performance to where I want it. sabnzbd will level out at 30-50MB/s where it should be able to easily push 90-105MB/s. Currently running on a gigabit connection and have followed everything under the sabnzbd high speed downloading guide. Both the incomplete and complete are on my cache which is 4x400gb SSD in BTRFS raid0. Not sure where else to go to try to raise the speed. I am able to get 80+MB/s on nzbget but much prefer sabnzbd.