Piaware 9.0.1 TLS handshake failed: unexpected eof while reading

FlightAware ADS-B Flight Tracking
1

Hi,

I am running Piaware 9.0.1 on a Raspberry Pi 64-bit system and recently started seeing TLS handshake failures when connecting to FlightAware servers.

System information:

  • Raspberry Pi OS Bookworm

  • Kernel: Linux raspberrypi 6.12.75+rpt-rpi-v8

  • Architecture: aarch64

Log output:

May 18 19:25:04 raspberrypi piaware[27419]: piaware version 9.0.1 is running, process ID 27419
May 18 19:25:04 raspberrypi piaware[27419]: your system info is: Linux raspberrypi 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/Linux
May 18 19:25:06 raspberrypi piaware[27419]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
May 18 19:25:06 raspberrypi piaware[27419]: Connection with adept server at piaware.flightaware.com/1200 established
May 18 19:25:06 raspberrypi piaware[27419]: TLS alert (write): decode error
May 18 19:25:06 raspberrypi piaware[27419]: TLS error: unexpected eof while reading
May 18 19:25:06 raspberrypi piaware[27419]: TLS handshake with adept server at piaware.flightaware.com/1200 failed: handshake failed: unexpected eof while reading
May 18 19:25:06 raspberrypi piaware[27419]: reconnecting in 5 seconds...

The ADS-B feeder is otherwise working normally, but piaware cannot complete the TLS handshake with FlightAware.

Has anyone seen this issue before?
Could this be related to OpenSSL, TLS version compatibility, or recent server-side changes?

Thanks.

2

Hi,

Now there is PiAware 11 so I think is better to upgrade in any case, if it doesn’t work from the web panel you can run the following commands inside terminal:

sudo apt update

sudo apt full-upgrade

3

Do you know when this started happening? There haven’t been any recent changes on the server side that would cause this AFAIK

You can try:

openssl s_client -trace -connect piaware.flightaware.com:1200

to check if the problem is internal to piaware, or a problem at the TLS/network level. (It’s normal to get a certificate validation error from s_client, since piaware isn’t using the normal root CAs, but you should get a TLS handshake completed at least)

The most probable explanation is that something changed in your network that’s interfering with the connection.

(FWIW, the last successful connection handshake I see was on May 19, so actually after the logs you posted above, so it’s perhaps an intermittent problem. I see no further connections attempts from the same IP after that, so either they’re failing before reaching us or your IP changed. Given your location I think it’s likely to be interference from your network provider..)