Endless loading screen with WebSocket 4000 "Failed to start session" error

Can't reproduce, it's working fine for me on MacOS, Windows and Chromium-based browser.

can reproduce on my main account, getting WebSocket closed [4000] Failed to start session with an alt account I am able to sign in fine in a browser reproducible across Windows, macOS and Linux with desktop clients as well as Android on Chrome

@hihi217 Yeah get the same WebSocket error and it just keeps retrying to connect. Created an alt and was able to get into fine but on my normal account it fails. So it seems to be something account based.

The issue seems to be related to specific user accounts and in some cases bots. My partner can't access Fluxer on either her laptop via Flatpak, nor the phone via the PWA. We share a network, and these issues don't persist for me, neither via Flatpak nor the PWA, and the behavior seems to be consistent regardless of network stuff with Ethernet or Wifi, so it isn't a personal network config issue of some kind. Someone else reports this happening with Bots as well. https://fluxer.app/channels/1427764813854588940/1427764813854588943/1493864569019360794 (in Fluxer Developers) They allege it's some kind of gateway issue, unfortunately i lack the technical knowhow to know where the breakdown here is.

I can't reprod the issue, so it does seem like this is only on certain accounts/bots.

Same issue here I can confirm I’m experiencing exactly the same problem.

Description

• After successful authentication, the app gets stuck on infinite loading
• WebSocket repeatedly reconnects
• Error in console:

  [Gateway] [Warn] WebSocket closed [4000]
  Failed to start session
  

Important observations

• Happens only with one specific account
• Other accounts work perfectly in the same environment
• Reproduces everywhere:
• Browser (normal + incognito)
• Native desktop app
• Mobile device
• Reproduces across different networks (with/without VPN)

What I tried

• Clearing all browser data (cookies, localStorage, etc.)
• Incognito mode
• Different browsers/devices
• Different networks

Nothing helped.

Additional notes

• Issue seems account-related rather than client/network related
• Looks like a broken session or invalid server-side state during gateway initialization

image

This is currently being looked into, track the incident here: https://fluxerstatus.com/cmo0307iy02llqteawv10xq88

Hey there, sorry about this; it's now fixed. Around 378 users were getting stuck because of a bug in our internal session counter. It wasn't decrementing properly in all cases, so it would incorrectly flag users as having too many active sessions and reject new connections. I've unblocked everyone affected and am fixing the underlying bug. Apologies for the trouble!