pixly.

Fix NetherNet errors and Terracotta errors in Geyser

Fix NetherNet and Terracotta errors on a Geyser server: check your InitialConnection code, update Geyser, and verify TCP and UDP access.

AlekseiFounder
6 min read
GeyserMC logo above a closed stone doorway, terracotta blocks and a disconnected cable on a grass platform.

Pixly supported Bedrock 26.60 from day one. Turn on Bedrock crossplay in Settings and restart; Pixly installs and configures Geyser and Floodgate automatically. Java and Bedrock players join on the same address.

What the NetherNet, Terracotta and Door codes mean

Bedrock 26.60, released on 27 October 2026, joins servers only over NetherNet.12 When a join fails with a NetherNet error, Terracotta or Door, press Show details to see its InitialConnection number. Use that number below to choose which checks to run.

A Bedrock 26.60 join starts with signaling, a web request over TCP that finds the server, and then plays over UDP.3 GeyserMC's support notes match each InitialConnection number to a cause:4

CodeDetailsCauseFix
TerracottaInitialConnection-149Geyser on RakNet, or TCP port closedThe four steps below
DoorInitialConnection-83UDP blocked, or server behind NATOpen UDP, set advertise-addresses
NetherNetInitialConnection-13No answer over NetherNet or RakNetCheck the address and both ports
NetherNetInitialConnection-122Connection opened, then closedUpdate Geyser; inspect disconnect logs if it continues

Terracotta with 149 means the server does not speak NetherNet, or its signaling is unreachable.4 A NetherNet error with 13 means the server answered neither way, so check the address first. With 122, the connection opened and then closed; Geyser builds before 1273 did this on Alpine Linux.5

Fix the Terracotta error on a Geyser server

Download Geyser from GeyserMC's download page, then:

  1. Update Geyser to the latest build. Build 1273, from 26 October, is the first that supports Bedrock 26.60.6
  2. Set transport: nethernet in Geyser's config. It is in plugins/Geyser-Spigot/ on Paper and config/Geyser-Fabric/ or config/Geyser-NeoForge/ on Fabric or NeoForge.7 Builds up to 1279 keep an old raknet line; build 1280 changes it for you.89
  3. Open the Geyser port for TCP and UDP. With Docker, publish -p 19132:19132 -p 19132:19132/udp.3 It cannot be the Java server's port.7
  4. Restart and test a Bedrock join. Built-in signaling started on http://0.0.0.0:19132 confirms Geyser's signaling server started.8 Join from outside your network to check that players can connect over TCP and UDP.3

The bedrock: section of the config then reads:

bedrock:
  port: 19132
  transport: nethernet

A proxy, Geyser Standalone or a host that only opens the Java port needs more than this; the Geyser and Floodgate setup guide covers those cases.

Fix the Door error: check UDP and NAT

Door with 83 means signaling over TCP worked and game traffic over UDP did not get through. A port forward or Docker mapping for TCP only causes this, so add UDP on the same port. One owner cleared Door 83 on a 26.60 console by fixing UDP while TCP already worked.10

If Geyser is behind a router or NAT and Door continues, GeyserMC advises adding your public IP to bedrock.signaling.advertise-addresses and restarting.4 Merge this into the existing bedrock: section, replacing 203.0.113.10 with your server's public IP:

bedrock:
  signaling:
    advertise-addresses:
      - "203.0.113.10"

Geyser warnings after 26.60 and what they mean

Geyser prints these at startup, and from build 1273 also messages operators about NetherNet when they join.6

Geyser console warnings

WARNING! NetherNet support is NOT enabled.

The config still says raknet. Set transport: nethernet and restart.

WARNING! Raknet-only transport has now been REMOVED.

Build 1280 moved the config to NetherNet. Open the port for TCP as well as UDP.

NetherNet is not available on Linux (amd64)

Geyser could not load its NetherNet library: reported causes are a missing libcrypto.so.3 (install libssl3 on Ubuntu) and a read-only /tmp.1110

Skip that last warning's advice to set transport to raknet: GeyserMC says Bedrock 26.60 does not connect over RakNet at all.2

Tested: what each broken setup does to a join

We ran five setups on 1 November 2026 with Paper 26.3, Geyser 2.12.1 and a NetherNet test client built on gophertunnel, an open-source Bedrock library.8

GeyserSetupJoin result
1279transport: raknetRefused at once over TCP
1279transport: nethernetLogin reaches Geyser
1280transport: raknetMoved to NetherNet; login reaches Geyser
1280TCP 19132 closedRefused at once over TCP
1280UDP 19132 droppedSignaling works; times out after 30 s

The test client reports the step where each join stopped. Outside reports match the working setup: an owner joins from Bedrock 26.60 on Windows over NetherNet,12 and the groundsgg server images restored 26.60 joins with build 1280 and TCP plus UDP 19132.13

NetherNet and Terracotta error questions

How do I fix the NetherNet error as a player?

Confirm the server address and your game version. Send the owner the full Show details screen, your device and game version, and whether other players can join. Codes 13 and 122 mean the connection failed or closed; the owner can use the details to check the server logs.

Why doesn't my Geyser server show under LAN Games on 26.60?

Bedrock 26.60 looks for LAN worlds on UDP port 7551, where Geyser does not answer yet, per a report still open on Geyser's issue tracker on 1 November 2026.12 Add the server by address under Servers instead.

Why can't players on an older Bedrock version join?

Build 1273 removed Bedrock 26.30, and current Geyser builds accept Bedrock 26.40 to 26.60.614 Players on an older version update the game from their device's store.

Footnotes

  1. minecraft.wiki, Bedrock Edition 26.60: released 27 October 2026, protocol 2225. Checked 1 November 2026. ↩

  2. GeyserMC, Preparing Your Geyser Server for NetherNet, 8 October 2026: "Bedrock clients will stop connecting over RakNet." ↩ ↩

  3. GeyserMC, Port forwarding: "players find the server over TCP (signaling), and play on it over UDP." Checked 1 November 2026. ↩ ↩ ↩

  4. GeyserMC, support tags for Bedrock error codes, GeyserDiscordBot: InitialConnection-149 is "Terracotta", UnsupportedTransport, and "may also appear if the signaling server is unreachable or not running"; 83 is "Door", NetherNetICE, "try adding your public IP address to the advertise-addresses config option"; 13 is "NetherNet", LegacyDisconnect, shown "if both attempts time out"; 122 is "NetherNet", NetherNetDataChannelClosed. Checked 1 November 2026. ↩ ↩ ↩

  5. GeyserMC/Geyser issue #6807, closed: on the Alpine image the client "shows InitialConnection-122 (NetherNetDataChannelClosed) after 30 s"; fixed in build 1273. ↩

  6. GeyserMC, Geyser 2.12.1 build list: build 1273, 26 October 2026, "Support 26.60", "Surgically remove 26.30" and "Add operator join message informing NetherNet deprecation, change bedrock.transport config default to nethernet". Checked 1 November 2026. ↩ ↩ ↩

  7. GeyserMC, Geyser setup guide: "Geyser uses it over both TCP and UDP, so it cannot be the port of the Paper / Spigot server." Checked 1 November 2026. ↩ ↩

  8. Pixly test, 1 November 2026: Paper 26.3 and Geyser-Spigot 2.12.1 builds 1279 and 1280 in Docker, joined by a NetherNet client built on gophertunnel on the same network; ports closed with firewall rules inside the server's container. Build 1279 generated a new config with transport: nethernet and kept an existing transport: raknet, logging WARNING! NetherNet support is NOT enabled. ↩ ↩ ↩

  9. GeyserMC, Remove RakNet-only transport (#6843), build 1280, 31 October 2026 (UTC). ↩

  10. spruyt-labs, run NetherNet transport for Bedrock 26.60 clients, closed 28 October 2026: "The first console test failed with initialconnection 83. TCP signaling worked", then UDP was fixed and "A console on Minecraft 26.60 reaches the server list and joins"; startup had failed with "/tmp/datachannel-java-...: Read-only file system". ↩ ↩

  11. GeyserMC/Geyser issue #6852, "NETHERNET: Terracotta error", 31 October 2026: the log shows libcrypto.so.3: cannot open shared object file, and a Geyser contributor answers "Installing libssl3 should resolve your issue." ↩

  12. GeyserMC/Geyser issue #6853, 31 October 2026, open on 1 November: "Joining by address from the Servers tab works fine over NetherNet" on Bedrock 26.60 for Windows with Geyser 2.12.1-b1279, while the client's LAN broadcast to UDP 7551 gets no answer because "Nothing listens on UDP 7551". ↩ ↩

  13. groundsgg, fix(geyser): restore Bedrock 26.60 connections, merged 1 November 2026: pins Geyser 2.12.1 build 1280 and opens TCP and UDP 19132. ↩

  14. GeyserMC, Supported versions: "Geyser currently supports Minecraft Bedrock 26.40-26.60 and Minecraft Java 26.3." Checked 1 November 2026. ↩

AlekseiFounder at Pixly

Writes about running Minecraft servers — measured numbers, reproducible fixes, and the tradeoffs hosting pages leave out.

Keep reading.