7 replies
tomspark wrote:
Same family as the VPN-settings panel bug you hit on 9239 yesterday — dashboard JS click-handler not wired up on at least some installs. Try Ctrl+Shift+R hard refresh first; if that fixes it, the bug is just a stale cached chunk in your browser. If not, open F12 → Console tab → click the toggle once → screenshot any red error lines that appear and paste here. That'll tell me whether it's a server-side handler missing in your build or a SPA caching issue. v1.6.106 just shipped (unrelated Seerr fix) — sudo sparkbox update is worth running to get on current either way.
GamerX06 wrote:
I did the hard refresh and still have the issue. With the developer console open nothing is shown when clicking the toggle, just one error from when if first loads the page
tomspark wrote:
Thanks for checking — nothing logging on click plus one error on page load is the tell. That single load-time error is almost certainly a JS exception that aborts the rest of the dashboard init, so none of the toggle handlers ever get wired (same family as the VPN-settings one). Can you paste the exact text of that one console error — the red line and the file:line it points at? That's the smoking gun I need. Also try the dashboard once in a private/incognito window: if the toggle works there it's a stale cached JS bundle and I'll add a cache-bust; if it still fails it's server-side in your build. This is the 3rd report of this class so it's getting a real fix. (v1.6.115)
GamerX06 wrote:
Let me see if I can get you everything Console Paste (index):1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/potentially-trustworthy-origin and https://html.spec.whatwg.org/the-cross-origin-opener-policy-header. :8443/api/remote-access:1 Failed to load resource: the server responded with a status of 403 (Forbidden) The file its linked to on (index):1 Console images on incognito Incognito Console Paste (index):1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/potentially-trustworthy-origin and https://html.spec.whatwg.org/the-cross-origin-opener-policy-header. :8443/api/updates/available:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/backups:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/environment:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/config:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/support/status:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/arr-auth/state:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/wizard/status:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/config:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/chat/available:1 Failed to load resource: the server responded with a status of 401 (Unauthorized) :8443/api/config:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
tomspark wrote:
Got it — those 401s on every API endpoint mean your session auth isn't passing through. That COOP header warning is a red herring (HTTP origin issue, harmless). The real problem: you're logged out or the session cookie isn't being sent on CORS requests. Try clearing all cookies for :8443, then log in fresh — if the toggle works after that, it's a stale session issue and I'll add a session-timeout banner. If still broken, run sudo sparkbox update to v1.6.115 (just shipped with a fix for this class of auth-state bugs).
GamerX06 wrote:
This is now working after I added my Legend License. If that was an intended bonus, then I think all is well; if not, then there may still be an issue with unlicensed versions
Chris wrote:
Good of you to flag it rather than just move on — and the honest answer is that it was never a Legend perk. Scheduled updates do need an activated licence, but the free personal-use key counts for that. So your Legend key switched it on, and a free key would have done exactly the same. What you actually hit was a toggle sitting behind a licence check with nothing on screen telling you why it would not move, which is a poor experience and was not unique to you. That has since changed: the Updates page is no longer put behind a licence check at all. So no, there is nothing still broken for unlicensed installs. — Chris