Reproduction steps
- Move User
Observed behaviour
The user gets moved to the channel, but is invisible, and gets disconnected and reconnected constantly in a loop
Build information
Canary Desktop 2026.606.140333, Web 2026.605.11941, Windows 11 10.0.26300 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-US
Platform
Windows
Details
Expected behaviour
Should move the user to the channel without issues
17 comments
Comment by Rex
Comment by Aidan
Comment by Excorio
- User joins a channel and connects to voice.
- An admin moves the user to another channel.
- Instead of being auto-connected in the new channel, the user is prompted to connect voice.
- Following this, the user is briefly presented with a reconnect prompt and gets placed back in the previous channel with voice connected.
My interpretation of the events: The sequence looks like the move is treated as a sudden disconnect, which appears to trigger an auto-reconnect feature (if it exists) that restores the last connected channel. If so, that feature makes sense for genuine sudden disconnects but should not fire on an intentional move. A moved use that was voice-connected in the previous channel and moved should be voice-connected in the destination channel they get moved to.Comment by Aidan
Comment by The Dark Wizard
Comment by Zaostaly Jezevec
PATCH /guilds/{g}/members/{u}with{"channel_id": ...}returns 200, the user sees "connecting" (orange), then an error, and after ~5 s the client puts them back in the original channel. Same on desktop and web. Console output (both clients):
If (2) is processed while (1) is still in flight, the attempt id is bumped byVOICE_STATE_UPDATE(new channel). The client handles it inMediaEngineFacade.ts(~L1889-1898): it callsdisconnectForChannelMove('server')and, in.finally(),recoverConnectionExpectation(...). That starts a new connection attempt.VOICE_SERVER_UPDATE(token for the new channel). The handler inVoiceEngineV2AppConnectionHostAdapter.tsaccepts it, then awaitsgetRoomVideoDecoderExclusions()and re-checksisLatestConnectionAttempt(attemptId)(~L519-526).recoverConnectionExpectationand the already running attempt for the token is discarded as stale. The server only sends the token once, so the client waits for aVOICE_SERVER_UPDATEthat never comes again, times out after 5 s and reconnects to the old channel. With a fast, local LiveKit the token seems to arrive right after the state update, so this lost the race every time for us. (This is my reading of the client code, I did not trace the exact event order.) This also matches the "Connection succeeded but attempt is stale, disconnecting" log from other self-hosters in this thread. Workaround that works for us Influxer_gateway/src/guild/voice/guild_voice_move.erl, delay the token dispatch a bit soVOICE_STATE_UPDATEis always handled first. The function already runs in a spawned process, so nothing is blocked:Comment by ternera
Off-topic comment by Comfy_Deer
Comment by Comfy_Deer
Comment by Fullest
Comment by @laurentm28
Comment by @laurentm28
Comment by VII
Comment by mesub
Comment by penguin
- Self-hosted Fluxer
- Canary Web 2026.1008.22644
- Linux (x64), Firefox 157.0, Locale en-US
- Second user: Chrome (web client)
- Both users were using the web version, not the desktop app.
Observed behavior:- Moving another user to a different voice channel sometimes makes them disappear from the voice channel list entirely.
- Moving them back sometimes works, but both users may then be unable to hear each other.
- Repeated channel moves can also cause the moved user to disconnect.
- Fully disconnecting and reconnecting both users temporarily resolves the issue.
Relevant log messages: Browser:Comment by probablyjassin
fluxer-vc-moved.png
1602×905 | 90 kB Link to fluxer-vc-moved.png
Comment by Aidan