Community AlphaAlpha MUADMINS
FILFilipino
Mag-sign in
Sa MuADMINSConfig ScannerI-upload ang zip ng mga file mo: rate, drop, spot, limitBuksanSa MuADMINSMakipagkita sa amin sa DiscordHumingi ng tulong, ibahagi ang ginagawa mo at makipag-usap tungkol sa MU sa ibang may-ari ng server.Buksan
← Lahat ng solusyon

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

✓ Kinumpirma sa 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.

Kinumpirma ng taong nagbukas ng issue na naayos nito ang problema.

Orihinal na salita (Ingles)

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

Sa issue, 2026-10-07 (orihinal na salita)
GitHub (MUnique/OpenMU) · 2026-10-07
Nakatulong ba ito?

Naipit pa rin? Maghanap sa MuGPS Magtanong sa MU Assistant

MuADMINS Community Alpha: libre, gawa ng komunidad, at patuloy na dine-develop.