Add the key. Get a SatNOGS DB API key from db.satnogs.org (your avatar, then Settings / API Token). On the server, save it with echo YOURKEY > ~/downlink-desk/secrets/satnogs_token. The next fetch uses it.

The key is wrong. The most common cause is a SatNOGS Network key instead of a SatNOGS DB key; they are different. The other cause is extra characters pasted with the key. Get the DB key again and save it as in Result A.

The server's clock has not synced since boot. A Raspberry Pi has no clock battery, so this can happen after a power cut. Check the network connection. The fetch resumes by itself once the clock is set.

The server has no working internet connection. Check its network cable or Wi-Fi, and the router. Once the connection is back, the next fetch resumes collection.

Collection is working again. The alarm clears once the console sees a successful fetch. Write a log note with the cause, if known.

SatNOGS may be unavailable, or may be limiting requests. Downlink Desk waits and retries by itself. Do not shorten the fetch interval: SatNOGS is run by volunteers. Write a log note, check again after the next fetch, and report it if the alarm is still open at handover.