Start with the exact symptom
Keep the error wording, installed version and the time it happened. Don’t share passwords, setup files, device credentials or private keys in a support message.
| What you see | Check first |
|---|---|
| Cannot open the Pi page | Same local network, Pi power, current address. |
| Setup file expired | Download a fresh setup file from the same account/station. |
| Sign in again | Use the Pi’s actual local sign-in form, then return to the action. |
| Radio missing or disconnected | USB connection, power, supported chipset and selected device. |
| No observations | Whether the radio is healthy and a supported broadcast is actually nearby. |
| Reports waiting to upload | Internet connectivity, receiver time and the displayed upload error. |
| Update rejected | Correct file type, compatible version, available space and valid signature. |
Cannot reach the local page
Use a browser on the same network as the receiver. Guest Wi-Fi and client isolation can prevent devices from reaching each other. The receiver’s address may change if your router assigns a new one.
On the Pi, recover the local setup address with:
sudo layer400 setupUse the address the Pi prints. Do not open a router port to make local setup work. If you see a certificate warning, verify that you are reaching your own receiver; do not ignore warnings on the public Layer400 or account websites.
Account and setup files
The Layer400 account login and the Pi’s local receiver login are separate. A successful website sign-in does not unlock the Pi’s management page.
For an expired setup file, download a fresh one for the intended station. For an identity or already-claimed error, stop and contact the team with the error text. Do not delete the device’s credentials or create repeated stations to work around it.
Hardware and reception
Check the connected adapter matches the detected device. Keep the internet interface separate from the capture adapter, and make sure a shared ADS-B SDR is still controlled by its existing decoder.
A Bluetooth controller can be detected even when the release does not support Bluetooth capture. Use the current hardware compatibility guide.
If hardware looks healthy but the sky is quiet, compare with genuine nearby supported transmissions. A green state alone is not a reception test.
Reception but no map result
Check whether observations were decoded, whether they were uploaded and whether Layer400 accepted them. These are separate steps. A saved local report is not automatically a live map track.
The map needs an eligible, recent report with usable position information. Reconnected queued reports may be historical, not current live traffic. Read the result states.
Ask for help without losing data
Send your receiver version, the step that failed, the exact error and a short description of the hardware. Redacted diagnostics from the receiver can help. Keep the original setup and saved observations in place while we diagnose it.
For update-specific issues, follow the recovery notes. Otherwise, message the Layer400 team.
Need a hand? Talk to Layer400.