SpigotMC / BungeeCord

BungeeCord, the 6th in a generation of server portal suites. Efficiently proxies and maintains connections and transport between multiple Minecraft servers.
https://www.spigotmc.org/go/bungeecord
Other
1.53k stars 1.09k forks source link

If player dies inside spigot server and kept on death screen the player will get kicked with disconnected with: ReadTimeoutException : null #3146

Closed ham1255 closed 2 years ago

ham1255 commented 3 years ago

as title says here is a video: click here

what i have tried so far:

  1. disable all plugins on proxy(bungeecord) and spigot servers
  2. check if am running any proxy forks (waterfall) if i do switch it to bungeecord, same goes to spigot too.
  3. created fresh and running test setup proxy setup with test spigot server

    what console shows when disconnected:

    19:01:50 [INFO] [Ham1255] <-> ServerConnector [test1] has connected
    19:02:00 [WARNING] [Ham1255] <-> DownstreamBridge <-> [test1] - read timed out
    19:02:00 [INFO] [Ham1255] disconnected with: ReadTimeoutException : null
    19:02:00 [INFO] [Ham1255] -> UpstreamBridge has disconnected
    19:02:00 [INFO] [Ham1255] <-> DownstreamBridge <-> [test1] has disconnected

    Bungeecord version: #1593

    not sure if if this bungeecord issue or spigot since spigot server logs says when kick happens

    [19:22:04] [Server thread/INFO]: Ham1255 fell out of the world
    [19:22:04] [Server thread/INFO]: Killed Ham1255
    [19:22:15] [Server thread/INFO]: Ham1255 lost connection: Disconnected
    [19:22:15] [Server thread/INFO]: Ham1255 left the game

    one of spigot forks output

    [19:01:50 INFO]: Ham1255[/127.0.0.1:49543] logged in with entity id 1 at ([test]222.00844959612, 72.0, -243.72180147943428)
    [19:02:00 INFO]: Ham1255 lost connection: Disconnected
    [19:02:00 INFO]: Ham1255 left the game

    which is pretty normal.

I don't know what is wrong if this issue on my side please tell me.

Outfluencer commented 3 years ago

witch minecraft version was the client?

ham1255 commented 3 years ago

First version i tired was 1.17 Then later 1.16 but issue seem to happen when 1.17 support added

Janmm14 commented 2 years ago

First, please showe your bungeecord config timeout value.

There was a change to Timeout behaviour in that timeframe between 1.16 and 1.17, which was required to fix an attack vector. Can you please check with Bungeecord 1557 an 1558 to see if hte issue was introduced with BungeeCord 1558?

ham1255 commented 2 years ago

its default value:

timeout: 30000

and issue seems to be stoped after using 1557 edit: it exists :/

ham1255 commented 2 years ago

Update:

after some research to fix this, since i am using linux as my main os, I told myself let me try windows. so i ran windows suddenly the issue went away on windows. but returning to linux issue was there. so hmmm i think i might have problem with my installtion. so i got another device. and ubuntu iso ready to install and when install finished and tested the issue was there. so hmm i told myself, it could something else. and went to the shell and i wrote

apt-get update && apt-get upgrade 

and issue was solved! I think it could some program had effect with networking? or the desktop service had some issue? or the a java bug? not sure tho.

so maybe close this?

Janmm14 commented 2 years ago

@ham1255 you can close it yourself