Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
Thanks for pasting the exact error, losh. It's what pinned this down. Byparr opens a hidden screen for each check, and sometimes a start is cut short and leaves a small lock file in Byparr's temporary folder. Every later start then waits on that leftover file and gives up, so Byparr keeps reporting "starting". A plain restart keeps that folder, which is why it comes back up and then drops again. To clear it now, run this on the NAS: sudo sparkbox restart media byparr That rebuilds only the Byparr container, so your VPN and other apps are left alone. Then give it up to 15 minutes, because Byparr only runs its health check that often, and check: sudo docker ps --filter name=sb-byparr It should show (healthy). A permanent fix for this is not in a released version yet, so updating alone won't clear it for now. If it goes back to "starting" after the restart, reply here with that docker ps line.