Offer Why us? How it works?
Guide

Minecraft Bedrock Server Port: 19132 and Forwarding

Bedrock servers listen on port 19132 by default – but on newer versions forwarding that one UDP port often isn't enough anymore. Here's which ports a Bedrock Dedicated Server uses, how to change them in server.properties, what to forward on your router since NetherNet, and how to check what's blocking your friends.

Updated: 6 min read
Table of contents
  1. What port does a Minecraft Bedrock server use?
  2. Why do you have to type the port in separately?
  3. How do you change the port of a Bedrock server?
  4. Which ports should you forward on your router?
  5. Why does port forwarding not work?
  6. How do ports work for a Bedrock server on Spot.gg?
  7. FAQ
  8. What is the default Minecraft Bedrock port?
  9. Is the Bedrock port TCP or UDP?
  10. Do I need to forward 19133?
  11. Can I use 25565 for a Bedrock server?
  12. Why does my Bedrock server work on Wi-Fi but not for friends?
  13. What port does my Spot.gg Bedrock server use?

What port does a Minecraft Bedrock server use?

By default, Bedrock Dedicated Server uses port 19132 UDP for IPv4 and 19133 UDP for IPv6. That's what the game fills in automatically when you click "Add Server". Since version 1.26.50, Bedrock connects players through NetherNet, which adds TCP on the server port and separate UDP ports for gameplay.

Port Protocol server.properties key What it's for
19132 UDP (and TCP since 1.26.50) server-port Main server port – players type this in
19133 UDP server-portv6 Same server over IPv6
Extra UDP ports UDP server-udp-ports Gameplay traffic under NetherNet (1.26.50+)

For comparison, Minecraft Java uses 25565 TCP. The two editions don't share ports or protocols, so a Java port forward does nothing for a Bedrock server.

Why do you have to type the port in separately?

Because Bedrock's "Add Server" screen has separate "Server Address" and "Port" fields, and Bedrock doesn't look up the port from DNS the way Java can. If you type address:port into the address field, or leave 19132 when the server uses another port, the game simply fails to connect.

That's also why hosts give you a port that's usually not 19132: many servers share one machine and each needs its own port. Always copy the port from your host's panel.

How do you change the port of a Bedrock server?

Edit server-port (and server-portv6) in server.properties while the server is stopped, then start it again.

server-port=19132
server-portv6=19133

A few rules:

  • Use a free port – two servers on one PC can't use the same port. Typical choices are numbers above 1024 that nothing else on your machine uses.
  • Change the router too – if you forwarded 19132 and switch to another port, update the port forward.
  • Tell your players – everyone has to change the port in their saved server.
  • LAN visibility – with enable-lan-visibility=true the server also answers LAN discovery on the default 19132/19133, even if server-port is set to something else. Turn it off if you run two servers on one machine and they clash.

Which ports should you forward on your router?

For older Bedrock versions, forwarding UDP 19132 (and 19133 for IPv6) was enough; since 1.26.50, forward the server port for both TCP and UDP and set fixed UDP ports for gameplay. Under NetherNet, the connection is negotiated over TCP on the server port, and the game itself runs over UDP on ports the server announces to players.

On a home server:

  1. Give the server PC a fixed local IP address (a DHCP reservation in the router settings is easiest).
  2. In the router, forward the server port (19132 by default) for TCP and UDP to that local IP.
  3. Set fixed gameplay ports with server-udp-ports in server.properties and forward them as UDP too. The exact format is described in bedrock_server_how_to.html, which ships with the server.
  4. Allow bedrock_server through the operating system's firewall. On Windows, when Windows Defender Firewall asks on first start, allow it on the network type you're using.
  5. Test from outside your home network, for example from a phone on mobile data.

If the server works on your Wi-Fi but nobody can join from outside, the port forward isn't working – most often because of CGNAT (below) or because only UDP was forwarded on a 1.26.50+ server.

Why does port forwarding not work?

The usual reasons are CGNAT at your ISP, forwarding to the wrong local IP, a firewall on the PC, or only half of the ports forwarded.

Problem How to recognise it What to do
CGNAT The WAN address in your router differs from your public IP shown by "what is my IP" sites Ask your ISP for a public IP, use a tunnel service, or move the server to hosting
Wrong local IP The PC's IP changed after a restart Set a DHCP reservation, then fix the forward
PC firewall Works on the PC itself, not from other devices at home Allow bedrock_server in the firewall
Only UDP forwarded (1.26.50+) Server visible but players can't connect Forward TCP on the server port and the UDP gameplay ports
Version mismatch "Outdated server" / "Outdated client" Update the server or the game

A note on port checkers: online "open port" tools usually test TCP only. Bedrock's gameplay runs over UDP, which can't be reliably tested from outside, so "port closed" in such a tool doesn't always mean the server is unreachable – and "open" doesn't guarantee players can play. A real test with a player outside your network is what counts.

How do ports work for a Bedrock server on Spot.gg?

You don't forward anything: every server gets its own address and ports, and the Bedrock settings for them are written automatically at every start. Each Bedrock server on Spot.gg has:

  • a main port (TCP and UDP) – the one players type into the "Port" field,
  • three additional UDP ports used by Bedrock for player connections – for IPv6 and NetherNet gameplay (server-portv6 and server-udp-ports).

All of them are listed in the "Network" tab, with the protocol and a copy button. Because they're set at every start, don't change server-port, server-portv6 or server-udp-ports in server.properties – they’re overwritten at the next start anyway, and a different port only leaves your players with a wrong number.

To connect, click "How to connect?" in the panel: the address and the port are shown as two separate fields, exactly like the game asks for them. Bedrock servers on Spot.gg use the standard server address with a port; a custom domain isn't available for Bedrock servers.

New to it? A Bedrock server is free for the first 24 hours, no card needed, then from $3.90 / month with 2 GB of RAM. Console players add servers differently – see how to join a Minecraft server on Xbox, PS5 and Switch.

FAQ

What is the default Minecraft Bedrock port?

19132 UDP for IPv4 and 19133 UDP for IPv6. Since Bedrock 1.26.50 the server also uses TCP on the main port and additional UDP ports for gameplay (NetherNet).

Is the Bedrock port TCP or UDP?

Traditionally UDP only. On Bedrock Dedicated Server 1.26.50 and newer, the main port is used for both TCP (connection setup) and UDP, and gameplay runs over UDP on separate ports.

Do I need to forward 19133?

Only if players connect over IPv6. Most home setups get by with the IPv4 port, but forwarding 19133 UDP does no harm.

Can I use 25565 for a Bedrock server?

Technically you can set any free port, including 25565, but it's the Java default and only invites confusion. Bedrock players have to type the port in anyway, so pick any free number and tell them.

Why does my Bedrock server work on Wi-Fi but not for friends?

Friends from outside need a working port forward. Check for CGNAT (WAN IP in the router different from your public IP), make sure the forward points at the server PC's current local IP, and on 1.26.50+ forward TCP on the server port as well as UDP.

What port does my Spot.gg Bedrock server use?

Its own port, usually not 19132. You'll find it under "How to connect?" in the server panel and in the "Network" tab, next to the additional UDP ports Bedrock uses for player connections.

Other guides