#Error when connecting on Bedrock: io.netty.channel.StacklessClosedChannelException

5 messages · Page 1 of 1 (latest)

acoustic wigeon
#

I run a public Minecraft server that peaks at around 9-15 players daily. Today when I restarted the server to update Paper and plugins, players that used Geyser to connect began to have issues with it. When they attempt to connect to my server on a Bedrock client they can see the MOTD and server name pop up but when they attempt to connect it gives them a "StacklessClosedChannelException" error. I've provided a console screenshot and in-game screenshot

I am hosting the server remotely using Oracle Cloud, specifically the "Always Free" 24 gb Ampere virtual machines
I am also using a service called "NeoProtect" which is a DDoS mitigation service that requires you to enable proxy protocol on both Paper and Geyser

Geyser dump: https://dump.geysermc.org/LfKwPcIrCUtmoUbp9WYz4XiLdN22vrNK

wanton doveBOT
# acoustic wigeon I run a public Minecraft server that peaks at around 9-15 players daily. Today w...

Possible problems:

  • enable-proxy-protocol should ONLY be enabled if you run a reverse UDP proxy in front of Geyser.
  • use-proxy-protocol should ONLY be enabled if either of these apply:
        1. Your server supports PROXY protocol (this has nothing to do with if you're using BungeeCord or Velocity).
        2. You have the exact same option enabled in your BungeeCord/Velocity config (it is off by default).
Git info

Latest: Yes
Commit: ef4acb1
Branch: master

Platform

Spigot

Listen address

0.0.0.0:19132 (internal IP)

Remote address

***:25565

Auth type

FLOODGATE

Server version

1.21.1-119-7cd4f2c (MC: 1.21.1)

Autoconfigured remote?

Yes

wanton doveBOT
wanton doveBOT
acoustic wigeon