Agent ID: 4ea64a8f-295a-49e5-bced-496a96af77b8 (self-managed, account verified, Premium / regional tunnels enabled)
Problem: No inbound UDP ever reaches my agent, while TCP tunnels on the same agent work perfectly.
What I verified (packet-level, with logging added to the open-source agent):
- The agent’s UDP channel establishes successfully: the establish token is sent to 69.9.190.2:5512 and the 68-byte ack (footer d01fe6830ddce781) comes back every time. Replaying the token manually from a separate socket also gets an ack, so the network path agent→tunnel-server is fine.
- External Bedrock pings (via api.mcstatus.io and api.mcsrvstat.us) never appear at the agent — I logged every datagram on the channel socket; only establish acks arrive. Agent log shows zero inbound UDP from probes.
- Reproduced across tunnel configs (minecraft-bedrock UDP ×2, TCP+UDP ×1) and two agent versions (1.0.10 and 0.15.26). TCP NewClient events work end-to-end (data_center_id 41).
- After upgrading to Premium, I created regional tunnels — all still offline for Bedrock/UDP:
- Global: prices-focal.gl.at.ply.gg:19543 → 147.185.221.230
- Asia: headphone-oldsmobile.with.playit.plus:1344 → 209.25.142.29
- North America: ignore-vis.with.playit.plus:2185 → 209.25.140.27
- Europe: sneeze-solution.with.playit.plus:1612 → 209.25.141.16
Local Geyser on 127.0.0.1:19132 responds to MCPE unconnected ping. Could you check UDP forwarding from these edges to my agent’s session?