Server crashing right on startup with "Main game process exited with code 134"? Your RustDedicated process aborts (SIGABRT signal), looping restarts — no map gen, no players. Common especially with Oxide/uMod mismatches or servers witt low resources.

Don't wipe yet; fix in 10 mins!  

This hits new servers hard, but it's usually mods, RAM, or files. Guide for beginners — step-by-step to stable wipes.

Why "Exited with Code 134" Happens 

• Mod loader mismatch: Oxide/uMod/Carbon version doesn't match Rust server build (e.g., Windows Oxide on Linux).  
• Out of memory / crash during boot: Low RAM allocation, big maps, or corrupted saves.
• Corrupted files: Bad updates, mixed Rust versions, or incomplete installs.  
• Startup config: Wrong args, missing libs on Linux.

Quick Check: Scroll console logs before the 134 — look for "assertion failed," "stack overflow," or Oxide errors.

Step 1: Stop & Backup (Safety First) 

1. Orbit command (https://orbit.lunarracks.com/) > Your Rust server.
2. Console tab > Red Stop.
3. Backups tab > Create quick one (view our backup guide).

Step 2: Test Vanilla (Rule Out Mods)

1. Startup tab > Disable Oxide/uMod:
   1. Set MOD_LOADER or similar to 0 / vanilla (egg vars).
   2. Or delete Oxide files: Files tab > Delete oxide/ folder (or Carbon/).
2. Save > Start.
3. Works? Mods guilty — proceed to Step 4.
4. Still crashes? Next.

Tip: Fresh reinstall wipes mods anyway.

Step 3: Reinstall Server Files (Nuclear Option)

1. Settings tab > Scroll to Reinstall Server.
2. Click Reinstall > Confirm (keeps configs/backups).
3. Startup > Ensure latest Rust version (e.g., public).
4. Increase Memory Limit: Bump to 8-16GB (134 often RAM-related).  
5. Save > Start. Watch for "Server startup complete."

Step 4: Re-Add Mods Safely (If Needed)

1. Download exact Oxide/uMod for your Rust version: uMod.org > Builds > Match commit/hash.
2. Files > Upload Oxide zip > Extract to root.
3. Edit oxide/config/oxide.config.json: Verify ports match panel.
4. Restart. No 134? Add plugins one-by-one.

Note: Always Linux 64-bit Oxide — not Windows!

Still Crashing? Troubleshooting Table 

Bonus: Prevent 134 Forever 

• Schedules: Auto-restart + update Oxide weekly.
• Monitoring: Use console alerts for crashes.
• Vanilla First: Always test clean before mods.

Quick Recap (Cheat Sheet) 

Need Help? 

• Full logs screenshot?
  • Take a screenshot and open a ticket: https://my.lunarracks.com/submitticket.php 
  • Take a screenshot and open our live chat

Crash conquered! 

Fresh map loading, raids incoming - server unbreakable.