8050 on the server machine, forward UDP 8050 on your router if hosting from home, then test direct connect before waiting for the public server list.Fast diagnosis
| Symptom | Likely cause | What to check |
|---|---|---|
| You can join locally, friends cannot | Router port forwarding or public IP issue | Forward UDP 8050 to the host PC local IP. |
| No one can join | Server not listening or firewall blocked | Server process, logs, Windows Firewall, Linux firewall. |
| Server runs but list does not show it | Browser delay or visibility issue | Try direct connect by IP and port first. |
| Worked yesterday, fails today | Local IP changed | Reserve a static LAN IP for the host PC. |
| You changed the config port | Rules still point to old port | Match config, firewall, and router forwarding. |
UDP 8050 checklist
- Confirm the server config uses port
8050, or note the custom port you changed it to. - Allow the Romestead server executable through Windows Defender Firewall.
- If using Linux, allow UDP
8050in your firewall or provider rules. - On your router, forward UDP
8050to the hosting PC local IP address. - Make sure the host PC keeps the same local IP.
- Ask a friend to test direct connect using your public IP and port.
Common mistake: TCP only
Many router screens ask whether a rule is TCP, UDP, or both. If you only create a TCP rule, friends may still fail to connect. Make sure UDP 8050 is allowed.
When to stop debugging
If your home router, ISP, or shared apartment network blocks inbound connections, managed hosting may be faster than fighting network rules.
Related Romestead server guides
If players still cannot find the server, use server not showing in list. If you are tired of router issues, compare hosting options. Before changing config, make a save backup.