8050, then check firewall, router forwarding, local IP changes, server password, and whether the server is actually still running.Start with the symptom
| Symptom | Likely problem | Next guide |
|---|---|---|
| Friends cannot join, but host can play locally | Router forwarding, firewall, or public IP issue | Port 8050 not working |
| Direct connect works, but the server list does not show it | Server browser delay, filter, or visibility issue | Server not showing in list |
| Server opens and closes before anyone joins | Runtime or launch error | .NET 8 Runtime fix |
| Players join but rubberband or disconnect | Upload speed, host load, or location problem | Server lag fix |
| Password or world settings seem wrong | Config mismatch or old config loaded | config.json explained |
Multiplayer checklist
- Restart the dedicated server and confirm the server console stays open.
- Ask one friend to test direct connect before testing the public server list.
- Use the correct public IP and port. If you changed the config port, share that exact port.
- Allow the server executable through Windows Firewall or your Linux firewall.
- Forward UDP
8050on the router to the host machine's current local IP. - Reserve the host machine's local IP so the router rule does not break tomorrow.
- Check whether the server has a password and whether friends typed it exactly.
- If direct connect works, stop changing firewall settings and focus on server-list visibility.
Common multiplayer mistakes
- Forwarding TCP only instead of UDP or both TCP/UDP.
- Forwarding to an old local IP after the router assigned a new one.
- Testing from the same home network and assuming outside friends will behave the same.
- Changing config, port, password, and world settings all at once.
- Assuming the public server list is required even when direct connect already works.
When to consider hosting
If multiplayer fails because your ISP blocks inbound connections, your router is locked down, or your PC cannot stay online, paid hosting can remove the network problem. Do not buy hosting just because one setting is wrong, but do compare hosting if every session starts with port and IP troubleshooting.
Related Romestead server guides
Use UDP 8050 troubleshooting for join failures, server list troubleshooting for browser visibility, server requirements for hardware and upload planning, and hosting options if home networking is the recurring blocker.