Forge Server: Netty error; Malformed Byte around Byte 44.
Opened this issue ยท 24 comments
Error reading bee conversion recipe to packet causes multiplayer servers to misbehave, always resulting in a disconnect on the client side, or even a memory leak that OOM's the client.
Productive Bees 1.16.2 (newest)
Forge (on server) 33.0.22 (on client) 33.0.32
Optifine installed on client
Could you check if you still have the issue with the hotfix 0.3.1 I just put out? In any case it should provide some better debug info.
The issue persists, however it is a completely new error message this time (Port closed)
new client-side log:
debug.log
The registry loaded and everything, the server simply gave up.
I am not seeing any errors from my mod anymore, but the file ends in three error from BYG. Did you update this mod recently?
Is it possible to see the server log too? It might have more info.
the server log does not provide basically any error info at all, not even the debug.
BYG has been the same version whilst testing your mods. I have a feeling BYG is somehow incompatible with your mod.
I'll load up BYG and see if I have any problem. In the meantime there's one more thing to try. In the debug log it looks like there's a discrepancy in the mod list between the server and the client and I am not seeing a mod version check for productive bees
like this one:
[03Sep2020 22:14:38.075] [Netty Client IO #1/DEBUG] [net.minecraftforge.fml.network.NetworkRegistry/NETREGISTRY]: Channel 'minecolonies:net-channel' : Version test of '1.0' from server : ACCEPTED
to clarify, my modpack works fine on single player, just not via multiplayer.
The server does indeed go through a version check.
It is a custom modpack. the mods list can be found in the debug log at the top (scroll down some, look for "found valid mod" lines in the forge debug, that will list all of them for you)
I haven't bothered to write down 102 mod names so...
The version check I mean is the one between the client and the server, but it looks like they both have the mod.
With just BYG and PB 1.16.2 is running fine in SSP. Are you only having issues with server connection or does SSP not work either?
you will need to install the mod on a custom forge server on your machine in order to replicate the issue
I was very tired yesterday :) Got it fixed today and a new version will be approved in just a few minutes.
Okay, I will install the new update once it's out, and will let you know if it's fixed.
No more malformed bytes, however, now the server disconnects any attempts to connect with "took too long to login: connection reset"
even though I have random patches installed which makes the maximum login time 300 seconds, it suddenly throws this at around 40 seconds.
without productive bees it works fine yeah. the logs seem to say the client gives up sending handshake replies after the "registry: entity type" packet gets sent
it looks like somehow your mod is breaking the entity type registry packet causing the client to stop handshaking packets.
Thank you. I will start adding mods from your list to my server and see when it breaks.