It's invite-only for now. Join the waitlist and we'll email you a signup link the moment a place opens up.
Seven things account for most of it. Two of them aren't bugs and never will be — the first one leads, because knowing that saves you the hour.
Star Citizen used to write a line naming who killed whom. CIG removed it. It isn't hidden behind a setting — there is no logging option that brings it back, and anyone telling you to enable one is guessing.
So StarStats works it out sideways: your ship is destroyed, you respawn, and it infers that you died — marked as inferred, because it is. Your own deaths come through reliably. Kill credit against another player does not, and won't until the game logs it again.
The app looks for your game folder on its own and usually finds it. When it can't, point it at the file by hand in Settings.
The hint by that box says “Leave blank to auto-discover the largest LIVE/PTU/EPTU log” — that text is out of date and undersells it. Auto-discovery actually walks five channels: LIVE, PTU, EPTU, HOTFIX and TECH-PREVIEW. If you play on HOTFIX or TECH-PREVIEW, leaving it blank still works.
The banner means your installed build and your update channel disagree — a beta build set to take stable updates, or the reverse. The next update check will poll the channel you configured, which may not be the one you're running. Set the release channel to match the build you want to stay on.
The app is sending and the server is refusing, because cloud sync is off for that uplink. Turn it on from the Emitter page on the web, or tick Sync settings with your account in the app and press Save.
Worth saying: this is not you being logged out. It reads like an auth error and isn't one — an older build made exactly that mistake and unpaired itself in a loop over it.
Pointing Test connection at localhost, a 192.168./10./172.16. address, or a link-local one is refused on purpose. It stops the app being talked into probing machines inside your network.
If you're self-hosting, this is the one that'll bite you, and it's working as designed rather than failing.
Hangar data comes from your RSI session cookie, and that lapses whenever RSI ends the session. Paste a fresh one — see the cookie page for where to find it.
If the title bar draws, the tray icon works, and the inside of the window is a blank white rectangle, you are on 0.1.14 or earlier. Update and it goes away. Started from a terminal, the old builds say why:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
We were shipping a copy of libwayland-client inside the AppImage and putting it ahead of yours. Your graphics driver needs its own, so on any distro with a newer one than our build machine — Arch and its family, rolling releases generally — the driver failed to load and the part of the app that paints the page gave up. The window and the tray survived, which is why it looked like nothing was wrong.
The .deb was never affected, and neither was Windows. If you are still stuck on 0.1.15 or later, that is a different fault and worth telling us about — start it from a terminal first, because the first line of output is usually the whole answer.
On Linux everything lands in ~/.local/share/tray/ (or $XDG_DATA_HOME/tray/ if you've set that). On Windows it's %APPDATA%\StarStats\tray\data\. Two files matter:
panic.log is always written — every crash appends to it, with the version that crashed. client.log.YYYY-MM-DD is the detailed one and is off by default; turn on Debug logging in Settings, restart, and reproduce the problem to fill it.
The catch: if your window is blank you can't reach Settings to turn that on. Start the app from a terminal instead — it prints the same log to the terminal whether or not the file is enabled, and that output is the useful thing to paste into a bug report.
If none of this fits, it's worth reporting: during the beta a parser gap is the likeliest cause, and those only get fixed when someone files them. Back to the quickstart.