Me too! No stats at the moment 
/paul
paulmerkx, wizowor - could you visit flightaware.com/fix and paste the results? Although we made some recent changes to that page, we’re not able to reproduce any problems.
FYI… I am having the same problem on multiple devices (tablet, descktop PC) both at work and at home…
Session Diagnostics
•Your browser is Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
•You are not using a mobile device
•You are NOT using HTTPS
•You may be behind a proxy
- via: 1.1 localhost.localdomain AC19F432
•You are currently logged in.
•Your username is wizowor
•Your user id is 203993
•Your session id is edc6b39f602a…7e76ed81854a
•You can accept cookies from FlightAware
•You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
•You have never chosen a language (locale).
•No default locale detected.
•Your region is US US/en_US
•Your javascript is working fine.
•Time (zulu) is Thursday, 23-Oct-2014 19:35:06 GMT
•JavaScript system clock: Thu Oct 23 14:35:05 CDT 2014
•JavaScript timezone offset: 300 minutes (5 hours)
•Your account can view 8 months of flight history
Here’s one from my tablet at home…
Session Diagnostics
Your browser is Mozilla/5.0 (Linux; U; Android 4.0.4; en-us; AT100 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30 You are not using a mobile device (cookie) You are NOT using HTTPS You do not appear to be behind a proxy server Your public IP address is 63.155.240.141 You are currently logged in. Your username is wizowor Your user id is 203993 Your session id is 0eef48405d92…dbd249b5c20e You can accept cookies from FlightAware You have successfully logged in to FlightAware with this machine and browser at least one time in the past. You have never chosen a language (locale). No default locale detected. Your region is US US/en_US Your javascript is working fine. Time (zulu) is Friday, 24-Oct-2014 00:17:28 GMT JavaScript system clock: Thu Oct 23 2014 19:17:27 GMT-0500 (CDT) JavaScript timezone offset: 300 minutes (5 hours) Your account can view 8 months of flight history
Here’s one from my laptop… which works fine. I see all stats and map.
Session Diagnostics
•Your browser is Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
•You are not using a mobile device
•You are NOT using HTTPS
•You do not appear to be behind a proxy server
•Your public IP address is 63.155.240.141
•You are currently logged in.
•Your username is wizowor
•Your user id is 203993
•Your session id is 03723187867d…bb6211c7652f
•You can accept cookies from FlightAware
•You have successfully logged in to FlightAware with this machine and browser at least one time in the past.
•You have never chosen a language (locale).
•No default locale detected.
•Your region is US US/en_US
•Your javascript is working fine.
•Time (zulu) is Friday, 24-Oct-2014 00:29:13 GMT
•JavaScript system clock: Thu Oct 23 19:29:10 CDT 2014
•JavaScript timezone offset: 300 minutes (5 hours)
•Your account can view 8 months of flight history
Me too; on desktop and android.
Upon further testing, this issue is for the /user/:username URL; the /adsb/stats/user/:username URL works fine, though, interestingly enough.
Nice catch!
Thanks for your patience, we’ve found the issue.
You’re right that we’ve moved the stats page to /adsb/stats/user/ from it’s previous location. The tab was supposed to be a link directing you to the right place, but if you set your user profile to not show your information publicly, we weren’t generating that link correctly.
We’ll fix that soon - in the meantime you can view your stats from the new URL.
I’m having a similar problem: I can see info on my LAN by going to port 8080 (and also by telnetting to 10001), but at flightaware.com/adsb/stats/user/jreese66 it just says “No Active FlightAware ADS-B Sites For This User (jreese66).”
Running in -debug mode, I can see that it’s sending info to FA:
10/25/2014 06:11:10 piaware received a message from the ADS-B source!
10/25/2014 06:11:27 1 msgs recv’d from dump1090; 1 msgs sent to FlightAware
10/25/2014 06:11:56 server is sending alive messages; we will expect them
10/25/2014 06:12:40 piaware has successfully sent several msgs to FlightAware!
10/25/2014 06:16:27 52 msgs recv’d from dump1090 (51 in last 5m); 53 msgs sent to FlightAware
10/25/2014 06:21:27 145 msgs recv’d from dump1090 (93 in last 5m); 147 msgs sent to FlightAware
10/25/2014 06:26:27 241 msgs recv’d from dump1090 (96 in last 5m); 244 msgs sent to FlightAware
10/25/2014 06:31:27 328 msgs recv’d from dump1090 (87 in last 5m); 332 msgs sent to FlightAware
10/25/2014 06:36:27 386 msgs recv’d from dump1090 (58 in last 5m); 391 msgs sent to FlightAware
10/25/2014 06:41:27 434 msgs recv’d from dump1090 (48 in last 5m); 440 msgs sent to FlightAware
10/25/2014 06:46:27 497 msgs recv’d from dump1090 (63 in last 5m); 504 msgs sent to FlightAware
So: Why isn’t the stats page showing anything?
I’m running the latest piaware (1.15).
Any ideas?
Did you claim your device at flightaware.com/adsb/piaware/claim ?
I am having the same problems…not seeing any stats. The device appears to be claimed, but that was a week ago when I first put it together without the antenna…now that I have the antenna, I don’t see stats…
Same problem here. New contributor as of yesterday. Device claimed, just no stats show up. I see a nice pretty web page generated by dump1090 at :8080
Here’s my debug output, which looks fine to me:
pi@raspberrypi /etc/init.d $ sudo piaware -debug
10/25/2014 15:36:35 ****************************************************
10/25/2014 15:36:35 piaware version 1.15 is running, process ID 3112
10/25/2014 15:36:35 your system info is: Linux raspberrypi 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux
10/25/2014 15:36:37 connecting to FlightAware eyes.flightaware.com/1200
10/25/2014 15:36:37 FlightAware server SSL certificate validated
10/25/2014 15:36:37 encrypted session established with FlightAware
10/25/2014 15:36:38 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
10/25/2014 15:36:38 i see faup1090 serving on port 10001
10/25/2014 15:36:38 connecting to faup1090 on port 10001…
10/25/2014 15:36:38 piaware is connected to faup1090 on port 10001
10/25/2014 15:36:38 faup1090 is listening for connections on FA-style port 10001
10/25/2014 15:36:38 logged in to FlightAware as user n6ly
10/25/2014 15:36:38 piaware received a message from the ADS-B source!
10/25/2014 15:36:38 piaware has successfully sent several msgs to FlightAware!
10/25/2014 15:37:08 39 msgs recv’d from dump1090 via faup1090; 39 msgs sent to FlightAware
10/25/2014 15:37:37 server is sending alive messages; we will expect them
What’s the deal? Also, how do I convert my account to a higher level as a feeder?
Hi guys:
Same problem here. First time setup today.
All is good on the Pi:
Web GUI on 8080 looks great and spots airplanes I can see/hear departing KBOS.
nc verifies good messages from dump1090 on 30002, 30003, 10001.
/tmp/piaware.out reports sending plenty of messages to FlightAware.
Re-visited claim page, says already claimed. MAC address correct. (Although – it lists eth0’s MAC address. I’m reporting on wlan0 – hopefully that doesn’t matter, right?)
But – no stats: https://flightaware.com/adsb/stats/user/jbreen
I think it’s you, not us 
You know, mine is also reporting the MAC of eth0 instead of wlan0, I’m using wlan0 to connect.
FWIW – I think eth0’s MAC address is a better unique identifier for the Pi than wlan0’s since you can easily swap out dongles, but I thought I’d mention it because everything else looks perfect. I can’t imagine it matters, but who knows… : )
Yes. It appears that I claimed it:
Linked PiAware Receivers (jreese66)
Great news! Your account is associated with the following PiAware receivers and you can view your statistics here:
b8:27:eb:xx:xx:xx (Friday, October 24, 2014)
=======================
jreese66
Same problem here: Raspberry Pi sends data to flightaware, but statistics are empty after several hours.
piaware.out:
10/25/2014 17:48:43 ****************************************************
10/25/2014 17:48:43 piaware version 1.15 is running, process ID 2573
10/25/2014 17:48:43 your system info is: Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux
10/25/2014 17:48:43 connecting to FlightAware eyes.flightaware.com/1200
10/25/2014 17:48:44 FlightAware server SSL certificate validated
10/25/2014 17:48:44 encrypted session established with FlightAware
10/25/2014 17:48:44 ADS-B data program 'dump1090' is listening on port 30005, so far so good
10/25/2014 17:48:44 i see dump1090 serving on port 10001
10/25/2014 17:48:44 connecting to dump1090 on port 10001...
10/25/2014 17:48:44 piaware is connected to dump1090 on port 10001
10/25/2014 17:48:44 dump1090 is listening for connections on FA-style port 10001
10/25/2014 17:48:44 logged in to FlightAware as user jbrosowski
10/25/2014 17:49:03 piaware received a message from the ADS-B source!
10/25/2014 17:49:13 piaware has successfully sent several msgs to FlightAware!
10/25/2014 17:49:14 7 msgs recv'd from dump1090; 7 msgs sent to FlightAware
10/25/2014 17:49:44 server is sending alive messages; we will expect them
10/25/2014 17:54:14 46 msgs recv'd from dump1090 (39 in last 5m); 47 msgs sent to FlightAware
10/25/2014 17:59:14 127 msgs recv'd from dump1090 (81 in last 5m); 129 msgs sent to FlightAware
10/25/2014 18:04:14 182 msgs recv'd from dump1090 (55 in last 5m); 185 msgs sent to FlightAware
10/25/2014 18:09:14 245 msgs recv'd from dump1090 (63 in last 5m); 249 msgs sent to FlightAware
10/25/2014 18:14:14 280 msgs recv'd from dump1090 (35 in last 5m); 285 msgs sent to FlightAware
10/25/2014 18:19:14 358 msgs recv'd from dump1090 (78 in last 5m); 364 msgs sent to FlightAware
10/25/2014 18:24:14 403 msgs recv'd from dump1090 (45 in last 5m); 410 msgs sent to FlightAware
10/25/2014 18:29:14 450 msgs recv'd from dump1090 (47 in last 5m); 458 msgs sent to FlightAware
10/25/2014 18:34:14 494 msgs recv'd from dump1090 (44 in last 5m); 503 msgs sent to FlightAware
10/25/2014 18:39:14 526 msgs recv'd from dump1090 (32 in last 5m); 536 msgs sent to FlightAware
10/25/2014 18:44:14 596 msgs recv'd from dump1090 (70 in last 5m); 607 msgs sent to FlightAware
10/25/2014 18:49:14 713 msgs recv'd from dump1090 (117 in last 5m); 725 msgs sent to FlightAware
10/25/2014 18:54:14 779 msgs recv'd from dump1090 (66 in last 5m); 792 msgs sent to FlightAware
10/25/2014 18:59:14 810 msgs recv'd from dump1090 (31 in last 5m); 824 msgs sent to FlightAware
10/25/2014 19:04:14 867 msgs recv'd from dump1090 (57 in last 5m); 882 msgs sent to FlightAware
10/25/2014 19:09:14 945 msgs recv'd from dump1090 (78 in last 5m); 961 msgs sent to FlightAware
10/25/2014 19:14:14 985 msgs recv'd from dump1090 (40 in last 5m); 1002 msgs sent to FlightAware
10/25/2014 19:19:14 1027 msgs recv'd from dump1090 (42 in last 5m); 1045 msgs sent to FlightAware
flightaware.com/adsb/stats/user/jbrosowski
No Active FlightAware ADS-B Sites For This User (jbrosowski)
But on flightaware.com/adsb/piaware/claim
Linked PiAware Receivers (jbrosowski)
Great news! Your account is associated with the following PiAware receivers and you can view your statistics here:
b8:27:xx:xx:xx:xx (Samstag, 25 Oktober 2014)
Any ideas?
Mine suddenly just started working
Mine is working now, too. This occurred at about 19:00-20:00 PDT, or approximately 22 hours after my pi started sending data to FlightAware. I’m not sure if FA fixed a bug, or whether they needed to receive nearly a day’s worth of data before displaying it.
jreese66