Community AlphaAlpha MUADMINS
ITItaliano
Accedi
Su MuADMINSConfig ScannerCarica lo zip dei tuoi file: rates, drop, spot, limitiApriSu MuADMINSIncontraci su DiscordChiedi aiuto, condividi quello che stai creando e parla di MU con altri proprietari di server.Apri
← Tutte le soluzioni

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

✓ Confermato nella issue

Strumento: 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.

La persona che ha aperto la issue ha confermato che questo l'ha risolta.

Parole originali (Inglese)

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

Nella issue, 2026-10-07 (parole originali)
GitHub (MUnique/OpenMU) · 2026-10-07
Ti è stato utile?

Non hai ancora risolto? Cerca su MuGPS Chiedi all'Assistente MU

MuADMINS Community Alpha: gratuito, fatto dalla community, in sviluppo attivo.