Self-help / diagnostics thread for people having infrequent, sudden disconnects when multi-boxing

So in this thread I’d like to discuss a problem with a very specific kind of disconnect issue. This relates ONLY to players who:
-have a very stable, fast, low-latency, wired internet connection with no general connectivity issues
-only get disconnected from EVE while all other internet-related apps are unaffected
-always get disconnected on all clients simultaneously with no warning signs like general lagginess for minutes prior to the disconnect
-can always immediately reconnect after such a disconnect(!)

This is NOT for you if you:
-often have general problems with your internet (or even game with a wifi connection, ugh)
-always or sometimes lose connection with some clients but one or more other EVE clients stay connected
-experience lagginess in EVE during the minutes before the disconnect
-can not immediately reconnect
If you fit one or more of these criteria, you may have legitimate issues as well, but they are definitely different from the issue I experience and want to discuss here.

With that out of the way: I was logged in for multiple hours per day almost every day for the last several months, but the vast majority of the time with only one or two clients that don’t do much, only scanning and monitoring. I NEVER got disconnected during these many, many hours of ‘low-intensity playing’.

But sometimes I use up to five clients, and in a much more intensive way, sometimes issuing a lot of orders in rapid succession. And when playing like this, I had still rather rare and infrequent, but multiple instances where I got disconnected as described above: Totally suddenly, with no warning signs like lagginess, on all clients simultaneously. And I could always reconnect immediately. It actually doesn’t really feel like a disconnect, more like being deliberately kicked by the server.

This always without fail happened at the worst possible moment: In high-end combat sites, resulting in the loss of ships.

But recently I could trigger such a disconnect in a different situation: I was undocking five characters at once and was frantically clicking stuff on all clients very rapidly. Boom, disconnect on all clients.

I have seen in reports by other players who seem to have this issue that most or all seem to share one thing: They get these disconnects while multi-boxing.

So my theory is that these disconnects are a result of new anti-DDoS measures on the part of CCP. When we use multiple clients and issue a lot of commands in a short time, it will sometimes trigger a mechanism meant to protect the cluster from DDoS attacks and kicking such clients before they can overwhelm the servers. Meaning it isn’t actually a connection issue at all.

If this is true, CCP are not going to acknowledge it because it means they are actively kicking players from the server. I’m not really mad about that by the way; DDoS is a serious problem and difficult to defend against.

In one instance some days ago I had the weird occurence that all my clients seemed to be frozen for about 20 seconds, no damage was dealt or received, or at least not displayed. Modules kept running but didn’t seem to do anything. I just waited and didn’t click anything, and eventually the game resumed.

Then some days later I had the same situation, but this time I continued clicking stuff. Boom, disconnect, ship loss.

So I encourage anyone who experiences this issue to try this:
-deliberately slow down when using multiple clients, avoiding to issue commands rapidly (one command per second or less)
Or do the opposite in non-critical situations:
-try to click madly on several clients to generate as much (non-automated) input as possible and see if you can sometimes trigger a disconnect
(but the latter definitely does not reliably work, thankfully)

Let’s see if being slow eliminates or reduces these disconnects.

1 Like

I have come to the same conclusion as you have: CCP is suspicious of multiboxed connections because they look a lot like DDoS attacks.

I too am suffering this issue but not with multiboxing. It CAN happen when I have dual clients (only one character will drop) but it can also happen when I only have 1 client open.

I had this issue 3 months ago after a stealth patch(no patch notes) that cleared up after 4-5 days.

Once again after a recent patch around wednesday or thursday I have suddenly started having multiple disconnects per day. There is no latency issues. My internet is solid in all other programs. The most common disconnects occur when

  1. Undocking.
  2. Landing on grid after a warp.
  3. Interacting with the probe scanning window.

EXCEPTION #35 logged at 20/09/20 13:19:07 : Exception during soft clock sync

Formatted exception info:
UserError: User error, msg=GPSTransportClosed, dict={‘what’: ‘The transport has not yet been connected, or authentication was not successful.’}

Common path prefix = c:/buildagent/work/d2d8a22a74178531/eve/release/release

Caught at:

/packages/bluepy/__init__.py(42) CallWrapper
/carbon/client/script/remote/connectionService.py(289) ClockSyncDaemon

Thrown at:
/carbon/client/script/remote/connectionService.py(259) ClockSyncDaemon
/carbon/common/script/net/ServiceCallGPCS.py(775) callable
/carbon/common/script/net/machobase.py(134) ThrottledCall
/carbon/common/script/net/ServiceCallGPCS.py(766) doCall
/carbon/common/script/net/ServiceCallGPCS.py(312) RemoteServiceCallWithoutTheStars
/carbon/common/script/net/ObjectCallGPCS.py(244) CallDown
/carbon/common/script/net/ExceptionMappingGPCS.py(80) CallDown
/carbon/common/script/net/ExceptionMappingGPCS.py(57) _ProcessCall
/carbon/common/script/net/ExceptionWrapperGPCS.py(118) CallDown
/carbon/common/script/net/machoNet.py(4095) _BlockingCall
(2) _GetTransports
/packages/ccpProfile/blueTaskletImplementation.py(40) Wrapper
/carbon/common/script/net/machoNet.py(4253) _GetTransports
destAddress = Address::Node(nodeID="1000005140",service="machoNet",callID="None")
self = 
srcTransport = None

Thread Locals: session was 
Stackhash: 759381310

Reported from: stdlogutils
EXCEPTION END

Well, I’ve never had problems undocking with 1 or 2 characters, but I have found that I need to stagger my undocks when boxing multiple toons.

Same issue here. 3 clients, no lag, and never had this issue before. In my case, it seems to begin between 01:00 and 02:00 and lasts 1 to 4 hours. I would love any advice. Perhaps I can do something on my end to stop it. I have tried logging out 2 accounts and the issue persists.

I have mostly been cruising around depopulated lowsec and null the last couple of months (with a number of alts). Today I tried logging into Jita (and environs) on a couple of different alts while I was also logged into low/null.

The system not only disconnected my alt after a few minutes (each time), it disconnected all my other characters as well.

I bit the bullet and got a VPN. Not a crash for 6 hours or so now…

Im happy I can play eve and FURIOUS I need to pay a VPN subscription fee to play eve on top of my regular sub.

Nordvpn works just fine I guess.