Fixing "Waiting for RCON to come up..." Error Print

  • Game Server, Fix, Guide, Troubleshooting, Rust, ARK, Orbit Command
  • 0

Stuck in an endless "Waiting for RCON to come up..." loop in your Orbit Command console? Your server starts but the panel never marks it "Online" — no web console, no commands, players might connect but you're locked out. Super annoying for wipes or mod tweaks!  

This hits hard, but it's a simple config fix (RCON = Remote Console for panel control). Guide for beginners — 5 mins to raid-ready.

 

Why "Waiting for RCON..." Happens 

  • No RCON port allocated: Rust needs a 2nd port (game + RCON TCP). 
  • Missing/weak RCON password: Default "CHANGEME" fails or empty.
  • Server booting slow: Custom maps/mods/Oxide take time (wait first!).
  • Mismatch in oxide.config: RCON port wrong after edits.

Quick Check: Console shows loop? Server logs above might say "RCON started" — if not, config issue.

 

Step 1: Log In & Stop the Server 

  1. Orbit Command (orbit.lunarracks.com) > Your Rust server.
  2. Console tab > Red Stop. Wait for Offline.

Tip: Fresh wipe? Back up first (see our backup guide).

 

Step 2: Allocate RCON Port 

  1. Startup tab (top bar).
  2. Scroll to Port Allocations (bottom).
  3. Click + Allocate Port > Pick TCP type > Assign to server.
  4. Note the new port (e.g., 28016).

 

Step 3: Set RCON Variables 

  1. Still in Startup > Variables section (env vars).
  2. Find/set these:
    • RCON_PORT: Paste your new port (e.g., 28016).
    • RCON_PASSWORD: Strong password (generate: 12+ chars, letters/numbers/symbols). Not CHANGEME/empty!
    • RCON_WEB (if shown): Set to 1 (enables web RCON).
  3. Click Save (top).

Pro Tip: Startup command auto-uses +rcon.port {{RCON_PORT}} +rcon.password "{{RCON_PASSWORD}}" +rcon.web 1.

 

Step 4: Restart & Wait 

  1. Console > Green Start.
  2. Watch logs: Look for "RCON started" (1-5 mins, longer for big maps).
  3. Panel turns Online? Victory! Test connection.

 

Still Stuck? Troubleshooting Table 

Issue Fix
Loops forever Wait about 10 minutes (booting). Check logs for map errors - delete bad custom map in Files.
"RCON bind failed" Wrong port type (must be TCP). Re-allocate/delete old.
Password error Reset RCON_PASSWORD - restart. Edit oxide.config manually (Files > oxide.config.json > "port":yourport).
Custom map/mod hang Files > Delete map file > Restart procedural. Or +rcon.ip "127.0.0.1" in startup args.
No variables? Wrong egg? Reinstall rust
Port conflict Allocate fresh port - avoid main game port.

 

Bonus: Prevent Future Loops 

  • Auto-wipe schedules: Include RCON check.
  • Oxide/Carbon: Verify mods in console post-start.
  • Test: Send /say hello via web console once online.

 

Quick Recap (Cheat Sheet) 

Step Action
1 Stop server
2 Startup > Allocate TCP port for RCON
3 Variables: RCON_PORT=newport, RCON_PASSWORD=strong -> Save
4 Start -> Wait for "Online"

 

Need Help? 

 


 

RCON rescued! Console commands flow, players raid - server slaying again.


Was this answer helpful?

Powered by WHMCompleteSolution