Community AlphaAlpha MUADMINS
PTPortuguês (Brasil)
Entrar
No MuADMINSConfig ScannerEnvie o zip dos seus arquivos: rates, drops, spots, limitesAbrirNo MuADMINSEncontre-nos no DiscordPeça ajuda, mostre o que está criando e converse sobre MU com outros donos de servidores.Abrir
← Todas as soluções

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

✓ Confirmado na issue

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

A pessoa que abriu o issue confirmou que isso resolveu.

Palavras originais (Inglês)

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

Na issue, 2026-10-07 (palavras originais)
GitHub (MUnique/OpenMU) · 2026-10-07
Isso ajudou?

Ainda com problema? Buscar no MuGPS Pergunte ao Assistente MU

MuADMINS Community Alpha: grátis, feito pela comunidade e em desenvolvimento ativo.