I haven't been able to login to the dashboard for some days, thought it needed an update so waited a bit. But it keeps on being a problem, even after changing the password, reseting the dashboard, sparkbox doctor and status show nothing wrong, restarting was and docker, paused tdarr and seerr (because they were hogging the cpu) in portainer but that didn't help, now portainer is failing too, but some others aren't. so, the problem, can access the dashboard, but it fails the login. Under here is what shows up in the dashboard logs while I load the page and try to login: Error: EACCES: permission denied, open '/app/state/sessions/MDmnttc6WqjkX22u9XQ-3nSezbsjyiXe.json.tmp.1.8a71a773' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) [alerts] sb-adguard was OOM-killed [alerts] could not record OOM kill: EACCES: permission denied, open '/app/state/oom-kills.json.tmp.1.2aa8b7da' [alerts] Check failed: EACCES: permission denied, open '/app/state/alerts.json.tmp.1.946b5ce0' Error: EACCES: permission denied, open '/app/state/sessions/TkG6bUmMKiYt8WPQRlWhwzSJdfZbhb4.json.tmp.1.2eb0ad62' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/FMlQ7uIXnKbMBcPPRipTIRL0Pbbv5wU.json.tmp.1.3ffcf8f7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/d-zrRyAxTsIRRMaTP33-soe9ff2ZYApy.json.tmp.1.691108ae' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/YXSIU--QbE2jbXVuXvcClq5uloa2h64N.json.tmp.1.8da0caac' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/-atUkeKX8GSt9HEdKG6vBbty92fWIg2c.json.tmp.1.66c73126' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) [alerts] sb-adguard was OOM-killed [alerts] could not record OOM kill: EACCES: permission denied, open '/app/state/oom-kills.json.tmp.1.0855a93c' [alerts] Check failed: EACCES: permission denied, open '/app/state/alerts.json.tmp.1.0eb9011d' Error: EACCES: permission denied, open '/app/state/sessions/AbzyPH8VmyY1XZxh4Z87vdNGpkGIgcS8.json.tmp.1.257271ae' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/dik-hQEQ4Kto6or5OJSAYCIzNV4kkr2.json.tmp.1.ceb211c1' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/6jTCtbBidsmHzyl-Gii8QN6WMYNSre33.json.tmp.1.c9e16154' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/yjieswOLU4vItqZa2TcOJ75TY9o33.json.tmp.1.1a9aad04' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/OrmjJvjDUhe21iejHvwbWFqcpR4AYbU.json.tmp.1.1b37aec9' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/GThigCVjpRW1AAnMv3anHAcOSBx7p5KP.json.tmp.1.70ea9cd7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/DjhCCsX8m09oZHTUMiaxq7ewrv8oA7I.json.tmp.1.e1bb6d7f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/iKZp-kNqoQx9XWxEm6lsFoIPNPGhzr7y.json.tmp.1.62a547a8' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/MQynvAQ1gehjOOT2VlXsofRV21a76PlP.json.tmp.1.3173a6cf' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/mkTEERokBk6noftK7Vn405Iq1d8rEGc0.json.tmp.1.3f155ea9' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/BakZY2BUd2nukaOMIkOhrqkpiVywMT.json.tmp.1.d3a2b843' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ngW1TFg2fZ-XeXkL-QlBDbrDkY9n5GS.json.tmp.1.6ce6ae59' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/aYQFkAmKFuB05fuCsogyJqKqy3Fs2dfX.json.tmp.1.f5864f35' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/-F21IvK78z2ECwrifiM-RTjG-cSk1nB.json.tmp.1.74a2ffbb' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/o9A5m0wsx6eR5K99s-aMSyfMVUGZVhj.json.tmp.1.eda5ee57' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/KIyEtIejhxpdv8RHjZ9oc5yotUEt3xd.json.tmp.1.6f65f7fc' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/WR56Iy7Q0pNAZXgkP6M6Qz8kBk7yEms.json.tmp.1.4fd6f891' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ieAxF9blHIPfo26esLCV28oH5hNQvIC.json.tmp.1.fcad735f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/xR1k6GaVBhOi3ZuxDPwObRpyJOlPu3E9.json.tmp.1.80e055dd' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/YaMH7IuVivmjSqE9F-cN-K2JQrcZuMI5.json.tmp.1.32e25105' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/IqHQTAjGyiW7kbbHxVlqrerTo5mHmYUv.json.tmp.1.afaacfc5' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/hwkJkizjxEEVIyKLKzacTsOWMRgV3AO.json.tmp.1.2b81bfa0' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/giGSpsNoKJwOGMU2AD1HAsgm5x23HI2B.json.tmp.1.4710784b' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/EHYwJoP6GRuFCpXSvwZ8amHa-ZSR-M6.json.tmp.1.5d2959e8' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/RAD-ejJ77gL8G1sX8cng35f4wWFLWh.json.tmp.1.3ad9597c' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/gMkFiknTjlIxhp8OaEdI6JwY6i5p8B5.json.tmp.1.1e267c9c' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/THpBC66ArpV6KnjRyv8LTx27PqvNtic.json.tmp.1.fe641eaf' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/p4wdzhqLmx0I4h6dNcU-6mb67ittb8d4.json.tmp.1.6752742f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ZaFpD7riueJ4XEbogRwVzFVJp9gV10gg.json.tmp.1.0692e7b6' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/7nVaVJ0cL2uFPouSfO6oT0uTdC-j5Tk.json.tmp.1.ee6e37b2' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/3DRoflB9mv98EuP61hLYmk6Atmjdl6.json.tmp.1.4871eb81' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/iD2Mn9YlKYOZ1r1O4kqXg76M2lEkl7x3.json.tmp.1.15f8b18d' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/2M4-mfLYGsYxxd8Oil-SgbWIP-tDljq.json.tmp.1.ae6f0211' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/6ltYbPOlKDehpcwBppXc2uWxe1QuzjGl.json.tmp.1.75fe80e9' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/VbcjPKViZdsKWMvWHEm1GJksCK8xSMOv.json.tmp.1.53e7ebc7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/XA-MNfnuUtfQeicq0N2larDbuULWeNye.json.tmp.1.22e0f000' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/RMhRhmQcLVeIWHVaB00Zn-qsG44r5qRI.json.tmp.1.1e702884' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/t1ZT7Z3XHb2RmN3UN7-XQc4JpXOdyEUS.json.tmp.1.980a2113' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/iv79z8IGJ1flMmqM0i-IeAvNTWnl7YRx.json.tmp.1.99e2ce43' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/x2vqWHPXXEAt433ktnEhHSjwL7NL3rq.json.tmp.1.74bb1054' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/tqSFvY4LlrCocljisRh8H57nvLjGMOmv.json.tmp.1.3fcf83c2' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/k2sM04VDg4KIRhypJz3Qx1P5bm1kAU6v.json.tmp.1.33e13167' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ATQRom28lG8Bz7ccSb09dGKIdg51UgMb.json.tmp.1.f7122ae7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/zb-BwiOZM91vuYuiE1skLBawI508ko6.json.tmp.1.35f7b0c1' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/5W-IxhkAb0QrELp2JsLznntDecDflyB.json.tmp.1.93fb9900' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/aKJeMYkczqhw8WQa8oha1jTmbuyHU49O.json.tmp.1.deb9d1d0' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/-5IhbFAcn4-ud8LWv93WKh5tAjNG9CfD.json.tmp.1.36f027a6' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/OJjjNbvsJ6HzWwsflQuxO1cCJ1tr5zp9.json.tmp.1.21434cd1' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/OE-a-FD1RjVf37Z3IzdeLIAZ7RTCrdMm.json.tmp.1.40f8321e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/GfT7eAWFDQQ7Vc6xCLT9OcFpIGqS0aN.json.tmp.1.dd9b84f3' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/1cwbbYEvMiT5kH60la9iFE5l4b0G08hK.json.tmp.1.237cdac4' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/KAEthpC1l7hqFbYWP-Ok36MZNewcRAr.json.tmp.1.e008aa2a' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/lCwwhZU6vEQj48oF5WcNUdNICQTr8Mhs.json.tmp.1.650e9e72' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/wkAqk9Iy3K5Jk8Ei6LfVvwgYh8ImbB.json.tmp.1.27b1fe28' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/Veun51s9dzrc5nP0pfB0oyYNHLqWywKT.json.tmp.1.9772545f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/2mub0qNVMoZyN0u47VGv6zmbECxWYS.json.tmp.1.bb997ad5' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/Brn53VWV6ywAsmn4VhpXfNO5fevesrVR.json.tmp.1.d5302ef4' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/rjgT3UWTGPJufnmxBGxJpJ9E7KgnPwE.json.tmp.1.78703379' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/dJ4Q0itxr6SZ3pfVOIF0WSsjgRqZzPAu.json.tmp.1.7320e185' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/0P1RcsdkFko6okV6wYfJCAIz53kzYcix.json.tmp.1.28f287e7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ATFyOCx-XGCsPJhI-rnlqP6iMDEgVHb6.json.tmp.1.818e1e43' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/hkHqqE05FcdTq0B9Yb-bts3keu1WOt4F.json.tmp.1.88e4c934' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/hPKZQBUGOvvhGKMxU5vXZgjsVYFUXWp6.json.tmp.1.f1a7f596' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/a3B1LycN3SY1fwV4xG2Jd0qZdgB4aGC7.json.tmp.1.4d238dd6' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/97UDpkmAunPRfv5OQ1njQFyX7sRdU7w.json.tmp.1.2ee336dd' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/QstSfnRItHZWMW7LMNej3UQX5NQWCRr.json.tmp.1.e9e799f1' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/gMKgPXgn9EZgNI-ZQqOSJppMdY7yA7Q.json.tmp.1.a6aa5d8b' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/M-5QNTuqA1bLWPUbiiDwiAxwKqOXIoPC.json.tmp.1.b768d610' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/sh5CS1oIF6thezZ9Uyax5oeGnlWWN0.json.tmp.1.fb49bd6b' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/GLMC-P1xSCptu8IjPQsCToZryh0pdHT.json.tmp.1.813a7f0b' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/P6KPSkOOl6BgacCVVryFn7WEj4cKLflf.json.tmp.1.90711aff' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/QEwRSzsoJggnOiCVZQsiVMAfHW1Np.json.tmp.1.7b0e0f35' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/HxJcPJNgH-Z7dm2ZEfucfoTZykTV1d6m.json.tmp.1.faa14577' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/cGPsYEhzzEBnJb-KK0iGRfLkcoccb0iw.json.tmp.1.8eedcb8e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/QI0VPnUBPJqY0VVUNRZ8pEh-VWecpYmD.json.tmp.1.f06e5206' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/sHJLzFPvwGoa5Fe8-cGNH4bDDvEzn9w.json.tmp.1.48379437' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/L2w4NrmVMzLarob0gbQX3eooCaPBwx4.json.tmp.1.4dca6312' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/WgTb9i3MEPJIA8UxowS6DYy-FgZHyVg.json.tmp.1.4c0a788b' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/KA8pK2MzJ8QvEedcegpN-Z4oIr8rzuW.json.tmp.1.e44cc15d' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/dMJX32DMMTbqL6Pr3FRXV20eIx75pLaF.json.tmp.1.e5b3e98c' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/WWPgdBgX1ANDbNL4kZqvHSExbpJgPr3G.json.tmp.1.c462e6d4' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/-cdC3jU67kRWbZYKmT1pciABeQZIM2UT.json.tmp.1.8d9afa66' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/6HOh30tJjkATMKCFpAHlPgx9I6cVVQ3b.json.tmp.1.749493f7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/pWWkVUa7qsCx-B0UWqNwinUqzOttn0ea.json.tmp.1.9d9716bc' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/NSgnSthWCQFneks5L3PtLqFKImzLoi7.json.tmp.1.0b23060a' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ubKvWq9apLgKzttnlIW0DFeA-ftPHSDO.json.tmp.1.e447122c' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/QeVr7clPh3QMLub3Oao7iLyyJaKGOUM9.json.tmp.1.e6158449' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) [alerts] could not record OOM kill: EACCES: permission denied, open '/app/state/oom-kills.json.tmp.1.546ae530' [alerts] sb-adguard was OOM-killed [alerts] Check failed: EACCES: permission denied, open '/app/state/alerts.json.tmp.1.aee25a5a' Error: EACCES: permission denied, open '/app/state/sessions/PAtu5MISbdDIy-LoNofV7wpeidf8kqXk.json.tmp.1.f650ef9e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/Ex9xPC4S4gIqVPf0AxneEuo0WWth3BhQ.json.tmp.1.dfd0fb5e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/aYDyusyyEnKzEA8IpNQ3YPp6ieGkft6.json.tmp.1.0d6f682f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18)
37 replies
Chris wrote:
Hi TestedEcho — I can see exactly what's happening in those logs. Your dashboard container can't write session files because the state/sessions directory is owned by root when it needs to be owned by the app container user. This was a permissions issue in earlier installs that we fixed in v1.6.110. Here's the repair: sudo sparkbox update sudo sparkbox up The update brings in the fix, and sparkbox up runs the corrected permission setup on your dashboard. This is idempotent — if your sessions directory is already correct, it's a no-op. Try logging in after those two commands. Let me know if you hit any other permission errors after that.
TestedEcho wrote:
my version is SparkBox v1.6.695, but I tried again and it didn't work. now the page only shows an error, so no trying to login: Internal Server Error
Chris wrote:
Hi TestedEcho — I see the error escalated after the update. The permission fix from v1.6.695 should have worked, but something didn't apply cleanly. Let's repair the permissions directly and restart. Run these two commands: sudo chown -R 1000:1000 /opt/sparkbox/state/sessions sudo sparkbox restart dashboard Then try the dashboard in your browser again. Let me know if you're back in or if it's still showing the error.
TestedEcho wrote:
Thanks, it worked. Any idea how this changed? Cause it always worked great before
Chris wrote:
Happy to explain. That session directory is created and owned during the initial install. In earlier versions, if something went wrong during install setup or on manual updates, the permissions could get misaligned — the directory would end up owned by root instead of the app container user. What likely happened: an earlier install or update had a hiccup in that specific setup step, leaving the sessions directory root-owned. The permissions stayed that way until you updated to v1.6.695, which includes the fix that catches and corrects this issue automatically. The manual chown command we ran just sped things up by applying the correction immediately. You are all set now — the fix is in place.
TestedEcho wrote:
I have the impression a lot more of the permissions got screwed up by an update. This last one too again. Which folders do I have to give what permissions/ownership to let it all work again?
Chris wrote:
I apologize — this should not be happening repeatedly after updates, and I want to help you get this sorted properly. Let's start with a diagnostic that will show exactly which directories are owned incorrectly. Run this: sudo find /opt/sparkbox/state -type d \! -user 1000 -ls This will list every directory under /opt/sparkbox/state that is not owned by user 1000 (the app container user). Paste that output back. Once we see what's affected, the fix is straightforward — we'll chown only the directories that need it, targeted to your exact situation rather than guessing. The pattern of this happening after multiple updates suggests we need to find out what's actually breaking, and your output will help us identify that.
TestedEcho wrote:
it shows I thing about every folder and subfolder in there.
Chris wrote:
Thanks for running that — if every folder is listed, we have a bigger permission problem than just sessions. Let's take this step by step and fix it properly. First, let's repair all the state folder permissions at once: sudo chown -R 1000:1000 /opt/sparkbox/state sudo sparkbox restart core Then try logging into the dashboard again. If you're back in, the next thing is to figure out why this keeps happening after updates. The fix shipped in v1.6.110 was supposed to catch this automatically, but your box is on v1.6.695 and it's still happening. Can you run this and let me know what it shows? sudo sparkbox version Once we see that, I want to pull your most recent update log to understand what's breaking the permissions during the update process. This pattern (fix works once, then reoccurs after the next update) means something in the update sequence isn't preserving or re-applying the permissions correctly. That's not how it should work, and we need to track down what's different on your box.
Chris wrote:
Thanks—that confirms the issue: every folder under /opt/sparkbox/state is wrong-owned. This recurring pattern after each update means the automatic fix isn't catching it on your box. Let's repair it and then diagnose why it's breaking again: sudo chown -R 1000:1000 /opt/sparkbox/state sudo sparkbox restart core Try logging in once that's done. Once you're in, I need to see why this isn't sticking across updates. Run: sudo journalctl -u sparkbox-update -n 100 Paste the output back. It'll show whether the fix ran during the last update and whether it actually succeeded or silently failed.
TestedEcho wrote:
It says no entries
Chris wrote:
TestedEcho — thanks for running that journal check. The empty log output confirms the update process itself is not logging that step on your box, which matches exactly what we've now fixed. This recurring permission problem is what v1.6.708 (released 2026-09-16) was specifically built to address. The root cause: during earlier installs and updates, the setup step that prepares your session state directory only ran during the initial sparkbox up, not during updates or restarts. That left the permissions broken after every update. v1.6.708 moves that directory prep to run on every update and restart path, and it runs regardless. Here's what to do: sudo sparkbox update sudo sparkbox up sudo docker restart sb-dashboard Then try logging in. The permissions will be corrected as part of the update, and they'll stay correct after future updates too. No more manual chown needed after this. Let me know if you're back in the dashboard after that.
TestedEcho wrote:
It keeps on changing the opt/sparkbox/state folder to root Shows this after last restart after last update : SparkBox v1.6.714 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Environment: NAS (generic) [INFO] Starting SparkBox... [INFO] Active modules: backup core dashboard files media plex tailscale unpackerr [INFO] Prepared 19 module config dir(s) for PUID=root PGID=10
Chris wrote:
TestedEcho — sorry, I sent you the wrong broad chown -R .../state repair earlier. It can change ownership of app data that should not be changed. The dashboard is different: its container runs as UID 1000, while your log shows PUID=root (UID 0) for the other module config directories; SparkBox is supposed to keep only the dashboard state and sessions directories owned by 1000:1000. Please run this read-only check on the NAS host and paste only its two lines: sudo stat -c '%u:%g %a %n' /opt/sparkbox/state /opt/sparkbox/state/sessions Please do not run another chown yet. We have corrected what we know so future guidance does not send the blanket repair again.
TestedEcho wrote:
0:10 775 /opt/sparkbox/state 0:10 775 /opt/sparkbox/state/sessions
Chris wrote:
I’m sorry — I sent you the wrong broad ownership repair earlier, and it was not safe to apply to all of /opt/sparkbox/state. Your two lines show that the state directories are owned by UID 0 (root), group 10; mode 775 does not give the dashboard user UID 1000 write access unless it is in that group, which explains the EACCES errors. The PUID=root startup line describes the module configuration preparation and does not prove that every dashboard directory should be changed. Please try one normal dashboard login now and tell me the exact result (login succeeds, Internal Server Error, or an EACCES message); do not run another chown, reset, or reinstall yet. I’ve corrected what I know here so future guidance does not send you the blanket ownership repair again.
TestedEcho wrote:
Error: EACCES: permission denied, open '/app/state/sessions/EebUdTbuzhaE7WwbNJz5KpyPetKZq15L.json.tmp.1.5db85810' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/Nbysu9mXKgZ5ztOablrGE4CnyR1gWiX.json.tmp.1.a31e4aad' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/vMU33mANnjyXf6m8kSZEL5Y0g9d0GsPO.json.tmp.1.a4b114ee' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) [2026-09-20T20:55:28.568Z] [INFO] License cache refreshed: licensed (Pro) Error: EACCES: permission denied, open '/app/state/sessions/OEVKsGuVzT115w0IQvE8SqyGXCjRHp3z.json.tmp.1.5a7a8c58' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/HCTHQGu7KcPhUKJl1v-U8EkDmCqonxRH.json.tmp.1.ab5e159e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/HMhpM65DVJ2rgEmZXVaVJanMLt32Vju.json.tmp.1.11ead4dd' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/ZJi1yQgF3yjdhmJLs0cQ-iogoWOgTRH.json.tmp.1.9dd2a4a2' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/2AY1G8ukSqrGaJZrarYCc46XKNajVu9q.json.tmp.1.7e542ab9' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/JHMu5jLVwurJFuGlXzpegOjKK6ixJhC.json.tmp.1.a2b96683' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/tE71GEDElQAEpBNF63rgfZiEfUKjx57x.json.tmp.1.2bff8460' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18)
Chris wrote:
I’m sorry — the earlier blanket ownership repair was the wrong step and was not safe for all of /opt/sparkbox/state. The error you just pasted shows that the dashboard still cannot write its session files; it does not mean every SparkBox state folder should be owned by the dashboard user. Please run one supported SparkBox upgrade: sudo sparkbox upgrade, then try one normal dashboard login again. I’ve corrected this guidance so future answers do not send people to the broad ownership repair.
TestedEcho wrote:
if that worked as a solution I wouldn't be here to ask... but I'm doing it again. if every restart, update, upgrade,... makes the ownership change, doing it again doesn't really help...
TestedEcho wrote:
and here are the logs again: [startup] Cleared stale operation lock: lock from previous dashboard instance (bootId mismatch) [2026-09-20T21:49:34.025Z] [INFO] SparkBox Dashboard running on port 8443 [2026-09-20T21:49:34.045Z] [INFO] SBROOT: /app [2026-09-20T21:49:34.050Z] [INFO] License tier (cached): legend [2026-09-20T21:49:34.064Z] [INFO] Backup encryption: dedicated key [health-report] Weekly report scheduler started (Sundays 8 AM). [knowledge-miner] Initialized. Daily mining at 4:00 AM. [2026-09-20T21:49:34.793Z] [WARN] [perms] could not chmod .env-hash: EPERM: operation not permitted, chmod '/app/state/.env-hash' [2026-09-20T21:49:34.794Z] [WARN] [perms] could not chmod .module-render-hashes: EPERM: operation not permitted, chmod '/app/state/.module-render-hashes' [2026-09-20T21:49:34.798Z] [WARN] [perms] could not chmod alerts.json: EPERM: operation not permitted, chmod '/app/state/alerts.json' [2026-09-20T21:49:34.801Z] [WARN] [perms] could not chmod arr-api-keys.json: EPERM: operation not permitted, chmod '/app/state/arr-api-keys.json' [2026-09-20T21:49:34.802Z] [WARN] [perms] could not chmod arr-bootstrap.log: EPERM: operation not permitted, chmod '/app/state/arr-bootstrap.log' [2026-09-20T21:49:34.802Z] [WARN] [perms] could not chmod authelia-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/authelia-admin-password.txt' [2026-09-20T21:49:34.803Z] [WARN] [perms] could not chmod backup-schedule.json: EPERM: operation not permitted, chmod '/app/state/backup-schedule.json' [2026-09-20T21:49:34.804Z] [WARN] [perms] could not chmod backup-status.json: EPERM: operation not permitted, chmod '/app/state/backup-status.json' [2026-09-20T21:49:34.807Z] [WARN] [perms] could not chmod bazarr-languages-seeded: EPERM: operation not permitted, chmod '/app/state/bazarr-languages-seeded' [2026-09-20T21:49:34.808Z] [WARN] [perms] could not chmod bazarr-wired: EPERM: operation not permitted, chmod '/app/state/bazarr-wired' [2026-09-20T21:49:34.808Z] [WARN] [perms] could not chmod chat-usage.json: EPERM: operation not permitted, chmod '/app/state/chat-usage.json' [2026-09-20T21:49:34.814Z] [WARN] [perms] could not chmod dashboard-prefs.json: EPERM: operation not permitted, chmod '/app/state/dashboard-prefs.json' [2026-09-20T21:49:34.815Z] [WARN] [perms] could not chmod doctor-last.json: EPERM: operation not permitted, chmod '/app/state/doctor-last.json' [2026-09-20T21:49:34.815Z] [WARN] [perms] could not chmod duplicati-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/duplicati-admin-password.txt' [2026-09-20T21:49:34.819Z] [WARN] [perms] could not chmod filebrowser-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/filebrowser-admin-password.txt' [2026-09-20T21:49:34.819Z] [WARN] [perms] could not chmod filebrowser-init.log: EPERM: operation not permitted, chmod '/app/state/filebrowser-init.log' [2026-09-20T21:49:34.820Z] [WARN] [perms] could not chmod filebrowser-initted: EPERM: operation not permitted, chmod '/app/state/filebrowser-initted' [2026-09-20T21:49:34.820Z] [WARN] [perms] could not chmod fleet-notices.json: EPERM: operation not permitted, chmod '/app/state/fleet-notices.json' [2026-09-20T21:49:34.821Z] [WARN] [perms] could not chmod fleet-patterns-active.json: EPERM: operation not permitted, chmod '/app/state/fleet-patterns-active.json' [2026-09-20T21:49:34.824Z] [WARN] [perms] could not chmod fleet-patterns-cache.json: EPERM: operation not permitted, chmod '/app/state/fleet-patterns-cache.json' [2026-09-20T21:49:34.824Z] [WARN] [perms] could not chmod gotify-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/gotify-admin-password.txt' [2026-09-20T21:49:34.824Z] [WARN] [perms] could not chmod hw-dri-gids: EPERM: operation not permitted, chmod '/app/state/hw-dri-gids' [2026-09-20T21:49:34.824Z] [WARN] [perms] could not chmod hw-dri-present: EPERM: operation not permitted, chmod '/app/state/hw-dri-present' [2026-09-20T21:49:34.825Z] [WARN] [perms] could not chmod install-failure-1781737441.log: EPERM: operation not permitted, chmod '/app/state/install-failure-1781737441.log' [2026-09-20T21:49:34.825Z] [WARN] [perms] could not chmod install-failure-1781816240.log: EPERM: operation not permitted, chmod '/app/state/install-failure-1781816240.log' [2026-09-20T21:49:34.825Z] [WARN] [perms] could not chmod install-failure-1781834156.log: EPERM: operation not permitted, chmod '/app/state/install-failure-1781834156.log' [2026-09-20T21:49:34.825Z] [WARN] [perms] could not chmod install-failure-1781840837.log: EPERM: operation not permitted, chmod '/app/state/install-failure-1781840837.log' [2026-09-20T21:49:34.825Z] [WARN] [perms] could not chmod install-failure-1781842516.log: EPERM: operation not permitted, chmod '/app/state/install-failure-1781842516.log' [2026-09-20T21:49:34.826Z] [WARN] [perms] could not chmod install-id: EPERM: operation not permitted, chmod '/app/state/install-id' [2026-09-20T21:49:34.826Z] [WARN] [perms] could not chmod install-meta.conf: EPERM: operation not permitted, chmod '/app/state/install-meta.conf' [2026-09-20T21:49:34.826Z] [WARN] [perms] could not chmod jellyfin-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/jellyfin-admin-password.txt' [2026-09-20T21:49:34.827Z] [WARN] [perms] could not chmod jellyfin-encoding-seeded: EPERM: operation not permitted, chmod '/app/state/jellyfin-encoding-seeded' [2026-09-20T21:49:34.827Z] [WARN] [perms] could not chmod jellyfin-language-seeded: EPERM: operation not permitted, chmod '/app/state/jellyfin-language-seeded' [2026-09-20T21:49:34.831Z] [WARN] [perms] could not chmod license-skipped: EPERM: operation not permitted, chmod '/app/state/license-skipped' [2026-09-20T21:49:34.831Z] [WARN] [perms] could not chmod license.json: EPERM: operation not permitted, chmod '/app/state/license.json' [2026-09-20T21:49:34.832Z] [WARN] [perms] could not chmod linkding-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/linkding-admin-password.txt' [2026-09-20T21:49:34.832Z] [WARN] [perms] could not chmod manifest-cache.json: EPERM: operation not permitted, chmod '/app/state/manifest-cache.json' [2026-09-20T21:49:34.832Z] [WARN] [perms] could not chmod media-autoseed.lock: EPERM: operation not permitted, chmod '/app/state/media-autoseed.lock' [2026-09-20T21:49:34.833Z] [WARN] [perms] could not chmod media-autoseed.log: EPERM: operation not permitted, chmod '/app/state/media-autoseed.log' [2026-09-20T21:49:34.833Z] [WARN] [perms] could not chmod media-autoseeded: EPERM: operation not permitted, chmod '/app/state/media-autoseeded' [2026-09-20T21:49:34.833Z] [WARN] [perms] could not chmod media-finish.log: EPERM: operation not permitted, chmod '/app/state/media-finish.log' [2026-09-20T21:49:34.835Z] [WARN] [perms] could not chmod media-finished: EPERM: operation not permitted, chmod '/app/state/media-finished' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod media-requests-watch.json: EPERM: operation not permitted, chmod '/app/state/media-requests-watch.json' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod media-research.json: EPERM: operation not permitted, chmod '/app/state/media-research.json' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod metrics-history.json: EPERM: operation not permitted, chmod '/app/state/metrics-history.json' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod modules.conf: EPERM: operation not permitted, chmod '/app/state/modules.conf' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod npm-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/npm-admin-password.txt' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod pihole-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/pihole-admin-password.txt' [2026-09-20T21:49:34.839Z] [WARN] [perms] could not chmod portainer-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/portainer-admin-password.txt' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod pre-update-digests.json: EPERM: operation not permitted, chmod '/app/state/pre-update-digests.json' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod profile-apply.log: EPERM: operation not permitted, chmod '/app/state/profile-apply.log' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod prowlarr-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/prowlarr-admin-password.txt' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod push-update-notifications.json: EPERM: operation not permitted, chmod '/app/state/push-update-notifications.json' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod qbit-forwarded-port.last: EPERM: operation not permitted, chmod '/app/state/qbit-forwarded-port.last' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod qbit-seed-limits.applied: EPERM: operation not permitted, chmod '/app/state/qbit-seed-limits.applied' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod qbittorrent-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/qbittorrent-admin-password.txt' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod qbittorrent-admin-password.txt.save: EPERM: operation not permitted, chmod '/app/state/qbittorrent-admin-password.txt.save' [2026-09-20T21:49:34.840Z] [WARN] [perms] could not chmod radarr-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/radarr-admin-password.txt' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod recyclarr-sync.log: EPERM: operation not permitted, chmod '/app/state/recyclarr-sync.log' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod recyclarr-synced: EPERM: operation not permitted, chmod '/app/state/recyclarr-synced' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod security-scan.json: EPERM: operation not permitted, chmod '/app/state/security-scan.json' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod seerr-seed-profiles.json: EPERM: o
TestedEcho wrote:
[2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod seerr-seed-profiles.json: EPERM: operation not permitted, chmod '/app/state/seerr-seed-profiles.json' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod seerr-seed.lock: EPERM: operation not permitted, chmod '/app/state/seerr-seed.lock' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod seerr-seed.log: EPERM: operation not permitted, chmod '/app/state/seerr-seed.log' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod self-heal-counts.json: EPERM: operation not permitted, chmod '/app/state/self-heal-counts.json' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod self-update-helper.log: EPERM: operation not permitted, chmod '/app/state/self-update-helper.log' [2026-09-20T21:49:34.841Z] [WARN] [perms] could not chmod setup-apply.log: EPERM: operation not permitted, chmod '/app/state/setup-apply.log' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod setup-complete: EPERM: operation not permitted, chmod '/app/state/setup-complete' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod sonarr-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/sonarr-admin-password.txt' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod sparkbox-err-trap.log: EPERM: operation not permitted, chmod '/app/state/sparkbox-err-trap.log' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod telemetry-history.json: EPERM: operation not permitted, chmod '/app/state/telemetry-history.json' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod telemetry-install-id.txt: EPERM: operation not permitted, chmod '/app/state/telemetry-install-id.txt' [2026-09-20T21:49:34.842Z] [WARN] [perms] could not chmod telemetry.json: EPERM: operation not permitted, chmod '/app/state/telemetry.json' [2026-09-20T21:49:34.846Z] [WARN] [perms] could not chmod updates.json: EPERM: operation not permitted, chmod '/app/state/updates.json' [2026-09-20T21:49:34.852Z] [WARN] [perms] could not chmod vault.enc: EPERM: operation not permitted, chmod '/app/state/vault.enc' [2026-09-20T21:49:34.853Z] [WARN] [perms] could not chmod vault.key: EPERM: operation not permitted, chmod '/app/state/vault.key' [2026-09-20T21:49:34.854Z] [WARN] [perms] could not chmod vaultwarden-admin-password.txt: EPERM: operation not permitted, chmod '/app/state/vaultwarden-admin-password.txt' [2026-09-20T21:49:34.859Z] [WARN] [perms] could not chmod wizard.json: EPERM: operation not permitted, chmod '/app/state/wizard.json' [2026-09-20T21:49:34.862Z] [WARN] [perms] could not chmod workspace-history.json: EPERM: operation not permitted, chmod '/app/state/workspace-history.json' [alerts] Service health monitor started (30s interval; safety floor active for all installs). [scheduler] Cron job started: 0 4 [scheduler] SparkBox-self-update check scheduled (0 5 ). [backup-scheduler] Cron job started: 0 2 0 [downloads-watch] watching /host/media/downloads (scan after 90s of quiet). [2026-09-20T21:49:40.099Z] [INFO] License cache refreshed: licensed (Pro) [downloads-watch] watcher error: EACCES: permission denied, watch '/host/media/downloads/incomplete/tmpplxzhapp' [alerts] disk-warning [data]: Your storage drive (app data, photos, backups) is 86% full — consider freeing space or adding storage. [alerts] sb-seerr is stopped [2026-09-20T21:50:14.507Z] [ERROR] [sessions] cannot write /app/state/sessions (EACCES). Logins are held in memory until the next restart; the folder must be owned by uid 1000. Fix on the host: sudo sparkbox restart (or: sudo chown -R 1000:1000 /opt/sparkbox/state/sessions) [2026-09-20T21:54:34.290Z] [INFO] License cache refreshed: licensed (Pro) [2026-09-20T21:59:34.237Z] [INFO] License cache refreshed: licensed (Pro) [metrics-history] cannot persist /app/state/metrics-history.json (EACCES); history will not survive a restart
Chris wrote:
I’m sorry — repeating sudo sparkbox upgrade was not a real answer to your report that the ownership changes again after every restart and update. Your new logs show a wider host-side permission failure: the dashboard cannot chmod the state files, then cannot write sessions or metrics. The earlier broad ownership repair was also the wrong step and was not safe for all of /opt/sparkbox/state. The true mechanism is that a root-run update/recreate path is writing dashboard state as root while the dashboard runs as UID 1000; the supported ownership repair is not being applied on your NAS. I’ve recorded this as an unresolved product bug, but the available investigation is not yet a released fix, so I won’t claim another upgrade will solve it. Please do not run another chown -R, reset, or reinstall. One next check only: on the NAS host, run sudo stat -c '%u:%g %a %n' /opt/sparkbox/state /opt/sparkbox/state/sessions and paste just those two lines (no logs containing passwords or keys). I’ve corrected this guidance so future answers do not send you through the same ineffective upgrade or blanket ownership repair again.
TestedEcho wrote:
0:10 775 /opt/sparkbox/state 0:10 700 /opt/sparkbox/state/sessions
Chris wrote:
You’re right — repeating an upgrade was not a real answer when the ownership changes again on the next restart. I’m sorry for sending you through that loop, and the earlier blanket ownership repair was also the wrong and unsafe step. Your new result confirms the immediate failure: /opt/sparkbox/state/sessions is owned by root (UID 0) and has mode 700, so the dashboard’s UID 1000 cannot create its session files. This is not a password problem, and it is not evidence that every folder under /opt/sparkbox/state should be changed. One next check only, on the NAS host: run sudo -u '1000' test -w /opt/sparkbox/state/sessions && printf 'WRITE-OK\n' || printf 'WRITE-BLOCKED\n' Please paste only WRITE-OK or WRITE-BLOCKED. Do not run another chown, reset, or reinstall yet. The existing repair path is not holding on your NAS, so I won’t claim another upgrade fixes this; I’ve corrected the guidance so future answers do not send you through the same ineffective upgrade or blanket ownership repair again.
TestedEcho wrote:
WRITE-BLOCKED
Chris wrote:
I’m sorry — the earlier replies kept sending you through upgrades and broad ownership repairs even after you showed that the ownership changes back. WRITE-BLOCKED confirms the immediate problem: the dashboard runs as UID 1000, but the host-side sessions directory is still root-owned with permissions that deny UID 1000, so this is not a password problem. Please do not run another chown -R, reset, or reinstall. One next check only, on the NAS host (not inside Docker): findmnt -T /opt/sparkbox/state/sessions -o TARGET,FSTYPE,OPTIONS Please paste just the single output line. This will show whether the path is on a filesystem or mount whose ownership rules prevent SparkBox's supported repair from sticking. I’ve corrected this guidance so future answers do not send you through the same ineffective upgrade or blanket ownership repair again.
TestedEcho wrote:
TARGET FSTYPE OPTIONS / overlay rw,relatime,lowerdir=/rootfs/oem:/rootfs/fw:/rootfs/apt:/rootfs/kernel:/rootfs/base,upperdir=/overlay/upper,workdir=/overlay/work if you need anything else please ask all at once, because life happens, I cant always come back fast it seems, so the main page and other things suffering under the same problem dont work.
Chris wrote:
You’re right to ask me to stop sending you through the same loop. I’m sorry: I repeated upgrades that had already failed, and I previously suggested a broad ownership change that was not safe. Your latest findmnt output shows that, in the environment where that command ran, the path resolves through an overlay filesystem; by itself it does not tell us what backs the NAS’s SparkBox data or why ownership keeps changing. The EACCES errors and WRITE-BLOCKED do confirm the dashboard cannot write its session files, and this is not a password problem. Please don’t run another recursive ownership change, reset, or reinstall. One clarification so we don’t send you around again: did you run findmnt directly in the NAS’s host shell, or inside a container/terminal opened from an app? I’ve corrected this guidance so it won’t recommend the earlier blanket repair again.
TestedEcho wrote:
I log in with ssh with a console app on my Mac/phone as the standard user.
Chris wrote:
Thanks—that confirms you connected to the NAS over SSH as your normal account. I’m sorry this has dragged on through repeated upgrades and earlier unsafe ownership advice. The overlay result means the path resolves through the NAS shell’s root filesystem, but it doesn’t show what backs SparkBox’s data or why its ownership keeps reverting; the earlier checks do confirm the dashboard cannot write its session state. Please send these details together, with no more changes or commands for now: the NAS make/model and OS version, and the SparkBox version currently shown on the box. I’ve corrected the guidance so it won’t repeat the blanket ownership fix or claim another upgrade will resolve this.
TestedEcho wrote:
agreen dxp2800, latest os update, sparkbox 1.6.850
Chris wrote:
Thanks — that gives us the NAS model and SparkBox version. I’m sorry this is still affecting the main page after all the repeated checks. The ownership problem remains unresolved; the earlier overlay result doesn’t show why the NAS keeps changing access to the dashboard’s session files. One remaining detail, with no more commands needed: what exact NAS OS version/build is shown in the NAS system information?
TestedEcho wrote:
1.20.0.0142 but it was with the previous version as well so
Chris wrote:
Thanks—that confirms this was happening on the previous NAS OS version too, so the OS update alone doesn't explain it. I'm sorry this has dragged on through repeated upgrades and checks. The earlier errors confirm the dashboard could not write its state, but the checks so far have not established why that access keeps reverting; I don't have a verified released fix for this exact NAS behavior, and it is already part of the unresolved report. Please don't run another ownership change, reset, or reinstall. One check only: since you're now on SparkBox 1.6.850, please try one normal dashboard login and tell me whether it succeeds, shows an Internal Server Error, or reports a permissions error.
TestedEcho wrote:
sometimes it works after a restart. but it now also cant seem to make encrypted backups anymore. it makes a backup but doesn't encrypt it. it always seems to come back to some kindergarten of ownership or rights problem, and seers seems to have a problem with it too. probably other things too, but I'd just like the underlying problem to be solved. this is what it says about the backup: Backups have been failing since 12m — EACCES: permission denied, open '/app/backups/sparkbox-backup-20261003214403.tar.gz.enc.tmp.1.bd08f8e54696'. I cant give you much more information you dont have. can you or tom give me a way to solve this all?
Chris wrote:
I’m sorry—we’ve sent you through repeated updates and ownership changes before, and that hasn’t stopped this coming back. The new backup message confirms a write-permission failure, but it doesn’t yet prove that the dashboard sessions, backup encryption, and Seerr all have the same cause, so I don’t want to guess with another ownership change. Could you do one read-only check from your NAS SSH session: get the filesystem type and mount options for the host folders backing SparkBox state and backups (the findmnt -T output for each), and share only TARGET, FSTYPE, and OPTIONS with any share names or source paths redacted? If Seerr shows a specific error, include just that error text too—no configs or secrets. We’ve corrected our support guidance so it won’t send the same broad ownership fix again; once we know what backs those folders, we can choose a safe next step rather than reset things blindly.