Skip to content
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

Open
4 tasks done
MATRIX-feather opened this issue Dec 3, 2024 · 15 comments
Open
4 tasks done

Can't join 1.21.3 Folia server with 1.21.1 client #925

MATRIX-feather opened this issue Dec 3, 2024 · 15 comments
Labels

Comments

@MATRIX-feather
Copy link

'/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

  1. Setup a 1.21.3 Folia server
  2. Join with a 1.21.1 client
  3. The client got kicked

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

  • Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. Velocity), not on both.
  • I have included a ViaVersion dump.
  • If applicable, I have included a paste (not a screenshot) of the error.
  • I have tried a build from https://ci.viaversion.com/ and the issue still persists.
@Barvalg
Copy link
Member

Barvalg commented Dec 3, 2024

Platform: 1.21.3--DEV--815dd7b%20%28MC%3A%201.21.3%29
ViaVersion (5.1.2-SNAPSHOT): Even with master
ViaBackwards(5.1.2-SNAPSHOT): Even with master

@kennytv
Copy link
Member

kennytv commented Dec 3, 2024

Cannot reproduce. You probably have a broken proxy or client

@MATRIX-feather
Copy link
Author

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

@kennytv
Copy link
Member

kennytv commented Dec 7, 2024

What's your compression threshold in the server properties file?

@MATRIX-feather
Copy link
Author

What's your compression threshold in the server properties file?

-1

@kennytv
Copy link
Member

kennytv commented Dec 7, 2024

Can you try setting it to a really high number instead? I haven't been able to reproduce this yet for some reason

@MATRIX-feather
Copy link
Author

Just tried 8192000 and 2147483647(huh), no kick.

It seems that this only happens when the compression is disabled.

@MATRIX-feather
Copy link
Author

MATRIX-feather commented Dec 7, 2024

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

@nicolube
Copy link

nicolube commented Dec 8, 2024

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:

[04:20:39] [Render thread/ERROR]: Registry loading errors:
> Errors in registry minecraft:enchantment:
>> Errors in element minecraft:range:
java.lang.IllegalStateException: Failed to parse value {anvil_cost:1,description:{translate:"custom_enchantment.range"},max_cost:{base:0,per_level_above_first:0},max_level:1,min_cost:{base:0,per_level_above_first:0},slots:["mainhand","offhand"],

@nicolube
Copy link

nicolube commented Dec 8, 2024

@MATRIX-feather
Pls check ur client-log if u see something simellar.

@MATRIX-feather
Copy link
Author

Hi,

I checked my client logs, but sadly, nothing worth to report:

[13:18:59] [Render thread/INFO] (Minecraft) Connecting to localhost, 25565
[13:19:00] [Netty Epoll Client IO #1/WARN] (Minecraft) Unknown feature flag: minecraft:winter_drop
[13:19:01] [Render thread/WARN] (Minecraft) Not all defined tags for registry ResourceKey[minecraft:root / minecraft:item] are present in data pack: minecraft:flowers, minecraft:tall_flowers, minecraft:trim_templates
[13:19:01] [Render thread/WARN] (Minecraft) Not all defined tags for registry ResourceKey[minecraft:root / minecraft:block] are present in data pack: minecraft:tall_flowers
[13:19:01] [Render thread/WARN] (Minecraft) Client disconnected with reason: Internal Exception: io.netty.handler.codec.DecoderException: Pipeline has no inbound protocol configured, can't process packet PooledUnsafeDirectByteBuf(freed)
[13:19:05] [Render thread/INFO] (Minecraft) Found non-pack entry '/media/neko/Btrfs/minecraft/profiles/kinopico/resourcepacks/folder.json', ignoring

And for the log you posted, I believe it's a different issue, since the client can at least join the server 🤔

@LaserSlime
Copy link

Can also confirm this for 1.20.6 clients on 1.21.3 Paper servers

@FlorianMichael
Copy link
Member

@nicolube Your issue is different and should be reported separately;

Seems to be valid on Folia server, doesn't happen on Paper ones.

@adabugra
Copy link

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

[10:42:03 INFO]: adabugra joined the game
[10:42:03 INFO]: adabugra[/176.234.131.2:27863] logged in with entity id 20 at ([world]-11.5, 113.0, 0.5)
[10:42:03 INFO]: adabugra lost connection: Internal Exception: io.netty.handler.codec.DecoderException: Pipeline has no inbound protocol configured, can't process packet PooledUnsafeDirectByteBuf(freed)
[10:42:03 INFO]: adabugra left the game

@cgw2023
Copy link

cgw2023 commented Jan 5, 2025

Tested here also, when network-compression-threshold is -1 on folia 1.21.4/1.21.3, this problem will occurs.

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)
client: vanilla 1.21.1 / vanilla 1.20.4 (any version that is not same as server version which triggers viaversion, so if 1.21.4 client login 1.21.4 server, this problem does not occurs because viaversion is not running for same version session)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants