U
/u/Jok030
Guest
Hey everyone,
I’m facing a massive issue trying to get Bedrock crossplay working on my server and I really need some experienced admin advice.
The server is hosted on EternalZero (Eternal Hosting). Originally, it ran perfectly on Paper (1.21.11) with Geyser, Floodgate, and ViaVersion. However, we wanted to use some specific mods, so we made the switch to Fabric. Since that moment, everything broke.
Bedrock players can no longer connect. They just get stuck on the "connecting to external server" screen followed by a "NetherNet" connection failure. Java players can always join fine.
Here is exactly what I have tried so far:
I wiped the
Since EternalZero uses specific port forwarding/allocations, did putting my custom IP into the Geyser config break the internal Docker/Node binding? And how can I get back to a working Fabric environment if the devs don't support 1.26.2 yet? Should I look into a separate Velocity proxy or ViaProxy setup to bypass the hoster's port restrictions entirely?
Any help would be deeply appreciated!
submitted by /u/Jok030
[link] [comments]
Continue reading...
I’m facing a massive issue trying to get Bedrock crossplay working on my server and I really need some experienced admin advice.
The server is hosted on EternalZero (Eternal Hosting). Originally, it ran perfectly on Paper (1.21.11) with Geyser, Floodgate, and ViaVersion. However, we wanted to use some specific mods, so we made the switch to Fabric. Since that moment, everything broke.
Bedrock players can no longer connect. They just get stuck on the "connecting to external server" screen followed by a "NetherNet" connection failure. Java players can always join fine.
Here is exactly what I have tried so far:
- Upgraded to 1.26.2: I updated everything to the latest snapshot/version, but it failed completely because the Geyser devs don't have a stable Geyser-Fabric release for 1.26.2 yet.
- Tried changing IP Configs: I changed the
addressfields in the Geyser/Floodgate configs to my server's custom IP address instead of leaving them at0.0.0.0. - Tried downgrading back to Paper / Spigot: Because Fabric didn't work, I tried reverting back to Paper and even plain Spigot to restore the old working state. But even going back now fails completely—Bedrock players still get the exact same NetherNet error, or the server refuses to start properly with newer Geyser files.
I wiped the
config/Geyser-Fabric and plugins folders multiple times to prevent old dependency conflicts, but nothing seems to clear this network block.Since EternalZero uses specific port forwarding/allocations, did putting my custom IP into the Geyser config break the internal Docker/Node binding? And how can I get back to a working Fabric environment if the devs don't support 1.26.2 yet? Should I look into a separate Velocity proxy or ViaProxy setup to bypass the hoster's port restrictions entirely?
Any help would be deeply appreciated!
submitted by /u/Jok030
[link] [comments]
Continue reading...