Port forwarding a Minecraft server means telling your router to send incoming connections on port 25565 (Java) or 19132–19133 (Bedrock) straight to your computer, instead of blocking them like it normally would. Without it, only people on your own Wi-Fi can join — with it, anyone with your public IP can connect from anywhere.

Here’s the full process, what to do if it doesn’t work, and a couple of ways to skip router configuration entirely if you’d rather not deal with it.

The Basic Steps (Any Router)

The process is the same shape on every router, even though the menu names differ slightly between brands:

  1. Find your computer’s local IP address. On Windows, open Command Prompt and run ipconfig — look for “IPv4 Address” (something like 192.168.1.100). On Mac or Linux, it’s in your network settings or ifconfig.
  2. Set that IP as static, not automatic. If your router hands out a new local IP later, your forwarding rule stops pointing at the right device. This is the single most common reason a working setup suddenly “breaks” a week later.
  3. Log into your router’s admin page. Usually 192.168.1.1 or 192.168.0.1 typed into a browser. Credentials are often on a sticker on the router itself if you’ve never changed them.
  4. Find the port forwarding section — look under “Advanced,” “NAT,” or “Firewall” depending on the brand (Netgear: Advanced → Port Forwarding; TP-Link: NAT Forwarding; Linksys: Security → Apps and Gaming).
  5. Create the rule: protocol TCP (and UDP for Bedrock), external port 25565, internal IP set to your computer’s static local IP, internal port 25565.
  6. Save, and restart the router if it asks you to.
  7. Find your public IP by searching “what is my ip” on Google, and share your.public.ip:25565 with friends — that’s what they type into Minecraft’s “Add Server” screen.

A free tool like canyouseeme.org lets you check whether port 25565 is actually open from outside your network before you tell anyone to try connecting — it saves a round of “it’s not working” messages back and forth.

If You’re on Frontier (or Another ISP-Locked Router)

Frontier routers handle this the same way underneath, but the menu path is its own small puzzle: log into the router (often at 192.168.1.1, though some Frontier/Arris models use a different default), then look for “Port Forwarding” or “Virtual Servers” under the Advanced or Firewall tab. If your specific Frontier router model isn’t behaving the way generic guides describe, searching your exact model number plus “port forwarding” usually turns up a dedicated walkthrough — router firmware varies enough between ISP-provided hardware that a generic guide can only get you most of the way there.

Why It Sometimes Just Won’t Work: CGNAT

If you’ve followed every step correctly and it still doesn’t work, the most likely cause is CGNAT (Carrier-Grade NAT) — a setup a lot of ISPs use where your router doesn’t actually have a true public IP. Instead, your address is shared with other customers behind the scenes, which makes traditional port forwarding impossible no matter how correctly you configure it.

You can usually tell if this is your situation: log into your router and check the WAN/internet IP it reports. If it starts with 100.64 through 100.127, that’s a strong sign you’re behind CGNAT. Some ISPs will sell you a static IP add-on to get around this; others won’t offer one at all.

Other Common Issues

  • Double NAT. If your ISP’s modem connects to your own separate router, you may need to either forward the port on both devices or put the ISP modem into bridge mode so only your router handles NAT.
  • Firewall blocking the port locally. Your computer’s own firewall (Windows Defender, etc.) can block the connection even after the router’s side is correctly configured — check that your Minecraft server or Java is allowed through.
  • Dynamic public IP. Most home connections get a new public IP periodically (router restarts, ISP resets). If friends suddenly can’t connect, check whether your public IP changed before troubleshooting anything else.
  • Server not actually running. Obvious, but worth checking first — the port only shows as “open” while something is actively listening on it.

Is Port Forwarding Actually Safe?

This comes up a lot, and the honest answer is: forwarding the single port your Minecraft server uses is low-risk, not risk-free. You’re opening one specific door, not your whole network — nothing happens through that port unless your Minecraft server software is the thing listening on the other end. The real exposure is your public IP becoming visible to anyone you give it to (and, if your server isn’t whitelisted, anyone who finds it by scanning), which mainly matters if you’re worried about griefers or basic DDoS annoyance rather than someone “hacking your computer” through Minecraft itself. Keeping a whitelist, not posting your IP publicly, and not running the server software with admin/root privileges covers most of the realistic risk.

Skipping Port Forwarding Entirely

If your connection is behind CGNAT, your router won’t cooperate, or you’d just rather not touch firewall settings at all, tunneling tools solve the same problem from the other direction — instead of opening a path through your router, they create a connection from their own servers straight to your PC, so nothing on your end needs to change.

playit.gg is the most common free option built specifically with Minecraft in mind — install their client, run it alongside your server, and it gives you an address to share instead of your own IP. Tailscale is a more general-purpose option that works similarly but is built for connecting devices privately rather than Minecraft specifically, which makes it a reasonable pick if you’re already using it for something else.

If You’re Running More Than a Quick Vanilla Server

All of the above gets one Minecraft world online. If you’re setting up something bigger — multiple gamemodes, modes, plugins, a real community server — the port forwarding step is identical either way, but everything behind that open port gets more involved: linking servers together, configuring each gamemode, keeping performance reasonable as more plugins stack up.

A premade bundle like Oak Network doesn’t touch the networking side at all, but it does remove a lot of what comes after — popular gamemodes like Duels and Bedwars arrive already configured and linked together, so once your port forwarding (or tunnel) is working, there’s a lot less left to build from scratch.

The Bottom Line

Port forwarding itself is a five-minute job on a router that cooperates — find your local IP, make it static, create the rule, test it. Where people actually get stuck is CGNAT, double NAT, or ISP-specific router quirks, and in any of those cases a tunneling tool like playit.gg gets you online faster than fighting your router settings. Try the standard steps first; if port 25565 won’t show as open after a correct setup, that’s your sign to stop troubleshooting the router and switch to a tunnel instead.

Ready to put a server online? Check out Oak Network for a complete, pre-built gamemode setup you can have running the same day.