No events are coming in

A server that connects fine may still produce no events for several distinct reasons. Work through the checklist below.

Checklist

1. Check the server’s status

Two things matter here:

The Enabled switch on the server’s page (Settings → Servers → the server, General tab) — if it’s off, heliana isn’t polling the server at all.
The server’s header on the Dashboard — its summary pill opens a list with a status dot per channel (RCON, SFTP). A grey Pending SFTP dot is the normal, healthy state; Not configured means the Game server folder was left empty, and Unknown means heliana’s collector didn’t answer at all. See Server won’t connect.

Fix: Turn the server on if it’s disabled. The SFTP dot cannot tell you whether the SFTP credentials or the folder are right — nothing checks those, which is what the rest of this checklist is for. Chat is the exception to a silent log: it arrives over RCON, so it keeps flowing even when nothing else does. The reverse does not hold: if the RCON dot is red, events that name a player (join, leave, death, wound, revive and so on) are not saved either, because they wait for the RCON roster and are dropped after about 15 seconds. Only game-level events (broadcast, map, round, capture zone, deployable spawned) get through. Fix RCON first — see Server won’t connect. Lines read more than a minute behind the end of the log (a catch-up after downtime) are not recovered.

2. Verify Game server folder

Saving a server does not confirm anything about the Game server folder — only the RCON and SFTP host addresses are checked on save. If the folder is wrong, or points at SquadGame/ itself instead of its parent, the server saves successfully and still produces zero events.

Fix: Open the server’s page (Settings → Servers → the server) and check all three:

Game server folder is the folder that contains SquadGame/, not SquadGame/ itself — heliana looks for the log under SquadGame/Saved/Logs/SquadGame.log relative to it.
SFTP host and SFTP port (usually 22) are correct.
SFTP username and SFTP password are correct. heliana supports password authentication only — an SSH key isn’t accepted.

See Server connection fields for what each field holds, and Get SFTP access for what the account must allow.

3. Give it a few seconds

heliana polls the log continuously in the background — there’s no interval you set. Right after saving or enabling a server, allow a few seconds for the first read to happen before assuming something’s wrong.

Fix: Wait briefly, then check the Live feed again. If nothing shows up after that, continue down this checklist.

4. The server restarted a moment ago

heliana fingerprints the first 512 bytes of the log file to tell one log epoch from the next. While the file is shorter than that, no epoch is opened and heliana reads no bytes out of it at all — a Squad server that has just restarted onto a fresh log therefore produces no events for a short while.

Fix: Nothing to do. As soon as Squad has written that much of the log header, reading starts on its own.

5. Check whether the server is idle

heliana only sees what Squad writes to its log. An empty or idle server — no one connecting, no chat, no squad activity — produces no log lines and therefore no events.

Fix: Join the server or have someone perform an action (connect, chat, switch squad), then check the Live feed again.

6. Confirm the Live feed is showing the right server

The Live feed widget on the Dashboard is scoped to the selected server. Switching servers changes what the widget shows.

Fix: Confirm the right server is selected, and that the feed’s time range covers the period you’re checking.