PiAware - Claim - Unclaimed

FlightAware ADS-B Flight Tracking
1

Hello there,

I just setup my piAware v5.0. The log /var/log/piaware.log seems fine. The web page on my local ip, shows me the planes, and the right bar.

The site statistics https://flightaware.com/adsb/stats/site/150035 , works just fine. But no on my user, that should be detected as:

https://flightaware.com/adsb/stats/user/zucos

The log says: logged in as a guest

And on the page: PiAware - Claim and Link a Brand New PiAware Ground Station - FlightAware
It says Unfortunately, FlightAware hasn’t found a new, unclaimed PiAware feeder to claim.

I waited 2 days, I change the WAN IP. Im on the same LAN. Also I build a new account and I can claim the station. Its always saying Unclaimed.

This is the log:

Apr 1 00:15:54 piserver piaware[771]: piaware version 5.0 is running, process ID 771
Apr 1 00:15:54 piserver piaware[771]: your system info is: Linux piserver 5.10.17-v7+ #1403 SMP Mon Feb 22 11:29:51 GMT 2021 armv7l GNU/Linux
Apr 1 00:15:55 piserver piaware[771]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Apr 1 00:15:55 piserver piaware[771]: Connection with adept server at piaware.flightaware.com/1200 established
Apr 1 00:15:55 piserver piaware[771]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Apr 1 00:15:55 piserver piaware[771]: FlightAware server certificate validated
Apr 1 00:15:55 piserver piaware[771]: encrypted session established with FlightAware
Apr 1 00:15:56 piserver piaware[771]: logged in to FlightAware as user guest
Apr 1 00:15:56 piserver piaware[771]: my feeder ID is 98395c99-xxxxxxxxx16e (< covered by me)
Apr 1 00:15:56 piserver piaware[771]: site statistics URL: https://flightaware.com/adsb/stats/site/150035
Apr 1 00:15:57 piserver piaware[771]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
Apr 1 00:15:57 piserver piaware[771]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
Apr 1 00:15:57 piserver piaware[771]: Started faup1090 (pid 783) to connect to dump1090-fa
Apr 1 00:15:57 piserver piaware[771]: UAT support disabled by local configuration setting: uat-receiver-type
Apr 1 00:15:58 piserver piaware[771]: piaware received a message from dump1090-fa!
Apr 1 00:15:59 piserver piaware[771]: piaware has successfully sent several msgs to FlightAware!
Apr 1 00:16:28 piserver piaware[771]: 42 msgs recv’d from dump1090-fa; 42 msgs sent to FlightAware
Apr 1 00:21:28 piserver piaware[771]: 254 msgs recv’d from dump1090-fa (212 in last 5m); 254 msgs sent to FlightAware

Any ideas?

1
13837×2058 1.56 MB
2
23635×2056 397 KB

2

You’re running into an ipv4-vs-ipv6 issue; the Pi is connecting over IPv6, and either the IPv6 detection isn’t working correctly when you try to claim from your browser, or the public v6 addresses of your Pi and your browser are sufficiently different they’re not considered on the same network.

Try visiting https://flightaware.com/adsb/piaware/claim/98395c99-xxxxxxxxx16e with your full feeder ID; this should skip the IP-based path and just directly claim that one feeder. (If you’re using a piaware sdcard image, this is where the “claim this feeder” links on skyaware / the top-level status page go to)

2 Likes
3

Thank You. It works.
I spend 2 days trying to found it.
for other guys. claim - unclaimed - on this adress:

https://flightaware.com/adsb/piaware/claim/YOU’R feeder ID

like this:

https://flightaware.com/adsb/piaware/claim/98395xxxxx-xxxxxx-xxxxxx-xxxxx16e

4

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.