GPortal is a popular option when you want the convenience of managed hosting but still need enough control to keep your StarRupture world stable.
This guide is intentionally practical: it assumes you care about uptime, save safety, and "how do I actually get the world running" more than platform theory.
TL;DR
- Configure the server in the host panel, but remember: you still need to start a session/world from the game client using Manage Server.
- Make backups before changing ports/slots/passwords.
- Use scheduled restarts to avoid long-running performance degradation.
- If the server doesn't show up, try direct connect and check the port/firewall assumptions first.
1) Basic Setup Checklist (Safe Defaults)
In your GPortal web panel, set:
- Server name: recognizable (include region)
- Slots / max players: start with 4-8
- Server password: optional, but recommended for small groups
- Restart schedule: nightly restart (off-peak)
- Backups: enable automatic backups (daily)
Then stop the server before applying deeper config edits.
2) The Most Common Mistake: "Server is running" but World is Not
StarRupture dedicated servers typically need a client-side step:
- Start the server in GPortal.
- Open StarRupture on your PC.
- Join via Dedicated Server connect flow (direct connect if needed).
- Click Manage Server.
- Set admin/server passwords and Start New Session.
If you don't do this, you can end up with:
- empty/missing world state
- players connecting but nothing persists
- confusing "it works for me" behavior
3) Configuration: DSSettings.txt (and What to Do If You Can't Find It)
On self-hosted servers, persistent settings live in DSSettings.txt.
On managed hosts, you may or may not get direct file access. If you do:
- Look for the equivalent of:
Saved/Config/WindowsServer/DSSettings.txt
If you do not have file access:
- Use the host panel's settings fields (name, slots, passwords, restart schedule).
- Avoid changing ports unless your host explicitly supports it for StarRupture.
For a full DSSettings walkthrough (self-host perspective):
4) Backups: How to Avoid Losing a 60-Hour Factory
Recommended backup policy:
- Daily automated backup
- Keep at least 7 days
- Before any big config change, take a manual snapshot
When troubleshooting:
- Download a known-good backup locally.
- Make your changes.
- If the world corrupts or players can't join, restore the snapshot.
5) Performance Tips (Lag, Autosaves, and "Rubber Banding")
Lag spikes usually come from:
- storage bottlenecks (hosts with slow disks)
- autosaves happening too frequently
- very large item throughput on belts/rails
Actions:
- Prefer SSD-backed plans
- Keep autosave interval reasonable
- Schedule a nightly restart
If you're seeing consistent spikes:
6) Troubleshooting
Server Not Showing
Try:
- direct IP connect (if supported by your host)
- waiting a few minutes after restart (some hosts delay listing)
- verifying your server is fully started (not "starting")
Also:
Stuck in Restart Loop
Common causes:
- invalid password / config values
- incomplete updates
Fix:
- stop server
- restore last good backup
- start server again and re-apply changes one by one