Community AlphaAlpha MUADMINS
ENEnglish
Sign in
On MuADMINSConfig ScannerDrop your files zip: rates, drops, spots, limitsOpenOn MuADMINSMeet us on DiscordAsk for help, share what you are building and talk MU with other server owners.Open
← All solutions

OpenMU: a player stays 'already connected' after a dropped connection and cannot log in again, even with the right password

✓ Confirmed in the issue

Tool: OpenMU

  1. The old session stays registered while the TCP connection to OpenMU is still open. With the web client the WebSocket proxy keeps that connection alive, so every new login gets AccountAlreadyConnected and the old session only sees a login attempt warning.
  2. Update OpenMU to a version with PR #1128 (fix(login): keep the login server state correct, detect lost connections). A player in the world whose client stops pinging for longer than a configurable timeout (default 2 minutes) is disconnected.
  3. Until then a GM can free the account with /disconnect.
  4. For the web client proxy (Ignies/OpenMu-Client-Babylon) the maintainer advises a per relay ping and closing the WebSocket after about 30 to 45 seconds of silence.

“#1128 keeps the login server state correct and adds detection based on the client's ping”

In the issue, 2026-10-07 (original words)
GitHub (MUnique/OpenMU) · 2026-10-07
Did this help?

Still stuck? Search MuGPS Ask the MU Assistant

MuADMINS Community Alpha: free and community made, in active development.