Why is my StarRupture dedicated server not visible in the server browser?

The most common causes are build mismatch, invalid DSSettings values, closed UDP 7777, or firewall rules blocking inbound traffic. Confirm each layer in order before retesting.

Does direct IP connect still work when browser listing fails?

Yes. Browser listing can lag or fail while direct IP:port connect still works. Always test direct connect first to separate discovery issues from network reachability issues.

Which port should be opened for StarRupture dedicated server?

By default StarRupture uses UDP 7777. Ensure forwarding and firewall rules are both UDP, not TCP, and point to the host running the server process.

StarRupture Server Not Showing in Browser? 7 Fixes That Work (2026)

If your dedicated server is healthy but still missing from the in-game browser, treat this as a layered debugging problem: build, configuration, local process, network path, and discovery propagation. The checklist below minimizes guesswork and gets you to a reliable answer fast.

Verification note: Updated for current hosting guidance and the dedicated server workflow used in ourfull server guide. Last validated on 2026-03-07.

Fast Diagnostic Sequence

Run these fixes in order. Do not jump between steps; each check narrows one specific failure domain.

Fix 1: Confirm server and clients are on the same build

Run SteamCMD update again with validate and make sure all players update from Steam before joining. Build mismatch often looks like a listing issue.

app_update 3809400 validate

Fix 2: Validate DSSettings.txt syntax

Broken line endings or invalid values can prevent a healthy boot. Keep ServerName plain ASCII and verify MaxPlayers is in a realistic range.

ServerName=MyServer
MaxPlayers=4
AutoSaveInterval=15

Fix 3: Verify server process is listening on UDP 7777

Check local listening state before debugging routers. If the process is not listening, browser listing cannot work.

netstat -ano | findstr 7777

Fix 4: Correct port forwarding

On home networks, forward UDP 7777 to the exact LAN IP of the host machine. If DHCP changed your IP, old forwarding rules silently break.

External UDP 7777 -> Internal 192.168.x.x:7777

Fix 5: Open firewall inbound UDP

Windows Firewall or VPS network ACL may block traffic even when your router forwarding is correct. Add an explicit inbound allow rule for UDP 7777.

netsh advfirewall firewall add rule name="StarRupture-UDP7777" protocol=UDP dir=in localport=7777 action=allow

Fix 6: Test direct connect by IP:port

If direct connect works but listing does not, the server is reachable and your issue is discovery latency. Share IP:port with your players as a fallback.

In-game -> Multiplayer -> Join -> PUBLIC_IP:7777

Fix 7: Wait and re-check listing propagation

Server browser propagation can take several minutes after reboot or settings changes. Do not modify multiple settings at once; change one variable and retest.

Wait 3-5 minutes after stable boot before final verdict

When Browser Listing Is Optional

For private groups, direct connect can be your default workflow. Listing visibility is useful, but not required for a playable session. If your team can join via IP:port and gameplay is stable, keep moving and optimize browser visibility later.

Related Tools and Guides

After network stability, most multiplayer issues come from base scaling and resource throughput. Use theProduction CalculatorandLinux Server Guideto reduce downstream bottlenecks.

If the server becomes reachable but the session still feels unstable, the next step is usually the lag-fix guide, not another round of browser refreshes.