How to

Cox Panoramic Wifi Port Forwarding for a Game Server

How to forward game server ports on a Cox Panoramic Wifi gateway in the Cox WiFi app or cox.com/mywifi, and fix the errors and missing menus people hit.

Updated Oct 7, 2026 · 5 min read

On this page

Cox Panoramic Wifi gateways are set up through the Cox WiFi app or cox.com/mywifi, not a router login page. In the app tap WiFi, then View WiFi equipment, then Advanced Settings, scroll to Port Forwarding and tap Add Port Forwarding. Choose your server PC, enter the game's port and protocol, and save. If the menu errors out or friends still cannot join, the fixes below cover the usual causes.

Get these ready

  • The Cox WiFi app, signed in with the primary account User ID. Secondary users may not get equipment settings.
  • The server PC turned on and connected to the Panoramic gateway (or a Panoramic pod). The app only lists devices that are connected.
  • Your game's ports. Some popular ones:
Game Port Protocol
Palworld 8211 UDP
Minecraft: Java Edition 25565 TCP
Enshrouded 15637 UDP
Terraria 7777 TCP

Ports for every game we host are listed in how to port forward a game server.

Forward the port in the Cox WiFi app

  1. Open the Cox WiFi app. You will see tabs along the bottom such as Overview, WiFi, Home and Account.
  2. Tap WiFi.
  3. Tap View WiFi equipment.
  4. Tap Advanced Settings.
  5. Scroll to the bottom and tap Port Forwarding.
  6. Tap Add Port Forwarding.
  7. Pick the server PC from the device list.
  8. Choose a manual or custom setup, enter the port (or start and end of a range) and pick TCP, UDP or TCP/UDP.
  9. Save, then wait a minute for the gateway to apply it.

The gateway automatically keeps that device on the same local address once it has a port forward, which is what you want for a server.

Doing it in a browser instead

If the app keeps failing, use the website:

  1. Go to cox.com/mywifi and sign in.
  2. Select Network.
  3. Under Network Devices, select Gateway.
  4. Scroll down and select Advanced Settings.
  5. Open Port Forwarding and add the rule as above.

Both routes write to the same settings, so you only need one.

"Something went wrong" and other app errors

Cox's forums are full of people hitting an error when they open Port Forwarding. The common causes:

  • Gateway still updating or freshly restarted. Give it 15 minutes after a restart before changing settings.
  • Signed in as a secondary user. Switch to the primary account holder.
  • Gateway in bridge mode. In bridge mode the Panoramic gateway is just a modem, so it has nothing to forward. Forward on your own router instead.
  • App cache. Force close the app, or try the browser route above.

If none of that works, Cox support can push a refresh to the gateway from their side.

Panoramic Wifi pods

Pods extend the gateway's Wi-Fi. A PC connected through a pod is still on the gateway's network and appears in the same device list, so the rule works the same way. Wired servers are still better: a game server on a pod relays every packet over wireless twice, which adds latency for everyone who joins.

Using your own router with Cox

If you own a router and plug it into the Panoramic gateway, both devices do NAT and port forwards on the gateway reach only your router. Two ways out:

  • Bridge mode: in the app, go to WiFi, View WiFi equipment, Advanced Settings and turn on Bridge mode. The gateway's Wi-Fi and pods stop working; your router takes over and you forward ports there only.
  • Forward twice: forward on the gateway to your router's address, then on your router to the PC.

The double NAT guide explains how to tell which situation you are in. If you go with your own router, see the ASUS or Netgear Nighthawk guides.

Test from outside

  1. Start the server and wait for it to finish loading.
  2. Find your public IP: the gateway details in the app show it, or search "what is my IP" on the server PC.
  3. Ask a friend to join using publicIP:port, or use a phone on mobile data.

Testing from your own Wi-Fi with your own public IP often fails because many gateways do not loop that traffic back. That is the classic "it works for me on LAN but not with the public IP" situation explained in why friends cannot connect but you can.

If friends still time out

  • Windows Defender Firewall may be blocking the server program. Allow it on Private and Public, or add a port rule using our Windows Firewall guide.
  • Protocol mismatch. Palworld, Valheim and most Steam survival games use UDP. A TCP rule does nothing for them.
  • Rule pointing at the wrong entry. PCs with Wi-Fi and Ethernet appear as two devices. Use the one that is connected.
  • Public IP changed. Cox home addresses are dynamic. If friends could connect last week, check whether the address is still the same, or set up DDNS.

A scene from Palworld

When the house is the problem

Home hosting on Cox works, but you are relying on an app menu that sometimes breaks, a PC that must stay on and your upload speed. A hosted server has its own address and open ports with nothing to forward, plus a panel for settings, console and one click backups. With GamezServers you can split the bill with up to 10 friends, so nobody carries the whole cost.

FAQ

What is the Cox router login address?

Panoramic Wifi gateways are managed through the Cox WiFi app and cox.com/mywifi. The local admin page is limited or disabled on current firmware, so use the app or website.

Does Cox block any ports?

Cox filters a small number of ports on residential plans, mostly ones used by email and Windows file sharing. Normal game server ports are not on that list.

Does Cox use CGNAT?

Cox cable internet gives homes a public IPv4 address, so port forwarding works. If your WAN IP is in the 100.64.x.x to 100.127.x.x range, read how to tell if you are behind CGNAT.

Can I port forward with Cox bridge mode on?

Not on the gateway. In bridge mode you forward ports on your own router, which now holds the public IP.

Want a server without the setup?

From75¢

Pick a game, pay, play. Live the moment checkout finishes.

Keep reading