Can't login to dashboard anymore
Posted by TestedEcho
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)
17 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.