Edit history

Desktop app keeps the old gateway URL after the instance changes it has not been edited, so there are no earlier versions.

Current version | Original by df1z
Show

Desktop app keeps the old gateway URL after the instance changes it

Reproduction steps

  1. Sign in to a self-hosted instance in the desktop app.
  2. On the server, change FLUXER_GATEWAY_ENDPOINT to a new URL and restart. /.well-known/fluxer shows the new gateway straight away.
  3. Fully quit and restart the desktop app.
  4. Check which host the app's websocket is connected to (e.g. its TCP connections to 443).

Expected behaviour

The app picks up the new gateway from the instance on startup, or at least when the saved one stops working, so an instance can move its gateway without every member signing out.

Actual behaviour

The app keeps connecting to the old gateway, even after restarting. In my case that kept my members on the route I was trying to move them off. The desktop app saves gatewayEndpoint per account in desktop-app-store.sqlite3 (accounts.record_json). It also keeps a cached copy of the instance config under the old key. Restarting refreshes neither. Only signing out and back in did; after that the account record and both cached configs had the new URL. If the old gateway host had been shut down, I'd expect desktop users to be stuck until they signed out.

Platform

Windows

Evidence

Instance version: 2026.1118.162713. Before sign-out (after an app restart):
  • accounts.record_json: "gatewayEndpoint": "wss://<instance>/gateway" (old)
  • store_metadata runtime_discovery: the entry keyed by https://<instance> was stale; the one keyed by https://<instance>/api had the new gateway
  • The app's only websocket was to the old (Cloudflare) host
After sign-out and sign-in: all three had the new URL, and the app connected to the new host. Related: https://feedback.fluxer.com/p/4943/gateway-websocket-drops-in-bursts-behind-the-cloudflare-prox That's why I moved the gateway in the first place.