Intermittent "Server closed connection" errors: Server error or unknown status code: 400 / frugalusenet

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
asandhu
Newbie
Newbie
Posts: 5
Joined: November 3rd, 2025, 2:28 pm

Intermittent "Server closed connection" errors: Server error or unknown status code: 400 / frugalusenet

Post by asandhu »

Running the latest version of sabnzbd via Docker I get intermittent "Server closed connection" errors after large files have been downloading normally for some time, wondering if anyone else has seen this.

A large file (>50GB) will download fine at line speed (99-100MB/s) but after an indeterminate amount of time download speed will crater, going anywhere from 0B/s to 20KB/s and the logs show constant "Server closed connection" errors. I can also see in the connections window in sab, connections constantly appearing and disappearing from the list as well as the SSL cipher appearing and reappearing (does this indicate an SSL issue?). This behaviour continues until I fully restart the sab docker container and then it continues as normal until the next time it decides to stop working.

I saw this before months ago and the issue seemed to go away, I didn't notice it again until now and I still don't know what's causing it. This actually seems to be very similar to another post on this forum (ID 27080, I can't post links.). I get the exact same side effects but a different error, I don't usually see timeouts, just server closed connections.

To add, I have 3 servers set up and I see the errors from all of them when the issue starts. I've confirmed the provider is not down or experiencing issues currently. I've tried with direct unpack disabled, pausing when post processing, and I've confirmed I'm not running into memory issues (11+GB available). From inside the sab docker container I get full speed on speedtests and can ping the internet with no issues while experiencing the problem.

EDIT: I managed to capture the logs when the issue started, for context this is immediately after an unpack finished and the queue was resumed. I've trimmed duplicate lines to adhere by post limits. This is a download with missing articles obviously but the issue remains. The download is still in my queue with the "162 MB missing articles" message and increasing extremely slowly, connections disappearing, errors in logs, etc.:

Code: Select all

2025-11-03 19:43:18,405::INFO::[downloader:616] 5@eunews.frugalusenet .com: Initiating connection
2025-11-03 19:43:18,407::INFO::[downloader:616] 18@eunews.frugalusenet .com: Initiating connection
2025-11-03 19:43:18,411::INFO::[downloader:616] 1@bonus.frugalusenet .com: Initiating connection
2025-11-03 19:43:18,416::DEBUG::[downloader:950] Thread 47@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,427::DEBUG::[downloader:950] Thread 21@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,438::DEBUG::[downloader:950] Thread 73@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,449::DEBUG::[downloader:950] Thread 48@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,460::DEBUG::[downloader:950] Thread 22@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,460::INFO::[newswrapper:452] 22@news.frugalusenet .com: Failed to close socket (error=[Errno 32] Broken pipe)
2025-11-03 19:43:18,461::DEBUG::[downloader:950] Thread 74@news.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,462::INFO::[newswrapper:452] 74@news.frugalusenet .com: Failed to close socket (error=[Errno 32] Broken pipe)
2025-11-03 19:43:18,462::DEBUG::[downloader:950] Thread 49@news.frugalusenet .com: Server error or unknown status code: 400
...
2025-11-03 19:43:18,963::INFO::[newswrapper:365] 18@eunews.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:18,988::DEBUG::[downloader:950] Thread 11@eunews.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:18,997::INFO::[newswrapper:365] 1@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:18,999::DEBUG::[downloader:950] Thread 24@eunews.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:19,047::INFO::[newswrapper:365] 5@eunews.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:19,419::INFO::[downloader:751] Connecting 18@eunews.frugalusenet .com finished
2025-11-03 19:43:19,484::INFO::[downloader:751] Connecting 1@bonus.frugalusenet .com finished
2025-11-03 19:43:19,574::INFO::[downloader:751] Connecting 5@eunews.frugalusenet .com finished
2025-11-03 19:43:19,788::DEBUG::[downloader:760] Thread 1@bonus.frugalusenet .com: Article ye0xGBwRWqlUeI75nRnlubCi@d1l1Z8Nqi8Hm.Zm5 missing (error=430)
2025-11-03 19:43:19,789::INFO::[nzbstuff:268] Article ye0xGBwRWqlUeI75nRnlubCi@d1l1Z8Nqi8Hm.Zm5 unavailable on all servers, discarding
2025-11-03 19:43:19,835::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article YnBdnCOiN9fsKJmbEVRCYbAH@bBwTkzBldUtp.JIR missing (error=430)
2025-11-03 19:43:20,058::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article nvLZmzADjiagi1wSPlmGK8JC@VkehALAxpHd2.Xf1 missing (error=430)
2025-11-03 19:43:20,246::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article JKuFlrGLPRHRwTHPjfiQifB9@Q2ek2xPmriaJ.2Fz missing (error=430)
2025-11-03 19:43:20,458::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article FPYLX14CZ2bh6d6moaMLa4qb@tDAVb3Yo5IUj.tjZ missing (error=430)
2025-11-03 19:43:20,665::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article 3fU5txJiJKtXb8OCtuNnYl1h@ueD6mdyR4RyB.vmJ missing (error=430)
2025-11-03 19:43:20,859::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article tpGLOnzqK55d5zEtmP75POJx@hfxe7KkpBgvb.yhF missing (error=430)
2025-11-03 19:43:21,088::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article Y9eBkkpklZDXpzH3dddAojBQ@N5g7TNYf2X2s.uUF missing (error=430)
2025-11-03 19:43:21,310::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article nJ1Pj3aZiiCWCPIwXJYIbCOB@Ro7Bj0pCfVC9.7GK missing (error=430)
2025-11-03 19:43:21,480::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article hDkX0GLZdstPJ0oqrYy2j9vQ@jF6T6f4TbDks.JCp missing (error=430)
2025-11-03 19:43:21,735::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article catHzK1Mb0Zk5pwQfhyAPGUJ@QLldOxf1HnaA.9DW missing (error=430)
2025-11-03 19:43:21,893::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article 0jLdmWc09wEgYMWdSlpN1kGE@do6gnv69TWoj.8op missing (error=430)
2025-11-03 19:43:22,161::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article yoU2RG7MKj1voDuj27o8trQy@T5mLUIFh10yW.adO missing (error=430)
2025-11-03 19:43:22,285::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article Um9ETnjSU9S8kLB2dXHe0kNC@mlTUBQo8BuiM.3vG missing (error=430)
2025-11-03 19:43:22,605::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article Cy2V2jIuUQ6iYWtflwjYVIcI@O5D9MZ2mh5nX.6Et missing (error=430)
2025-11-03 19:43:22,697::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article dbZmwtzFvafZrCRfvrjT1jIb@Gr6KjCb9QmV2.abR missing (error=430)
2025-11-03 19:43:23,097::DEBUG::[downloader:760] Thread 18@eunews.frugalusenet .com: Article XcqEYDmT50Eej37bFZnhOr0V@gNg43eVpp3wG.ey0 missing (error=430)
2025-11-03 19:43:23,120::DEBUG::[downloader:760] Thread 5@eunews.frugalusenet .com: Article aUp7LXqWmr0XOe4iQpncXSKD@fBGti3vK7Yui.MMe missing (error=430)
2025-11-03 19:43:23,224::DEBUG::[downloader:950] Thread 28@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,235::DEBUG::[downloader:950] Thread 3@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,246::DEBUG::[downloader:950] Thread 41@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,256::DEBUG::[downloader:950] Thread 16@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,267::DEBUG::[downloader:950] Thread 29@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,278::DEBUG::[downloader:950] Thread 42@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,289::DEBUG::[downloader:950] Thread 4@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,300::DEBUG::[downloader:950] Thread 17@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,310::DEBUG::[downloader:950] Thread 30@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,321::DEBUG::[downloader:950] Thread 43@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,332::DEBUG::[downloader:950] Thread 5@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,343::DEBUG::[downloader:950] Thread 18@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,354::DEBUG::[downloader:950] Thread 31@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,365::DEBUG::[downloader:950] Thread 44@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,520::DEBUG::[downloader:760] Thread 1@bonus.frugalusenet .com: Article aUp7LXqWmr0XOe4iQpncXSKD@fBGti3vK7Yui.MMe missing (error=430)
2025-11-03 19:43:23,520::INFO::[nzbstuff:268] Article aUp7LXqWmr0XOe4iQpncXSKD@fBGti3vK7Yui.MMe unavailable on all servers, discarding
2025-11-03 19:43:23,523::INFO::[downloader:616] 47@news.frugalusenet .com: Initiating connection
2025-11-03 19:43:23,524::INFO::[downloader:616] 21@news.frugalusenet .com: Initiating connection
2025-11-03 19:43:23,524::INFO::[downloader:616] 73@news.frugalusenet .com: Initiating connection
...
2025-11-03 19:43:23,719::INFO::[newswrapper:365] 22@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,723::INFO::[newswrapper:365] 75@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,724::INFO::[newswrapper:365] 49@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,726::INFO::[newswrapper:365] 76@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
...
2025-11-03 19:43:23,777::DEBUG::[downloader:950] Thread 6@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,781::INFO::[newswrapper:365] 62@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,781::INFO::[newswrapper:365] 43@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,783::INFO::[newswrapper:365] 40@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
...
2025-11-03 19:43:23,811::DEBUG::[downloader:950] Thread 32@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,824::DEBUG::[downloader:950] Thread 45@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,835::DEBUG::[downloader:950] Thread 7@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,846::DEBUG::[downloader:950] Thread 20@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,857::DEBUG::[downloader:950] Thread 33@bonus.frugalusenet .com: Server error or unknown status code: 400
2025-11-03 19:43:23,859::INFO::[newswrapper:365] 19@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,876::INFO::[newswrapper:365] 46@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,884::INFO::[newswrapper:365] 71@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,884::INFO::[newswrapper:365] 45@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,904::INFO::[newswrapper:365] 20@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,916::INFO::[newswrapper:365] 72@news.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:23,966::INFO::[downloader:751] Connecting 22@news.frugalusenet .com finished
2025-11-03 19:43:23,967::INFO::[downloader:751] Connecting 75@news.frugalusenet .com finished
2025-11-03 19:43:23,968::INFO::[downloader:751] Connecting 49@news.frugalusenet .com finished
2025-11-03 19:43:23,969::INFO::[downloader:751] Connecting 76@news.frugalusenet .com finished
2025-11-03 19:43:23,969::INFO::[downloader:751] Connecting 48@news.frugalusenet .com finished
2025-11-03 19:43:23,969::INFO::[downloader:751] Connecting 28@news.frugalusenet .com finished
2025-11-03 19:43:23,970::INFO::[downloader:751] Connecting 57@news.frugalusenet .com finished
2025-11-03 19:43:23,971::INFO::[downloader:751] Connecting 24@news.frugalusenet .com finished
2025-11-03 19:43:23,972::INFO::[downloader:751] Connecting 53@news.frugalusenet .com finished
2025-11-03 19:43:23,972::INFO::[downloader:751] Connecting 79@news.frugalusenet .com finished
2025-11-03 19:43:23,973::INFO::[downloader:751] Connecting 32@news.frugalusenet .com finished
2025-11-03 19:43:23,973::INFO::[downloader:751] Connecting 64@news.frugalusenet .com finished
2025-11-03 19:43:23,973::INFO::[downloader:751] Connecting 56@news.frugalusenet .com finished
2025-11-03 19:43:23,974::INFO::[downloader:751] Connecting 8@news.frugalusenet .com finished
2025-11-03 19:43:23,976::INFO::[downloader:751] Connecting 51@news.frugalusenet .com finished
2025-11-03 19:43:23,976::INFO::[downloader:751] Connecting 52@news.frugalusenet .com finished
2025-11-03 19:43:23,976::INFO::[downloader:751] Connecting 78@news.frugalusenet .com finished
2025-11-03 19:43:23,977::INFO::[downloader:751] Connecting 4@news.frugalusenet .com finished
2025-11-03 19:43:23,977::INFO::[downloader:751] Connecting 27@news.frugalusenet .com finished
...
2025-11-03 19:43:24,066::DEBUG::[downloader:760] Thread 1@bonus.frugalusenet .com: Article XcqEYDmT50Eej37bFZnhOr0V@gNg43eVpp3wG.ey0 missing (error=430)
2025-11-03 19:43:24,066::INFO::[nzbstuff:268] Article XcqEYDmT50Eej37bFZnhOr0V@gNg43eVpp3wG.ey0 unavailable on all servers, discarding
2025-11-03 19:43:24,077::INFO::[downloader:751] Connecting 46@news.frugalusenet .com finished
2025-11-03 19:43:24,087::INFO::[downloader:751] Connecting 45@news.frugalusenet .com finished
2025-11-03 19:43:24,093::DEBUG::[downloader:950] Thread 56@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,104::INFO::[downloader:751] Connecting 71@news.frugalusenet .com finished
2025-11-03 19:43:24,106::DEBUG::[downloader:950] Thread 32@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,120::DEBUG::[downloader:950] Thread 57@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,131::DEBUG::[downloader:950] Thread 55@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,142::DEBUG::[downloader:950] Thread 61@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,153::INFO::[downloader:751] Connecting 20@news.frugalusenet .com finished
2025-11-03 19:43:24,156::INFO::[downloader:751] Connecting 72@news.frugalusenet .com finished
2025-11-03 19:43:24,156::DEBUG::[downloader:950] Thread 79@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,168::DEBUG::[downloader:950] Thread 59@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,178::DEBUG::[downloader:950] Thread 2@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,189::DEBUG::[downloader:950] Thread 36@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,205::DEBUG::[downloader:950] Thread 22@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,216::DEBUG::[downloader:950] Thread 65@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,231::DEBUG::[downloader:950] Thread 75@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,242::DEBUG::[downloader:950] Thread 64@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,253::DEBUG::[downloader:950] Thread 62@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,264::DEBUG::[downloader:950] Thread 35@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,282::DEBUG::[downloader:950] Thread 52@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,293::DEBUG::[downloader:950] Thread 27@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,305::DEBUG::[downloader:950] Thread 8@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,315::DEBUG::[downloader:950] Thread 39@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,335::INFO::[newswrapper:365] 14@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,338::DEBUG::[downloader:950] Thread 73@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,340::INFO::[newswrapper:365] 2@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,348::INFO::[newswrapper:365] 39@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,349::DEBUG::[downloader:950] Thread 80@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,350::INFO::[newswrapper:365] 15@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,359::INFO::[newswrapper:365] 40@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,360::INFO::[newswrapper:365] 27@bonus.frugalusenet .com: Connected using TLSv1.2 (ECDHE-RSA-AES128-GCM-SHA256)
2025-11-03 19:43:24,361::DEBUG::[downloader:950] Thread 40@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,373::DEBUG::[downloader:950] Thread 41@news.frugalusenet .com: Server closed connection
2025-11-03 19:43:24,384::DEBUG::[downloader:950] Thread 60@news.frugalusenet .com: Server closed connection
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Intermittent "Server closed connection" errors.

Post by sander »

> bonus.frugalusenet .com: Server error or unknown status code: 400

I would start by disabling bonus.frugalusenet .com, and see if that helps.

You're the same person as on Reddit, right:

Lower number of connections to 10 per server, and try again.
Top
asandhu
Newbie
Newbie
Posts: 5
Joined: November 3rd, 2025, 2:28 pm

Re: Intermittent "Server closed connection" errors.

Post by asandhu »

> I would start by disabling bonus.frugalusenet .com, and see if that helps.

This error appears for my main servers too, news.frugalusenet .com at the top of the log.

> You're the same person as on Reddit, right

Yes.

> Lower number of connections to 10 per server, and try again.

Trying now.
Top
asandhu
Newbie
Newbie
Posts: 5
Joined: November 3rd, 2025, 2:28 pm

Re: Intermittent "Server closed connection" errors.

Post by asandhu »

Reduced to 10 connections, obviously downloads were slower (~15MB/s) and it did seem to last longer but the same issue did eventually come up again. Disabling bonus server also had no impact.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Intermittent "Server closed connection" errors.

Post by sander »

> Running the latest version of sabnzbd via Docker

What if you run SABnzbd on a PC/Mac without docker?
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: Intermittent "Server closed connection" errors.

Post by safihre »

This is a server problem, not a user problem.
"Server error or unknown status code: 400"

This error code indicates: 400 Service temporarily unavailable

Contact Frugal.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Intermittent "Server closed connection" errors.

Post by sander »

safihre wrote: ↑November 4th, 2025, 4:00 am This is a server problem, not a user problem.
"Server error or unknown status code: 400"

This error code indicates: 400 Service temporarily unavailable

Contact Frugal.
From https://datatracker.ietf.org/doc/html/rfc3977

Code: Select all

   If the server has to terminate the connection for some reason, it
   MUST give a 400 response code to the next command and then
   immediately close the connection.  Following a 400 response, clients
   SHOULD NOT simply reconnect immediately and retry the same actions.
   Rather, a client SHOULD either use an exponentially increasing delay
   between retries (e.g., double the waiting time after each 400
   response) or present any associated text to the user for them to
   decide whether and when to retry.

From https://github.com/sabnzbd/sabnzbd/blob ... nloader.py

Code: Select all

# Timeout penalty in minutes for each cause
_PENALTY_UNKNOWN = 3  # Unknown cause
_PENALTY_502 = 5  # Unknown 502
_PENALTY_TIMEOUT = 10  # Server doesn't give an answer (multiple times)
_PENALTY_SHARE = 10  # Account sharing detected
_PENALTY_TOOMANY = 10  # Too many connections
_PENALTY_PERM = 10  # Permanent error, like bad username/password
_PENALTY_SHORT = 1  # Minimal penalty when no_penalties is set
_PENALTY_VERYSHORT = 0.1  # Error 400 without cause clues
So SAB only does a 0.1 minute (=6 second) timeout if it gets a "400"?

Would it be better if SAB did a higher timeout, for example 5 minutes? And log that in a better way?
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: Intermittent "Server closed connection" errors.

Post by safihre »

No. That's when there's a Cause clue.
Otherwise it does a wait as long as the timeout set by the user. So usually 60.seconds.
At least, that's what it should do.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
asandhu
Newbie
Newbie
Posts: 5
Joined: November 3rd, 2025, 2:28 pm

Re: Intermittent "Server closed connection" errors: Server error or unknown status code: 400

Post by asandhu »

> What if you run SABnzbd on a PC/Mac without docker?

Currently testing on a Windows machine, will let you know if it ends up replicating the issue. So far it's working. The other post I mentioned in the OP also had this issue in Docker, could it be an issue specific to the Docker image?

> Contact Frugal.

I've contacted them as I did the last time this happened, they said there is nothing on their end that would cause this behaviour. They did note that "normally you'd be using TLSv1.3" instead of 1.2 but I told them that as per the sab wiki I have 'AES128' entered for the cipher for each server which is why it's TLSv1.2. They said I should try clearing the cipher and letting it auto-negotiate to see if that solves it. They also suggested running without SSL enabled to see if that changes anything.


To add, I replicated this again today (but it did take longer to start throwing errors) I'm not sure if this series of events is related to the issue but it's happened in this order enough times for me to note it:

1. Queue full of large (>50GB) downloads.
2. First download completes after ~20 minutes.
3. Post process extracts the file (queue is paused, but for some reason the next download in queue shows ~3GB already downloaded?)
4. Once PP finishes and queue resumes, exact same log messages appear (400, broken pipe, etc.) and then I get closed connection errors forever until restart.

Whether the PP/queue resume is related or not I'm not sure but just pointing that out, I'm pretty sure this has also happened in the middle of a large download too so it's not always on resume as far as I remember.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Intermittent "Server closed connection" errors: Server error or unknown status code: 400

Post by sander »

As Safihre said: "400" is an active response from the frugal newsservers. No need to look at TLS.


If frugal can't help you, consider another newsserver. For example the Newshosting offer in the rop right corner of https://sabnzbd.org/
Top
asandhu
Newbie
Newbie
Posts: 5
Joined: November 3rd, 2025, 2:28 pm

Re: Intermittent "Server closed connection" errors: Server error or unknown status code: 400 / frugalusenet

Post by asandhu »

I cannot replicate this on my Windows machine, similar to the other poster. The Windows sab was restored from a backup of the docker one so all of the settings are the same including the AES128 cipher.

Clearing the cipher field is working so far on the docker instance but I haven't been testing for very long. I'm not sure how that indicates a provider problem if it works on Windows.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Intermittent "Server closed connection" errors: Server error or unknown status code: 400 / frugalusenet

Post by sander »

asandhu wrote: ↑November 4th, 2025, 4:15 pm but I haven't been testing for very long. I'm not sure how that indicates a provider problem if it works on Windows.
Indeed. So keep downloading on both systems to see how it behaves ...
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: Intermittent "Server closed connection" errors: Server error or unknown status code: 400 / frugalusenet

Post by safihre »

It's the provider that is sending us a specific error code that indicates they cannot process the request.
It's really really a provider problem.
Just tell them you are getting 400 errors.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
Post Reply

Return to “General Help”