How do I access my ADSB.im feeder after first boot?

Updated

After the first boot, try http://adsb-feeder.local first. If that doesn't load, go to my.adsb.im, which redirects to your new feeder. If you planned to use WiFi but couldn't configure it while writing the SD card, the image creates a hotspot named adsb.im-feeder that you can connect to.

The three access paths, in order

1. Local address via mDNS (try first)

Open a browser on a device on the same network and go to:

http://adsb-feeder.local

This works when mDNS resolution is functioning on your home network. It's the fastest path because it talks directly to the feeder without any external service.

2. Redirect service (fallback)

If adsb-feeder.local doesn't resolve — common on networks that block or don't forward mDNS — use:

http://my.adsb.im

This should redirect you to your new ADS-B feeder. Use this when the local name fails but the feeder is otherwise reachable.

3. WiFi hotspot (when WiFi wasn't pre-configured)

If you intended to use WiFi and weren't able to set it up while writing the SD card, the image starts a hotspot:

  • SSID: adsb.im-feeder

Connect to that hotspot, then reach the feeder through the browser. This is the path for a headless setup where no wired Ethernet is available and no WiFi credentials were baked into the card.

Before you try any of these

The steps that come before access, per the project's install flow:

  1. Start with one of the supported single board computers.
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot your SBC and wait — usually a few minutes, but in some cases 15 to 20 minutes depending on the model and image.

If you jump to the browser too early, the feeder may simply not be up yet. Give it the full wait window on slower boards before concluding something is wrong.

Quick decision table

Situation What to use
Wired Ethernet, mDNS working http://adsb-feeder.local
mDNS not working on your network http://my.adsb.im
WiFi not configured on the card Connect to adsb.im-feeder hotspot, then browse

Common sticking points

  • Nothing loads at adsb-feeder.local: this is usually an mDNS issue on the home network, not a dead feeder. Switch to my.adsb.im.
  • You never set up WiFi: don't wait for a network connection that won't appear — connect to the adsb.im-feeder hotspot instead.
  • You checked too soon: first boot can take 15 to 20 minutes on some models. Wait before troubleshooting.
  • No dongle or antenna attached: the hardware steps come before access; a feeder without its SDR and antenna isn't the setup you're trying to reach.

Once you're in, the feeder plots aircraft on your own map and can share to aggregators such as adsb.lol, ADS-B Exchange, FlightAware, FlightRadar24, and OpenSky Network, among others.