Connectivity Problem with Minecraft Bedrock - Bedrock server external connections not working

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Proteus’ v2.8.0.8 (Mainline)
Virtualization VMware
Application Minecraft Bedrock
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

Subject

Minecraft Bedrock external connectivity failure — AMP Proteus 2.8.0.8 / UDP 19132

Problem

I am running a Minecraft Bedrock Dedicated Server through AMP (Proteus 2.8.0.8 Mainline) on a Debian Linux VM under Proxmox.

The server works correctly from the local network, but cannot be reached externally over UDP 19132.

Environment

  • AMP: Proteus v2.8.0.8 Mainline
  • Minecraft: Bedrock Dedicated Server
  • AMP module: GenericModule / Bedrock
  • Host: Debian Linux VM under Proxmox
  • Server IP: 192.168.7.101
  • Public IPv4: 50.69.213.63
  • Bedrock port: UDP 19132
  • IPv6 Bedrock port: 19133
  • AMP-managed/internal port observed: UDP 7551
  • World/instance: Realms

What works

The Bedrock server is running and can be joined successfully from the local network using:

192.168.7.101:19132

The server therefore loads correctly and the Bedrock service is functional locally.

What does not work

External clients cannot connect using:

50.69.213.63:19132

This remains true when connecting from a phone using cellular/5G rather than Wi-Fi.

DNS is not involved in the current test; I am testing the raw public IP directly.

Router / firewall testing

The UDM-SE has port forwarding configured for UDP 19132 to:

192.168.7.101:19132

I have also tested forwarding UDP 19132 directly to the AMP/Bedrock process’s observed port 7551, but that did not produce a connection either.

TCP forwarding was also configured/tested, although the primary problem is UDP.

Most importantly, packet capture on the server proves that the external UDP traffic is reaching the VM.

While attempting to connect externally from a phone with public source IP 209.52.133.119, tcpdump showed:

209.52.133.119.xxxxx > 192.168.7.101.19132: UDP, length 548

However, there was no response from the server.

So the WAN connection, public IP, NAT, and port forwarding are not simply preventing the packet from reaching the server.

AMP / port observations

AMP initially reported the server IPv4 port as not listening, and there was subsequently a port-related error in AMP which was corrected.

AMP now reports the server port as listening.

However, Linux socket inspection shows:

  • UDP 19132: no listening socket
  • UDP 19133: no listening socket
  • UDP 7551: listening by bedrock_server
  • UDP 12820: listening by AMP_Linux_x86_6

The Bedrock process is therefore actually listening on 7551 rather than directly on 19132.

A local connection capture showed traffic involving both 19132 and 7551 during the initial connection/handshake. After the connection is established, traffic remains on 19132.

An external connection attempt, by comparison, produces traffic only to 19132 and nothing to 7551 or 12820, with no response.

Configuration checked

The instance’s server.properties contains:

server-port=19132

server-portv6=19133

The instance is configured to use NetherNet.

AMP’s LAN visibility setting is currently enabled.

AMP’s reverse-proxy configuration has approved hosts:

127.0.0.1

::1

Other troubleshooting

  • Fresh Bedrock AMP instance tested with the same external connectivity problem.
  • Local connectivity confirmed.
  • External UDP packet arrival confirmed with tcpdump.
  • Linux nftables rules were checked; no relevant 19132 rule was found.
  • The problem persists independently of DNS.
  • Other AMP server instances on the same general infrastructure are remotely accessible.
  • The problem has been reproduced from an external cellular connection.

I am particularly interested in whether this is related to the Nethernet/port-range handling introduced in recent AMP 2.8.x releases. AMP 2.8.0.8 specifically mentions changes to Generic Module port-range handling for Minecraft Bedrock Nethernet.

At this point I would appreciate guidance on what AMP expects for the external Bedrock UDP path when the Bedrock process is listening on 7551 while AMP advertises/receives traffic on 19132.

Please let me know what logs or diagnostic information you need.

Reproduction Steps

  • I’m not sure what is needed for this box..
  • Entering text to create the ticket..
  • This field seems to be lacking a description on what I am to put here, but I require 3..? Why..?