The feeder cannot resolve DNS queries. This will most likely prevent it from working at all. Try System -> Management -> Reboot to see if that will fix it.
The feeder has an IPv6 address but IPv6 isn't working. This can cause docker and other issues.
docker compose up has failed. If the retry doesn't work, go to System - Share Diagnostics and include that link when reporting the issue.
The feeder system kernel detected under-voltage. This can lead to random crashes and various issues with clock
stability, reduced reception, failing SDRs, etc. Please check and likely replace your power supply.
This pi5 is limiting USB current to 600 mA, this is insufficient for more than 1 SDR or additional USB devices.
You can fix this by using an official RPi power supply.
Or override by adding usb_max_current_enable=1 in /boot/firmware/config.txt if you're confident your power supply is sufficient.
The system has been deemed unhealthy for this reason:
The external IP of your browser and the feeder are different. The information in the status links for some of the
aggregators below may be incorrect.
You are running low on disk space on the your feeder. This can lead to odd problems and even crashes. Consider
upgrading to a larger storage device.
You are running in integrated feeder mode
Checking on last connection...
The Stage 2 system at address has
recently accessed this feeder.
No Stage 2 system has recently accessed this feeder. The last
contact was from ago
Connect a Stage 2 system (which will feed aggregators) to this
system.
Most likely 192.168.1.96
will work as the IP address for this integrated feeder.
Enabled indicates feeding the aggregator. feed is in good state,
feed is down,
feed is degraded,
feed state is not supported
▶Toggle detailed legend| Last status update:
'': feed/mlat is connected; '': feed/mlat is not connected
'': mlat sync errors (if this persists for hours, check this page)
'': feed is intermittent / degraded
'': mlat sync warning (intermittent sync issue / lack of traffic / no other receivers in the area)
'': container is up for less than a 30 seconds, not checking status
'': container is down
'': status information is not available at this time or not supported
No aggregators configured. Add aggregators:
Data Sharing
Update ADS-B Feeder Software
▶More information
If this update brings in new container images, even with a fast internet connection this can easily take more than ten minutes to complete. The web UI will pause while the update is running, but the feeder apps will only be briefly interrupted once all new components have been downloaded.
Please note that after a restart (or first install) it can take up to a couple of minutes for the pages above to
respond, so if you get an error, please wait a moment and try again.
(your feeder will be at an approximate location as holmdel-adsb)
Flightradar24
Note: The Flightradar24 status page is for monitoring only.
You should NOT change any settings through this page. Any changes you make there will not be saved.
Note: The SkyAware map on the status page does not work, it's not needed to supply data to FA
(You can re-enable that map at the cost of increased cpu / memory consumption by adding PIAWARE_MINIMAL=false
to the environment variables on the expert page)
Running the containers for the account-based aggregators on systems with 1GB of RAM or less can cause problems - it
certainly is possible, but many users have observed random issues like MLAT errors or generally issues reliably
connecting to those aggregators. A two stage setup which off-loads the connections to the aggregators to a different
system might be a good idea.