How to Fix Starbound Server Lag and Connection Problems

Most Starbound server problems come from one of four different causes: network latency, a local performance slowdown, a server that never finished starting, or a damaged world/mod setup. The fix depends on which symptom you actually have. First record the exact error and copy storage/starbound.log. Then test with every mod disabled, confirm the server has reached its ready state, verify the reachable address and configured port, and isolate Wi-Fi, router, firewall, and overlay issues. Do not delete the universe folder merely because players report lag: a reset removes every visited world and should be reserved for evidence of corruption.

What kind of Starbound problem are you seeing?

“Lag” is not a diagnosis. Steam describes latency as the time information takes to travel to the server; higher latency makes delayed movement, rubber-banding, and disconnects more likely. A low frame rate on one computer, a server that never becomes ready, and an IOException/Leaf Block error require different repairs.

Symptom	Likely category	First check
Every player rubber-bands or is disconnected together	Network latency, packet loss, router, firewall, or ISP path	Compare wired and Wi-Fi tests, close bandwidth-heavy applications, and restart the network equipment.
Only one player freezes or cannot join	That player’s network, firewall, address, or mod mismatch	Compare that computer’s connection and mod files with a player who can connect.
The game is “not responding” while the connection itself is stable	Local frame/performance slowdown or overlay conflict	Disable Steam and, where applicable, Discord overlays; test launching the executable without Steam.
The dedicated server never reaches its ready state	Startup failure, configuration error, or mod problem	Read the server console and storage/starbound.log before changing worlds.
IOException, “Leaf Block,” or one world repeatedly fails to load	World corruption, commonly associated with conflicting third-party mods	Back up the universe, identify the damaged world or mod, and avoid a full reset until the evidence supports it.

How should I capture evidence before changing anything?

Write down what happens, when it happens, and who is affected. This prevents a network symptom from being mistaken for a corrupted save and gives you something concrete to compare after each test.

1. Record the exact error text, including capitalization and punctuation.
2. Note whether the problem occurs during server startup, while selecting a character, when entering a particular world, or after playing for a while.
3. Ask whether all players are affected or only one. A single-player failure points first to that player’s network, firewall, or mod set; a simultaneous failure points toward the host, route, or shared configuration.
4. Watch the dedicated-server console and note whether it reaches its ready state before anyone tries to join.
5. Copy storage/starbound.log from the affected installation. Starbound Support identifies this log as useful for diagnosis and asks that it accompany a support report.
6. Back up the universe directory and your mod list before deleting, replacing, or updating files. Keep the untouched copy outside the Starbound folders so a later test cannot overwrite it.

Keep one change per test. If you change mods, router settings, and world files at the same time, you will not know which action helped or which one caused a new failure.

How can I tell network latency from local performance lag?

Use a controlled comparison rather than relying on how “slow” the game feels. Check the server-browser latency, close downloads and streams, and compare a wired connection with Wi-Fi. If only one computer shows stutter while other players remain responsive, investigate that computer’s frame rate, overlays, and local mod files before changing the server.

Signs of a network path problem

• All connected players see delayed movement, rubber-banding, or a disconnect at roughly the same time.
• The server browser reports high or rapidly changing latency.
• Gameplay improves when downloads, cloud synchronisation, video streams, or other bandwidth-heavy applications stop.
• A wired test is more stable than Wi-Fi or powerline networking.

Signs of a local frame or client problem

• Only one player sees freezing or “not responding” messages.
• Other players report that the affected character continues moving normally, suggesting the server is still receiving data.
• Disabling overlays or launching without Steam changes the symptom while the network is unchanged.

Steam’s troubleshooting guidance specifically recommends closing traffic-heavy applications, restarting networking equipment, and testing a wired connection. A Cat6 Ethernet cable is useful for this diagnostic comparison; it is not a guaranteed performance upgrade. If the computer has no Ethernet jack, a USB-C-to-Ethernet adapter can provide the same type of wired test, including on Steam Deck hardware that supports such an adapter.

How do I perform the clean mod test?

Disable every mod, start the server and clients with the same unmodified setup, and retry the action that failed. Starbound Support’s prescribed isolation method is: “If you’re using mods and having issues – first try disabling all mods to identify if they may be a factor, then enable one test which may be causing the error. Also make sure to update your mods when the game updates.”

1. Stop the dedicated server and close Starbound on every player’s computer.
2. Disable all installed mods for the server and for each client. Do not leave a workshop item active on one side while testing the other.
3. Start the server, wait for its ready state, and attempt the same connection, world load, or activity that produced the error.
4. If the clean setup still fails, leave the mods disabled and continue with address, port, router, and log checks. The problem is not yet proven to be mod-related.
5. If the clean setup works, re-enable one mod or one tightly related mod set at a time. Restart as required, repeat the same test, and write down which change reintroduces the failure.
6. Update the identified mod for the current Starbound version. Check that every player and the server use the same release and configuration.
7. If several mods are involved, use a binary-style test: enable half of the remaining list, test, and narrow the failing group. This reduces the number of restarts while preserving a clear cause-and-effect trail.

A mod can create a world error even when the network is healthy. Do not “fix” a suspected mod conflict by immediately resetting the universe; preserve the save and the log first.

Why can’t my friends connect to my Starbound server?

Confirm three things in order: the server finished initialization, the player is using an address reachable from their network, and the configured game port is permitted through the host firewall and router. A port number seen in a guide is only a starting point; the generated server configuration is authoritative if it specifies another value.

1. Wait for complete server initialization

Starting the executable is not the same as accepting connections. Watch the console until it reports that startup is complete. If it exits, loops, or displays an error, fix that startup problem before changing port forwarding. A client cannot connect to a server process that never reached its listening state.

2. Use the correct address for the player’s location

• Players on the same home network should use the host’s LAN address.
• Players connecting over the internet need the host’s reachable public address, subject to the router and ISP’s inbound-connection policy.
• Do not give internet players a private LAN address; it is not routable from outside the home network.

If one friend can connect and another cannot, keep the server files unchanged and compare the failing player’s address entry, firewall, mod set, and network. That pattern usually does not justify deleting a world.

3. Verify the configured port

Community setup guidance commonly reports TCP port 21025 as Starbound’s default internet game port. Treat 21025 as a common default, not a guarantee: a current server guide published October 14, 2026, warns that the generated configuration is the final authority when it uses a different port.

1. Open the server’s generated configuration and identify the game-port value actually in use.
2. Allow that TCP port through the host computer’s firewall for the Starbound server process.
3. Create a router port-forwarding rule from the same external port to the host computer’s LAN address and the configured internal port.
4. Ensure the host computer keeps the same LAN address, or reserve it in the router, so the forwarding rule does not silently point to another device.
5. Have an internet player retry only after the server is ready and the rule is saved. Test LAN connections separately; a local success does not prove that internet forwarding works.

Some university, workplace, hotel, and mobile networks block inbound traffic or place users behind carrier-grade NAT. In those cases, a correctly configured home router may still be unreachable from the outside.

How do I isolate router, Wi-Fi, firewall, and ISP causes?

Change one layer at a time and test with the smallest group possible. Steam notes that wireless or powerline interference can produce intermittent failures and recommends a wired test; it also warns that universities, proxies, and some ISPs can block or shape required traffic.

Run a clean network comparison

1. Stop downloads, cloud backups, video streams, and other bandwidth-heavy applications on the host and test players.
2. Restart the modem and router, then wait for the connection to return fully before starting the server.
3. Connect the host directly by Ethernet if possible. A Cat6 cable is sufficient for this diagnostic; the purpose is consistency, not a promised speed increase.
4. If the host has no Ethernet jack, use a compatible USB-C-to-Ethernet adapter for the test.
5. Repeat the same join attempt on Wi-Fi. Record whether latency spikes, packet loss, or disconnect frequency changes and whether every player notices the difference.

Check firewall and network boundaries

• Confirm the host firewall permits the Starbound server executable and the configured TCP port on the active network profile.
• Check that the router forwards to the host’s current LAN address, not an old DHCP address.
• Look for a second router, mesh node, or ISP gateway creating double NAT. If present, determine which device owns the public address and where forwarding must be configured.
• Ask whether the host network is behind a proxy, campus firewall, or carrier-grade NAT. Those restrictions may require a different network or a hosting arrangement that explicitly supports Starbound.

Do not leave broad, temporary firewall exceptions enabled after testing. Replace them with a narrowly scoped rule for the server process and configured port, then retest.

Can overlays or the launch method cause freezes?

Yes. If the symptom is a freeze or “not responding” message rather than synchronized delay for every player, disable the Steam overlay and, where relevant, the Discord overlay. Starbound Support also documents launching the executable without Steam as a troubleshooting test.

1. Close Starbound and the dedicated server.
2. Turn off the Steam in-game overlay in the Steam client’s settings. Disable the Discord overlay for Starbound if it is enabled.
3. Start the server and client again, then repeat the exact action that previously froze.
4. If the freeze disappears, re-enable one overlay at a time to identify the conflict. If it remains, restore the normal launch method and continue with logs, mods, and network checks rather than assuming the router is at fault.

This test separates an injected client interface from the server’s network path. It does not repair a failed port-forward or a corrupted world.

How should I handle IOException, Leaf Block, or suspected world corruption?

Starbound Support describes IOException/Leaf Block errors as world-corruption problems generally caused by conflicting third-party mods. Treat the world as valuable data: back up the universe directory before attempting a reset, and use the logs to decide whether one world or the entire collection is implicated.

When a single-world restore is safer

If the error names one world, occurs when entering one location, or began immediately after a particular mod change, preserve the current universe and restore only the affected world from a known-good backup when available. Keep the damaged copy separately so its log and files remain available for diagnosis.

When a full reset may be justified

A reset is a last resort after the clean mod test, log review, and backups point to broad universe corruption. Starbound’s warning is explicit: resetting removes all worlds visited. Do not perform it for ordinary latency, a failed port rule, a single player’s connection problem, or a server that simply has not finished starting.

After recovery

• Start without mods and verify that a new or restored world loads.
• Add updated mods one at a time, repeating the same load test.
• Keep dated backups of the universe and the working mod list.
• Record which mod or file was removed so the same conflict is not reintroduced.

Should I self-host or use managed hosting?

Neither option removes the need for compatible mods and usable logs. Self-hosting gives direct control over the router, firewall, configuration, and backups; managed hosting can avoid home-network port forwarding, but only if the provider explicitly supports Starbound and exposes the controls you need.

Decision factor	Self-hosting	Managed hosting
Port control	You configure the generated port, host firewall, and router forwarding.	The provider must expose a configurable Starbound port or a documented connection method.
Mod parity	You install and synchronize the server and every client yourself.	You need a way to upload or select the same mod files and versions for all players.
Backups	You control when and where universe backups are stored.	Confirm that downloadable, restorable Starbound universe backups are included.
Logs	You can read storage/starbound.log directly.	Confirm that server logs are accessible, downloadable, and retained long enough to diagnose a failure.
Network restrictions	Home NAT, ISP policy, Wi-Fi quality, and firewall rules remain your responsibility.	The provider may bypass home inbound restrictions, but its own network policy and Starbound support determine whether connections work.

The reviewed guidance does not establish a reliable Starbound-specific lag benchmark for self-hosted versus managed servers. Choose based on control, backup access, logs, mod parity, and explicit Starbound support rather than an unverified performance number.

What should I do when the first tests do not solve it?

Use the evidence to choose the next branch instead of repeating every fix. A useful escalation packet contains the exact error, date and time, affected players, server-console state, the mod list and versions, the configured port, network topology, and the relevant storage/starbound.log excerpt.

• All players fail before joining: verify server initialization, configuration, firewall, router forwarding, and whether the host network permits inbound traffic.
• Only one player fails: compare that player’s address, firewall, mod files, overlays, and wired/Wi-Fi behavior with a working player.
• Everyone joins but experiences delay: stop background traffic, compare Ethernet with Wi-Fi, restart the router, and investigate ISP or proxy restrictions.
• The server freezes or crashes after a mod change: repeat the all-mods-disabled test and re-enable one mod at a time.
• A world alone triggers an IOException or Leaf Block error: preserve the universe, inspect the log, and restore the affected world before considering a complete reset.

Send the preserved log and a concise timeline to Starbound Support if the documented tests cannot identify the cause. Avoid editing or deleting the only copy of the failing universe before that report is made.

Frequently Asked Questions

What port does a Starbound server use by default?

Community setup instructions commonly identify TCP 21025, but the server’s generated configuration overrides that assumption. Read the actual game-port value and forward that TCP port through both the host firewall and router.

Why can I join my Starbound server locally but my friends cannot?

A local success proves the process is reachable on the LAN, not from the internet. Check that friends use the public address, the router forwards the configured port to the host’s current LAN address, and the ISP or network is not blocking inbound connections.

Will deleting the Starbound universe fix server lag?

No. Deleting or resetting the universe is relevant only when logs and symptoms support world corruption, such as an IOException or Leaf Block error. A reset removes all visited worlds and cannot repair Wi-Fi interference, latency, or a closed port.

Why does only one Starbound player get a NetworkException?

Start by comparing that player’s mod versions, firewall, address, and network path with a player who connects successfully. If a wired test or a clean mod set changes the result only for that player, the cause is local rather than a damaged shared world.

What information should I send with a Starbound support request?

Include the exact error, when it occurs, whether all players are affected, whether the server reaches its ready state, the active mod list and versions, and a copy of storage/starbound.log. Keep a backup of the universe so further troubleshooting does not destroy the original evidence.