Romestead Hub

Romestead firewall settings

Open the right path for friends before changing worlds, passwords, or server names.

Short answer: allow the Romestead dedicated server through the host firewall, open UDP 8050, forward UDP 8050 on your router if hosting from home, and test direct connect with one remote friend before waiting for the public server list.

Firewall checklist

  1. Confirm the server is running and listening before changing firewall rules.
  2. Check the config port. If you use the default, plan around UDP 8050.
  3. Allow the server executable through Windows Firewall or your Linux firewall.
  4. If hosting from home, forward UDP 8050 to the host PC local IP address.
  5. Reserve the host PC local IP so router forwarding does not break later.
  6. Ask a friend outside your network to test direct connect.
  7. If direct connect works, stop changing firewall rules and troubleshoot server-list visibility separately.

Where the block can happen

LayerWhat to checkCommon mistake
Server appServer process is actually runningFixing firewall while the server is closed.
Windows FirewallAllow the server app or UDP portAllowing only private networks when friends connect from outside.
Linux firewallAllow UDP 8050Opening TCP only.
RouterForward UDP 8050 to the host PCForwarding to an old local IP.
VPS provider firewallOpen UDP 8050 in the cloud panelOpening Linux firewall but forgetting provider rules.

TCP, UDP, or both?

For Romestead server connection troubleshooting, treat UDP 8050 as the important rule. If your router only offers a combined TCP/UDP option, choosing both is usually fine while testing. If it asks for separate rules, make sure UDP is included.

When firewall is not the issue

Related Romestead server guides

Use port 8050 not working for deeper connection checks, multiplayer not working for the full join path, server not showing in list when direct connect works, and VPS setup if home networking keeps blocking friends.