Adept Server timeout

Sorry if this has already been brought up 1000 times - I have not had time to be very active on here for a few years now and I only saw one reference to what I’m about to ask but it was not totally relevant. I’ve been faithfully feeding the last 9 years and all of a sudden I’m seeing this - after seeing that my streak got wrecked yet again beginning 5 days ago:

● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2025-05-14 18:05:07 MST; 6min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 746 (piaware)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/piaware.service
├─ 746 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
└─1059 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 33.616 -

May 14 18:07:30 raspberrypi piaware[746]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
May 14 18:08:00 raspberrypi piaware[746]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
May 14 18:08:00 raspberrypi piaware[746]: reconnecting in 62 seconds…
May 14 18:09:02 raspberrypi piaware[746]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
May 14 18:09:32 raspberrypi piaware[746]: Connection attempt with adept server at piaware.flightaware.com/1200 timed out
May 14 18:09:32 raspberrypi piaware[746]: reconnecting in 70 seconds…
May 14 18:10:42 raspberrypi piaware[746]: 6060 msgs recv’d from dump1090-fa (5648 in last 5m); 1302 msgs sent to FlightAw
May 14 18:10:42 raspberrypi piaware[746]: Connecting to FlightAware adept server at 70.42.6.156/1200
May 14 18:11:12 raspberrypi piaware[746]: Connection attempt with adept server at 70.42.6.156/1200 timed out
May 14 18:11:12 raspberrypi piaware[746]: reconnecting in 56 seconds…

Now, I’d think network error somewhere along the lines, but I haven’t changed a thing in months if not years when it comes to my setup, network or otherwise.

Has something changed on the back-end? I actually had to email support a few weeks back because I used an old email address when I signed up and it wouldn’t even let me log back into my account - my email was updated for my account, but to my knowledge that wont matter so far as my feeder is concerned.

Any ideas would be great - I really don’t want to stop feeding, but my time for the “hobby” is very thin right now, so hoping it’s something goofy that just changed.

Thanks in advance~

I had a problem like that a couple of years ago. It turned out to be due to the ISP not handling IPv6 addresses correctly. I changed my router from the ISP provided router to my own router and that fixed the problem. Don’t know if your problem is similar.

1 Like

Looks like you are probably using a very old version of PiAware that has hardcoded IP addresses as fallbacks that are no longer valid.
See the response to a similar query in this thread:

That’s correct, version 3.7.2, might want to upgrade to the new version of Piaware indeed.

Yeah, probably the issue is old software rather than IPv6 as mentioned in my post. On the other hand, even when things are working normally, you can have some disconnects from the FlightAware Adept servers. I looked at my piaware logs over the last six weeks (the last boot) and noticed several periods where there were disconnects. Don’t know what that’s due to (WiFi drops, or something else). Turns out even with those drops, less than 0.1% of messages were lost between dump1090-fa and FlightAware.

Oddly enough when I restart PiAware, it connects without issue for a couple minutes then poof!

Not sure if this is just a band-aid or what, but I disabled IPV6 on the Raspberry and now it’s working just fine. I wasn’t even able to ping google before doing so. Not sure what the deal is/was. I lost a lot of ability on Debian as I haven’t really touched it in a few years now. Strange how old age effects the brain