Star Citizen Error Codes

Star Citizen errors fall into two families: 30k/20000 connection timeouts (you lost or timed out the game-server link) and the 60k login errors (60030, 60015) hitting the RSI Launcher sign-in. CIG points both to the same troubleshooting path — reconnect, whitelist the launcher, flush DNS. Here's what each common code means and the fastest fix.

Error codes

30000 (30k) Lost connection to the game server

Cause: A server crash, timeout, or the client dropping its link to the game server while still connected to the hub.

Fix:
  1. Close the game client fully, then reconnect.
  2. If it persists, log out of the RSI Launcher for a bit before trying again.
  3. Whitelist RSI Launcher.exe and StarCitizen.exe in your firewall/antivirus.
20000 (20k) General timeout connecting to the server

Cause: You timed out connecting to the game server but stayed connected to the hub server.

Fix:
  1. Reconnect to the servers — it often works on the second attempt.
  2. Log out of the launcher and back in if reconnecting fails.
  3. Run ipconfig /flushdns in an admin Command Prompt.
60030 Login / authentication error

Cause: The launcher couldn't complete sign-in — often a temporary account-service issue or a local block.

Fix:
  1. Wait a few minutes and retry — some 60k errors resolve on their own.
  2. Follow the 30k steps: firewall whitelist and DNS flush.
  3. Restart the RSI Launcher and re-enter your credentials.
60015 Login service error

Cause: A sign-in failure in the 60k family, usually account-service load or a network block on the launcher.

Fix:
  1. Retry after a short wait.
  2. Whitelist the launcher in firewall/antivirus and flush DNS.
  3. Restart your router and relaunch the RSI Launcher.
Install / slow-load errors The client is slow to load or fails to start

Cause: A slow drive or a partially verified install can cause startup and connection hitches.

Fix:
  1. Install the game on a faster SSD if you're on a hard drive.
  2. Verify the install through the RSI Launcher.
  3. Free up disk space and relaunch.

Fixes that work for most Star Citizen (PC — RSI Launcher) errors

  1. Check the game's server status first (official status page, or the studio's support/X account) — most named connection errors are a maintenance window or outage, and no local fix will help until servers are back.
  2. Restart the game and your PC/console, and power-cycle your router — a fresh connection clears the majority of temporary login and connection errors.
  3. On PC, allow the game and its launcher through your firewall and antivirus, and disable any VPN or proxy — these block the authentication handshake behind many 'can't connect' codes.
  4. Flush your DNS (Command Prompt: ipconfig /flushdns) or switch to a public DNS like 8.8.8.8 / 1.1.1.1 if the game can't reach its servers.
  5. Verify/repair the game files (Steam: Properties -> Installed Files -> Verify; Epic: repair) if the error points at a corrupted install or update.

FAQ

How do I fix the 30k error in Star Citizen?

A 30k (30000) error means you lost your connection to the game server. Close the game client fully and reconnect; if it persists, log out of the RSI Launcher for a bit before trying again, and whitelist RSI Launcher.exe and StarCitizen.exe in your firewall/antivirus.

What are the 60k login errors (60030, 60015) in Star Citizen?

The 60k family (60030, 60015) are login/authentication errors on the RSI Launcher. CIG points them to the same fix as 30k errors: wait a few minutes and retry, whitelist the launcher in your firewall, and run ipconfig /flushdns — some resolve on their own with time.

Other games