9 replies
tomspark wrote:
Good catch — you were exactly right. The changelog had frozen at 1.6.320 and wasnt showing the last several releases (321 through 329), even though your box was actually receiving them. That was a publishing bug on our end, nothing wrong with your box. Its fixed now — the release notes are live again, so after a refresh (or reopening the Updates screen) youll see everything up through 1.6.329, including some solid fixes like the OpenVPN media-install unblock and the Easy-WG login fix. Appreciate you flagging it!
TestedEcho wrote:
I still have the problem where my backups don’t encrypt. I suppose it’s something I only have encountered and you probably missed my last message in the post I started some time ago. Don’t really get it. It can see the key, but fails. When I ls the folder I can see a .tmp file where it seems to try to start to encrypt the file, but it never goes over 141000000 bytes, so 132MB? So, there is an unencrypted backup, and a partly encrypted tmp file, but I suppose it always fails. Is there a log I can help you with? Or is this enough?
tomspark wrote:
Thanks for the details — this is clearly separate from the releases issue. A backup stalling at 141MB with a .tmp file suggests something in the encryption pipeline. Logs would absolutely help us track this down. Can you share any console/system output or point us to the backup log location? We're flagging this with the team.
TestedEcho wrote:
Logs from what or where? Don’t know how your backup system works so
tomspark wrote:
Good question! For SparkBox backups, check docker logs sb-dashboard | grep -iE backup for errors, and ls -lah /opt/sparkbox/backups/ to see the .tmp file. Since your backup stalls at 141MB, we need to see: (1) encryption errors, (2) available disk space when it happens, (3) memory/CPU usage. SSH in and run those commands—the .tmp file size pattern will help us pinpoint whether it's a resource, crypto, or timeout issue.
TestedEcho wrote:
docker logs sb-dashboard | grep -iE backup [2026-07-05T02:34:54.589Z] [INFO] Backup encryption: dedicated key [2026-07-05T02:34:55.234Z] [INFO] [perms] migrated backup-schedule.json from 664 to 600 [backup-scheduler] Cron job started: 0 2 0 ~$ ls -lah /opt/sparkbox/backups/ total 8.7G drwxrwxr-x 2 ys admin 4.0K Jul 5 02:01 . drwxr-xr-x 13 ys 1000 4.0K Jul 4 21:54 .. -rw-rw-r-- 1 ys admin 535M Jun 2 22:50 sparkbox-backup-20260602224822.tar.gz.enc -rw-rw-r-- 1 ys admin 310M Jun 7 01:49 sparkbox-backup-20260607014846.tar.gz.enc -rw-rw-r-- 1 ys admin 483M Jun 11 07:55 sparkbox-backup-20260611075330.tar.gz.enc -rw-rw-r-- 1 ys admin 115M Jun 14 02:02 sparkbox-backup-20260614020023.tar.gz.enc.tmp.1.9e5abf21c92b -rw-rw-r-- 1 ys admin 88M Jun 16 23:33 sparkbox-backup-20260616233033.tar.gz.enc.tmp.1.7102b3fd0e31 -rw-rw-r-- 1 ys admin 106M Jun 17 21:54 sparkbox-backup-20260617215213.tar.gz.enc.tmp.1.4e5aaa4f339a -rw-rw-r-- 1 ys admin 521M Jun 18 03:05 sparkbox-backup-20260618030242.tar.gz.enc.tmp.1.68594c917ab5 -rw-rw-r-- 1 ys admin 130M Jun 20 11:17 sparkbox-backup-20260620111530.tar.gz.enc.tmp.1.d0b8ece98c63 -rw-rw-r-- 1 ys admin 136M Jun 21 02:02 sparkbox-backup-20260621020010.tar.gz.enc.tmp.1.0ff52f618d28 -rw-rw-r-- 1 ys admin 136M Jun 24 09:34 sparkbox-backup-20260624093243.tar.gz.enc.tmp.1.bad9569d4aa6 -rw-rw-r-- 1 ys admin 120M Jun 28 02:02 sparkbox-backup-20260628020010.tar.gz.enc.tmp.1.fea5b14bc456 -rw-rw-r-- 1 ys admin 136M Jul 4 20:00 sparkbox-backup-20260704195831.tar.gz.enc.tmp.1.81a06a24e781 -rw-rw-r-- 1 ys 1000 147M Jul 5 02:02 sparkbox-backup-20260705020012.tar.gz.enc.tmp.1.1f01bbd75602 -rw-rw-r-- 1 ys admin 601M Jun 14 02:01 sparkbox-full-20260614020023.tar.gz -rw-rw-r-- 1 ys admin 859M Jun 18 03:04 sparkbox-full-20260618030242.tar.gz -rw-rw-r-- 1 ys admin 855M Jun 20 11:17 sparkbox-full-20260620111530.tar.gz -rw-rw-r-- 1 ys admin 890M Jun 24 09:34 sparkbox-full-20260624093243.tar.gz -rw-rw-r-- 1 ys admin 901M Jun 28 02:01 sparkbox-full-20260628020010.tar.gz -rw-rw-r-- 1 ys admin 904M Jul 4 20:00 sparkbox-full-20260704195831.tar.gz -rw-rw-r-- 1 root root 903M Jul 5 02:01 sparkbox-full-20260705020012.tar.gz Changed my username with hashes. I deleted some backups to make sure there is enough space, but there has never been less space than 7-8GB disk space I’m using max 6GB of 16gb ram Only tried backups when cpu was idle No idea where to look for encryption errors
tomspark wrote:
That's plenty — you've given us exactly what we needed. The folder listing tells the story: since mid-June every backup builds the full file fine, but the encryption step dies partway through and leaves those .tmp leftovers behind. And you've already ruled out space, memory and CPU, so this is on our side, not yours. No more commands needed — we're digging into the backup code now and I'll post here when a fix ships. Your data is safe in the meantime; the plain backup files are complete.
Chris wrote:
Coming back to this because that follow-up never came, and three weeks of silence isn't good enough. Being straight with you: no fix has shipped for the encryption stall. I went through the backup code myself before writing this, and nothing has changed in it since you sent that listing — so I'm not going to tell you to update and hope. I've written it up properly, with your folder output, so Tom has the detail. One thing worth knowing: your last complete .enc archive is the 11 June one. Everything since is a .tmp, so treat mid-June as your real restore point. — Chris