Players can't connect to server (You are already connected to this network)

[phm07]

Stacktrace

https://gist.github.com/pauhull/77fbb0070b66a903ad84edc70c3b78e2

Actions to reproduce

Error appears randomly

CloudNet version

[17.01 16:24:10.550] INFO:  
[17.01 16:24:10.550] INFO: CloudNet Blizzard 4.0.0-RC5 4ec2a84d
[17.01 16:24:10.550] INFO: Discord: <https://discord.cloudnetservice.eu/>
[17.01 16:24:10.551] INFO:  
[17.01 16:24:10.551] INFO: ClusterId: b524d946-****-45c6-****-4a8fcdf47225
[17.01 16:24:10.551] INFO: NodeId: Node-1
[17.01 16:24:10.551] INFO: Head-NodeId: Node-2
[17.01 16:24:10.552] INFO: CPU usage: (P/S) 1.84/6.4/100%
[17.01 16:24:10.552] INFO: Node services memory allocation (U/R/M): 4096/4096/25600 MB
[17.01 16:24:10.552] INFO: Threads: 70
[17.01 16:24:10.553] INFO: Heap usage: 135/456MB
[17.01 16:24:10.553] INFO: JVM: Debian 17 (OpenJDK 64-Bit Server VM 17.0.4+8-Debian-1deb11u1)
[17.01 16:24:10.553] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: beta
[17.01 16:24:10.553] INFO:  

Other

Issue uniqueness

• [X] Yes, this issue is unique. There are no similar issues.

[derklaro]

Might be related to the thrown exception - other listeners that are listening for the event are not executed if one listener throws an exception. In general this is the first report of issues with player connections in v4, so I doubt that there is an issue in the general player handling process that is related to the issue.

[strich3]

same problem here. Happens when you timeout

[strich3]

Also it‘s already reported :)

[strich3]

#982

[0utplay]

I think this can be closed as outdated and not reproducable