Your kills aren't tracked. They can't be.

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.

“No Game.log found — set a path in Settings to start the feed.”

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.

Running one build, updating from another.

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.

“This uplink's sync is disabled.”

The app is sending and the server is refusing, because cloud sync is off for that uplink. Turn it on from Connected Uplinks 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.

“URL targets a private/loopback host.”

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.

The cookie went stale.

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.

Tell us — that's what the beta is for.

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.