Fixing Star Rupture EOS and Connection Errors
EOS messages, timeouts, and servers that appear online but cannot be joined can have several causes. Diagnose the path from process to player instead of pasting a guessed PublicIP or Engine.ini setting.
Run checks in order
- Build: update client and dedicated app from the same release line.
- Process: confirm the intended
StarRuptureServerEOS.exereaches ready state. - Endpoint: compare launch port, firewall, router/provider mapping, and client entry.
- External test: ask someone outside the host network to join.
- Access: check password/visibility in the current manager.
- Save isolation: use a clean world if the process starts but the world is wrong.
Common symptoms
| Symptom | Likely branch | Next action |
|---|---|---|
| Timeout before appearance | Process, firewall, port, or route | Check console, listening endpoint, and external reachability. |
| EOS/authentication error | Build, account session, or runtime | Use the official launch workflow and capture logs. |
| Visible but join fails | Endpoint mismatch or incompatible build | Compare public address/port and update both sides. |
| Blank world after join | Wrong save/working directory | Follow persistence recovery. |
Port-forwarding boundary
The official setup article shows -port=7777 as an example and says the chosen port must match the forwarded/router/firewall port. It does not publish a universal Star Rupture query-port or RCON table. Forward the endpoint the current package or provider actually uses.
CGNAT and managed hosting
Behind CGNAT, ordinary port forwarding may not make a home server reachable. A tunnel or a public host can be evaluated, but it changes the endpoint and must be tested with the current EOS workflow. Managed hosting removes home-router reachability, while support still needs to confirm the experimental app.
What to send support
- Server and client build.
- Launch command with secrets removed.
- Server log around startup and failed join.
- Same-LAN versus outside-network result.
- Whether a fresh test world works.
Start with setup, then check configuration and backups. Read Creepy Jar's setup article for the current official path.
Use managed Star Rupture hosting when home networking is the failure point.