have not been able to connect to page even tho its scanning 26-10-04T05:16:04.859343270Z 2026-10-04 01:16:04,772::INFO::[notifier:169] Sending notification: Error - Loading /config/admin/postproc2.sab failed (type=error, jobcat=None) 2026-10-04T05:16:04.859436375Z 2026-10-04 01:16:04,771::ERROR::[filesystem:1286] Loading /config/admin/postproc2.sab failed 2026-10-04T05:16:04.859441507Z 2026-10-04 01:16:04,774::INFO::[filesystem:1287] Traceback: 2026-10-04T05:16:04.859443889Z Traceback (most recent call last): 2026-10-04T05:16:04.859445905Z File "/app/sabnzbd/sabnzbd/filesystem.py", line 1276, in loaddata 2026-10-04T05:16:04.859479995Z data = RestrictedUnpickler(datafile, encoding=sabnzbd.encoding.CODEPAGE).load() 2026-10-04T05:16:04.859483202Z EOFError: Ran out of input 2026-10-04T05:16:04.859485676Z 2026-10-04 01:16:04,782::INFO::[scheduler:191] Scheduling RSS interval task every 60 min (delay=54) 2026-10-04T05:16:04.859487876Z 2026-10-04 01:16:04,787::INFO::[scheduler:200] Scheduling version check in 10 minutes and daily at 16:6 2026-10-04T05:16:04.859490167Z 2026-10-04 01:16:04,788::INFO::[scheduler:215] Setting schedule for midnight auto history-purge 2026-10-04T05:16:04.859492183Z 2026-10-04 01:16:04,788::INFO::[scheduler:224] Setting schedule for midnight BPS reset 2026-10-04T05:16:04.859494016Z 2026-10-04 01:16:04,788::INFO::[scheduler:233] Setting schedule for midnight server expiration check
21 replies
Chris wrote:
Sorry you're unable to reach SABnzbd. The log you shared shows an error reading SABnzbd's post-processing settings, but that alone doesn't explain why its page won't open. Could you share your SparkBox version and platform (NAS, Linux, Windows with WSL, or Docker Desktop), and what the browser shows when you open the SABnzbd tile—connection refused, a timeout, or an SABnzbd error page? Please don't delete or reset its configuration.
wildwill wrote:
Thanks , currently running wsl on windows version 1.6.856 the page is errsocketnotconnected
Chris wrote:
Thanks—that confirms SparkBox 1.6.856 on WSL. ERRSOCKETNOTCONNECTED means the browser connection did not complete, but the earlier SABnzbd settings-file error does not by itself explain that. As one check, can you tell me whether Docker is Docker Desktop or Docker Engine installed inside WSL, and whether the SABnzbd tile fails only in a Windows browser or also from a browser inside WSL? Please don't reset or delete SABnzbd configuration.
wildwill wrote:
docker engine inside wsl on dash it just been stuck on starting 1-2 mins Sab does not open from anywhere.
wildwill wrote:
also getting localhost didn’t send any data. ERREMPTYRESPONSE the page is switching from one to the other
Chris wrote:
Thanks, that narrows it down: you’re using Docker Engine inside WSL (not Docker Desktop), and the dashboard shows SABnzbd stuck starting while its page won’t open. The post-processing settings-file error you shared doesn’t explain why the container isn’t starting, so please don’t reset its configuration. From the same WSL distro where Docker Engine runs, please run this read-only check: docker ps -a --format 'table {{.Names}}\t{{.Status}}'. It will list container names and states; share only the SABnzbd row, or tell me if no SABnzbd row appears. Stop there, and please don’t post full logs or configuration.
wildwill wrote:
sb-sabnzbd Up 2 minutes (health: starting).
Chris wrote:
That localhost error confirms the page is not returning a response, but it still doesn't tell us whether SABnzbd exited or is restarting. You’re on Docker Engine inside WSL with SparkBox 1.6.856, so please run the read-only check I mentioned above from that same WSL distro and share only the sb-sabnzbd row (or say if there is no such row); then stop there. Please don't reset or delete its configuration. The earlier post-processing settings error may be separate from the page-access problem.
Chris wrote:
Thanks, that row helps. SABnzbd is running, but it started only two minutes before you checked and has not finished starting yet, which is why the page gives an empty response or no connection at all. The postproc2.sab error in your first post is not what's blocking it. I started the same SABnzbd version with that exact file empty, and it opened its page normally a few seconds later; it just begins with an empty post-processing list. So please don't delete anything in its folder. What decides this is how far SABnzbd gets after that point in its start-up. Wait until the row says it has been up for at least 4 minutes, then run this read-only line in the same WSL distro: sudo sparkbox logs sabnzbd 2&1 | grep -E 'ERROR|Traceback|Error|web-interface|Serving on' | tail -n 15 Paste what it prints. If any line shows the name of a download, replace the name with X before posting. If it prints nothing at all, tell me that too, and tell me whether the status still says "Up" with a small number of minutes, because that would mean it keeps restarting.
wildwill wrote:
its been on 1-2 mins for awhile now page is still down rest of the apps in the list were up at least 35 mins while sab still sits at 2 mins as it still is on dash as of now only adding info befor i run out reponses for the day
wildwill wrote:
no response
Chris wrote:
I'm sorry—I gave you an unverified SparkBox log command, and I shouldn't have asked you to run it. The short uptime you saw could mean SABnzbd is restarting, but the settings-file error by itself doesn't explain the page outage. From the same WSL distro where Docker Engine runs, please repeat the read-only check you already used: docker ps -a --format 'table {{.Names}}\t{{.Status}}'. Share only the sb-sabnzbd row (or say if it is missing), then stop there. I've corrected what I know so I don't give that unverified log command to the next person.
wildwill wrote:
sb-sabnzbd Up 4 minutes (unhealthy)
Chris wrote:
Thanks—that confirms SABnzbd is still running but Docker now marks it unhealthy, so my earlier guess that it only needed more startup time was wrong. I’m sorry. The empty post-processing settings-file error may be separate; I can’t verify its connection to this health failure yet. Please run this read-only check in the same WSL distro where Docker Engine runs: docker inspect --format '{{json .State.Health}}' sb-sabnzbd. Share only the result, and stop there; it should show the health-check status and recent check output. Don’t reset or delete SABnzbd files. I’ve corrected what I know so I don’t repeat the unsupported startup-time explanation for someone else.
wildwill wrote:
{"Status":"starting","FailingStreak":0,"Log":[{"Start":"2026-10-04T02:28:07.035646145-04:00","End":"2026-10-04T02:28:07.231087265-04:00","ExitCode":1,"Output":""},{"Start":"2026-10-04T02:28:12.232757885-04:00","End":"2026-10-04T02:28:12.315407045-04:00","ExitCode":1,"Output":""},{"Start":"2026-10-04T02:28:17.316460805-04:00","End":"2026-10-04T02:28:17.412217565-04:00","ExitCode":1,"Output":""},{"Start":"2026-10-04T02:28:22.413704315-04:00","End":"2026-10-04T02:28:22.577789345-04:00","ExitCode":1,"Output":""},{"Start":"2026-10-04T02:28:27.578795765-04:00","End":"2026-10-04T02:28:27.746944385-04:00","ExitCode":1,"Output":""}]}
Chris wrote:
I'm sorry—I was wrong to say that waiting longer would explain the outage, and earlier I gave you an unverified SparkBox log command. The check you just ran shows SABnzbd's health check repeatedly exits with code 1 and no diagnostic output; that confirms the health probes are failing, but it doesn't explain why the page won't load. The post-processing-file error may be separate. One read-only next check, in that same WSL distro: docker logs --tail 40 sb-sabnzbd. Please share only relevant startup/error lines, replacing any download names, addresses, passwords, or keys with [redacted]; if there are no relevant errors, just say so. Stop there, and don't reset or delete any files. I've corrected what I know so I don't repeat the unsupported startup-time explanation or unverified command.
wildwill wrote:
File "/app/sabnzbd/sabnzbd/filesystem.py", line 1276, in loaddata data = RestrictedUnpickler(datafile, encoding=sabnzbd.encoding.CODEPAGE).load() EOFError: Ran out of input Traceback (most recent call last): File "/app/sabnzbd/SABnzbd.py", line 1665, in <module main() ~~~~^^ File "/app/sabnzbd/SABnzbd.py", line 1160, in main sabnzbd.initialize(pause, cleanup, repair=repair) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/sabnzbd/sabnzbd/decorators.py", line 53, in callfunc return func(args, kw) File "/app/sabnzbd/sabnzbd/init.py", line 310, in initialize sabnzbd.NzbQueue.readqueue(repair) ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "/app/sabnzbd/sabnzbd/nzbqueue.py", line 116, in readqueue self.add(nzo, save=False, quiet=True) ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/app/sabnzbd/sabnzbd/decorators.py", line 68, in callfunc return func(params, kparams) File "/app/sabnzbd/sabnzbd/nzbqueue.py", line 332, in add self.endjob(nzo) ~~~~~~~~~~~~^^^^^ File "/app/sabnzbd/sabnzbd/decorators.py", line 68, in callfunc return func(params, kparams) File "/app/sabnzbd/sabnzbd/nzbqueue.py", line 787, in endjob self.sendback(nzo) ~~~~~~~~~~~~~~^^^^^ File "/app/sabnzbd/sabnzbd/decorators.py", line 68, in callfunc return func(params, kparams) File "/app/sabnzbd/sabnzbd/nzbqueue.py", line 226, in sendback oldposition = self.nzolist.index(oldnzo) ValueError: list.index(x): x not in list
Chris wrote:
Thanks for posting the traceback, and sorry this has taken so many rounds of checks. This shows SABnzbd is failing while it restores its queue; the earlier empty post-processing settings-file error is separate evidence, and I can't verify that it caused this failure. Please don't delete or reset the queue or configuration. For now, just let me know whether sb-sabnzbd is still restarting/unhealthy and the page is still unavailable; no more log dumps are needed yet. I've recorded this specific startup failure so it can be investigated without guessing at a repair.
wildwill wrote:
yes its still unhealthy
Chris wrote:
Thanks for confirming this is still unresolved. The traceback you already shared shows SABnzbd failing during queue restoration, but it does not establish a safe repair that would preserve its queue and configuration. Please leave those files untouched for now; I've kept this specific failure open rather than treating the health-check errors as the cause. No more logs are needed from you right now.
Chris wrote:
Good news: we found it, and SparkBox 1.6.859 (out now) fixes it. What happened. SABnzbd's "Check before download" setting is on, and the box stopped (most likely Windows shutting SparkBox down) right after SABnzbd had finished checking one of your downloads, before it started the real download. SABnzbd has a bug where a download left in that exact spot makes it crash every time it starts, while it reloads its queue, so its page never opens and Docker keeps calling it unhealthy. Your traceback is exactly that. We reproduced it here, and 1.6.859 works around it: SABnzbd starts normally and that download simply carries on, with nothing deleted. One step. Update SparkBox: Settings → Updates → Update SparkBox in the dashboard, or sudo sparkbox upgrade in your SparkBox terminal. The update restarts SABnzbd by itself; give it about 3 minutes, then open SABnzbd's page again. If it still says unhealthy after that, tell me and I'll take it from there. (If your box is on the free plan, the update reaches it in about a week; Legend and Backer boxes have it now.) You didn't do anything wrong, and keep leaving the queue and config files alone. They're fine.