Controller disconnect causes loss of active 2b2t connection after Broken pipe

[CCCP84]

Description

Controller disconnect causes loss of active 2b2t connection after Broken pipe

Description

I am running ZenithProxy on a VPS and connecting to it from my home PC.

My goal is to keep my 2b2t session alive even if my home internet connection becomes unstable.

The proxy is configured with:

• clientConnection keepAlive mode independent
• AutoReconnect enabled

Most of the time, if my home internet briefly disconnects, I can simply reconnect my Minecraft client to Zenith and continue playing without losing the active 2b2t session.

However, sometimes a temporary internet outage causes Zenith to lose the active connection to 2b2t and I end up back in the queue.

From my point of view, this seems unexpected because keepAlive mode independent suggests that the server connection should not depend on the controller connection.

Relevant log

Client Disconnected

Reason
io.netty.channel.unix.Errors$NativeIoException: sendAddress(..) failed with error(-32): Broken pipe

[Module] [WARN] [Bot] Detected teleport desync, resyncing. queueSize: 100
[Client] [INFO] Server teleport ...
[Module] [WARN] [Bot] Detected teleport desync, resyncing. queueSize: 76
[Module] [WARN] [Bot] Detected teleport desync, resyncing. queueSize: 52
[Module] [WARN] [Bot] Detected teleport desync, resyncing. queueSize: 27
[Module] [WARN] [Bot] Detected teleport desync, resyncing. queueSize: 2

[Client] [INFO] Disconnecting from server...
[Client] [INFO] Disconnected: You have lost connection to the server

Disconnected

Reason
You have lost connection to the server

Category
KICK

AutoReconnecting in 5s

After reconnecting, Zenith joins the queue again and my previous position is lost.

Expected behavior

If only the controlling client disconnects because of a temporary internet outage (Broken pipe), I would expect Zenith to:

• disconnect only the controller;
• keep the existing connection to 2b2t alive;
• continue running normally (or stay AFK);
• allow the controller to reconnect later without losing the active 2b2t session.

Actual behavior

Sometimes, after a Broken pipe, Zenith eventually disconnects from 2b2t and AutoReconnect starts a completely new session, forcing me back into the queue.

Additional information

This is not consistently reproducible.

I have had many cases where my home internet disconnected, the controller disconnected from Zenith, and after reconnecting everything continued normally without losing the 2b2t session.

This issue only happens occasionally, usually during periods of very unstable internet.

Questions

• Is this the intended behavior?
• Is the disconnect from 2b2t caused by the teleport desync after the controller disconnects?
• Is there any configuration that allows Zenith to keep the 2b2t connection alive even if the controller connection is lost?
• If not, would such an option be possible as a feature request?