-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't join 1.21.3 Folia server with 1.21.1 client #925
Comments
Cannot reproduce. You probably have a broken proxy or client |
But the server is not running behind a proxy, the client doesn't use any as well I also tried launching a fresh client using the official launcher, still got this problem when connecting |
What's your compression threshold in the server properties file? |
-1 |
Can you try setting it to a really high number instead? I haven't been able to reproduce this yet for some reason |
Just tried 8192000 and 2147483647(huh), no kick. It seems that this only happens when the compression is disabled. |
The server configuration is available here, if needed: https://drive.google.com/file/d/1AXqjApi48VSpcIF9SyjLMeH-YK5uFJFJ/view?usp=sharing Server starts on port 25566, and server.properties.broken is the one that kicks the player |
Hello, I can reproduce this with Client Vanilla 1.21.1 -> Server PaperMC 1.21.3. According I recaived an invalid packet aka an Item:
|
@MATRIX-feather |
Hi, I checked my client logs, but sadly, nothing worth to report:
And for the log you posted, I believe it's a different issue, since the client can at least join the server 🤔 |
Can also confirm this for 1.20.6 clients on 1.21.3 Paper servers |
@nicolube Your issue is different and should be reported separately; Seems to be valid on Folia server, doesn't happen on Paper ones. |
I can reproduce this with Client Fabric 1.21.1 -> Server Folia 1.21.4 with ViaBackwards-5.2.1 and ViaBackwards-5.2.0
|
Tested here also, when network-compression-threshold is recommended to set to -1 when server is behind velocity/bungee, in this test case, I am connecting the server directly and it trigger this error. I can also confirm that his problem occurs even if the server is behind velocity/bungee(tested). server: luminol-1.21.4-bundler (folia fork, folia also have this problem) |
'/viaversion dump' Output
https://dump.viaversion.com/b97219b4aed7cd8b3d0ea3d23cb0be5df4c0eb2ee72a9e7afdb9c822032b5a9a
Console Error
https://mclo.gs/SyuLCcT
Bug Description
When connecting 1.21.3 Folia server with 1.21.1 client, the client got kicked with
io.netty.handler.codec.DecoderException: Pipeline has no inbound protocol configured, can't process packet PooledUnsafeDirectByteBuf(freed)
Steps to Reproduce
Expected Behavior
The client can join the server
Additional Server Info
The server is running Folia version 1.21.3-DEV-dev/1.21.3@815dd7b (2024-12-02T12:17:53Z)
No other plugins are installed, and the client is 1.21.1 vanilla
Checklist
The text was updated successfully, but these errors were encountered: