Self hosted Fluxer instances appear to have issues after updating Valkey to 8.1.9

(#748) Bug Fixed self-hosting

2mo agoby RexSystem edited originally by @Az-1-2 on GitHub

Summary

I updated my self hosted instance to the latest Valkey release, 8.1.9, as there were critical security fixes. However, upon attempting to load the web app, messages were unable to load and the app had multiple crashes. After resetting app data, I was unable to login and recieved the error "cannot use 'in' operator to search for "ban_view_token" in <!doctype html><..." when trying to login. Downgrading valkey back to 8.1.8 by adjusting the image tag fixed the problems I was having.

Steps to reproduce

Update Valkey as normal
Open the web app and notice the errors
Click the reset app data button when the app crashes
Attempt to login but fail

Environment

Version: Valkey 8.1.9, all other containers are the latest versions OS: Debian 13 Trixie Device: VPS

Logs or screenshots

image image

625433275-55a255a1-c3cb-4711-8ab7-7946652befe8.png
1440×3088 | 421 kB
625434086-4f0d26d4-c686-4c08-86c3-e1c535601d73.png
1440×3088 | 1.1 MB

History

2 comments

RexSystem 1 vote 2mo ago originally by @MrRubberDucky on GitHub

Works fine for me on that version, though in my case I'm using SSO. Does your reverse proxy reply with proper Content-Type header? It seems like it doesn't considering you get a HTML back for a (potential) JSON request, at least that's what I would assume. Error seems to hint as much.

cannot use 'in' operator to search for "ban_view_token" in <!doctype html><...

Permalink

RexSystem 1 vote 2mo ago originally by @Az-1-2 on GitHub OP

I'm not sure what happened but this seems to have been solved after updating the api and media proxy.

Permalink