PiAware is NOT connected to FlightAware


#1

I tried to set up PiAware this morning and I encountered an issue where I am unable to link my FlightAware account with PiAware on the reciever. When using “piaware-status”, I see that everything is running properly, piaware is connected to port 10001, but it is NOT connected to FlightAware.

I even tried manually connecting the account to the device via “piaware-config”, but after entering my credentials, I don’t appear to receive a confirmation message or anything like that. Any ideas I could use to get my account talking to my reciever?


#2

Have you tried restarting it? I’ve seen the first connection attempt fail sometimes.


#3

Yep, I’ve restarted it a few times, each time with the same result. I’ve tried scanning the network for receivers from the Pi itself, a wired connection, and from a laptop on the network as well.


#4

Log into the Pi and look at the /tmp/piaware.out file and paste the last dozen lines from it, or anything that looks relevant.


#5

I just got a chance to take another crack at it:

*3/11/2015 22:17:31 ****************************************************
03/11/2015 22:17:31 piaware version 1.20 is running, process ID 2273
03/11/2015 22:17:31 your system info is: Linux piaware 3.18.5+ #744
PREEMPT Fri Jan 30 18:19:07 GMT 2015 armv6l GNU/Linux
03/11/2015 22:17:31 connecting to FlightAware eyes.flightaware.com/1200
03/11/2015 22:56:46 got 'couldn’t open socket: connection timed out’
to adept server at eyes.flightaware.com/1200, will try again soon…
03/11/2015 22:56:46 ADS-B data program ‘dump1090’ is listening on port
30005, so far so good
03/11/2015 22:56:46 i see dump1090 serving on port 10001
03/11/2015 22:56:46 connecting to dump1090 on port 10001…
03/11/2015 22:56:46 piaware is connected to dump1090 on port 10001
03/11/2015 22:56:46 seconds since last message or startup (2355) less
than threshold for action (3600), waiting…
03/11/2015 22:56:46 dump1090 is listening for connections on FA-style port 10001
03/11/2015 22:56:46 piaware received a message from the ADS-B source!
03/11/2015 22:56:46 connecting to FlightAware 70.42.6.203/1200
03/11/2015 22:58:54 got 'couldn’t open socket: connection timed out’
to adept server at 70.42.6.203/1200, will try again soon…
03/11/2015 22:58:54 3 msgs recv’d from dump1090; 0 msgs sent to FlightAware
03/11/2015 22:58:54 connecting to FlightAware eyes.flightaware.com/1200
03/11/2015 23:01:01 got 'couldn’t open socket: connection timed out’
to adept server at eyes.flightaware.com/1200, will try again soon…
03/11/2015 23:01:01 connecting to FlightAware 70.42.6.203/1200
03/11/2015 23:03:08 got 'couldn’t open socket: connection timed out’
to adept server at 70.42.6.203/1200, will try again soon…
03/11/2015 23:03:09 connecting to FlightAware eyes.flightaware.com/1200
03/11/2015 23:05:21 got 'couldn’t open socket: connection timed out’
to adept server at eyes.flightaware.com/1200, will try again soon…
03/11/2015 23:05:21 7 msgs recv’d from dump1090 (4 in last 6m); 0 msgs
sent to FlightAware
03/11/2015 23:05:21 connecting to FlightAware 70.42.6.203/1200
*

and when I did sudo piaware-status, I did see that faup1090 wasn’t working…


#6

Your internet connection is preventing connection to our server by IP address or port number. You need to either fix this at your router or contact your service provider.


#7

Since 1,5 hours both my pi’s give the following error when trying to send data:

03/22/2015 12:02:40 connecting to FlightAware 70.42.6.203/1200
03/22/2015 12:02:40 error during tls handshake: handshake failed: connection reset by peer, will try again soon…

Other feeders didnt check in for over an hour either so im assuming technical difficulties at the FA servers?


#8

I think it is - just come here wondering if there was a problem as my fresh RPi PiAware stopped reporting 2 hours ago.


#9

Having the same issue here.


#10

+1

Restart of piaware doesn’t help.


#11

Looking at the site list on the statistics page, many sites are showing their last seen status as “Today” instead of “Live”. Looks like the issue is on FA’s side.

Marty


#12

Looks like this morning my PiAware stopped sending data. I’ve tried unplugging/replugging the device in, as well as sending the various restart and reboot commands on the My ADS-B interface. I was able to finally get into my view live data part of the site(so I’m accessing it correctly via the wi-fi network), and it’s working completely correct as far as I can tell, just not sending the data to/from flightaware. Just wondering if anyone has any ideas?


#13

Ditto here as well. Mine stopped around 06:37 EDT this AM (as I recall).
Everything here looks OK, I suspect this is a problem on the FlightAware side of things…


#14

Same here, about 4 hours ago. I am confident they will have it back up soon.


#15

Since of this 11:30 local time (10:30 UTC), I also am not able to send any data to FA:

When I take a look in /tmp/piaware.out, PiAware seems unable to connect to FA. The timestamps in the logging are in UTC, but my PiAware-Tracker is in GMT. I think that this could be a problem why a TLS handshake could not be made.

03/22/2015 14:27:23 connecting to FlightAware eyes.flightaware.com/1200
03/22/2015 14:27:24 error during tls handshake: handshake failed: connection reset by peer, will try again soon…

I tried to update the Timezonedata on the Pi, reset the services multiple times, restarted my P, tried another powersupply, nothing… dump1090 is running normaly, and has the correct timezonesettings.

-EDIT- There’s another thread about the current connection errors…


#16

I have a similar problem, but it looks like there is a problem at flight aware:


03/22/2015 14:55:24 connecting to FlightAware eyes.flightaware.com/1200
03/22/2015 14:55:25 error during tls handshake: handshake failed: connection reset by peer, will try again soon...

What can I do to fix this?


#17

I think the problem is on their end. I am having the same issue. Maybe they’re asleep at the switch?


#18

Same issue here.


03/22/2015 14:58:02 ****************************************************
03/22/2015 14:58:02 piaware version 1.20 is running, process ID 2129
03/22/2015 14:58:02 your system info is: Linux piaware 3.18.7+ #755 PREEMPT Thu Feb 12 17:14:31 GMT 2015 armv6l GNU/Linux
03/22/2015 14:58:02 connecting to FlightAware eyes.flightaware.com/1200
03/22/2015 14:58:02 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
03/22/2015 14:58:03 ADS-B data program 'dump1090' is listening on port 30005, so far so good
03/22/2015 14:58:03 i see dump1090 serving on port 10001
03/22/2015 14:58:03 connecting to dump1090 on port 10001...
03/22/2015 14:58:03 piaware is connected to dump1090 on port 10001
03/22/2015 14:58:03 dump1090 is listening for connections on FA-style port 10001
03/22/2015 14:58:03 piaware received a message from the ADS-B source!
03/22/2015 14:58:33 45 msgs recv'd from dump1090; 0 msgs sent to FlightAware
03/22/2015 15:00:02 connecting to FlightAware 70.42.6.203/1200
03/22/2015 15:00:02 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
03/22/2015 15:01:50 connecting to FlightAware eyes.flightaware.com/1200
03/22/2015 15:01:50 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
03/22/2015 15:03:02 connecting to FlightAware 70.42.6.203/1200
03/22/2015 15:03:02 error during tls handshake: handshake failed: connection reset by peer, will try again soon...
03/22/2015 15:03:33 317 msgs recv'd from dump1090 (272 in last 5m); 0 msgs sent to FlightAware
03/22/2015 15:04:57 connecting to FlightAware eyes.flightaware.com/1200
03/22/2015 15:04:57 error during tls handshake: handshake failed: connection reset by peer, will try again soon...



#19

You are not - alone! :wink:


#20

I was suspecting problems on their end and came here to find I am not alone.
Would have expected some sort of “official” notice somewhere but yet to see one.
BTW my page shows orange bar with Anomalies where local airport normally shows. Is that what you guys/gals showing