Connection refused piaware-ipv6.flightaware.com

FlightAware ADS-B Flight Tracking
1

For the last 6 hours or more I have been getting:

May 23 09:17:22 piaware piaware[610]: piaware received a message from beast-splitter!
May 23 09:23:20 piaware piaware[610]: 209 msgs recv'd from beast-splitter; 0 msgs sent to FlightAware
May 23 09:23:20 piaware piaware[610]: Connecting to FlightAware adept server at piaware-ipv6.flightaware.com/1200
May 23 09:23:20 piaware piaware[610]: Connection to adept server at piaware-ipv6.flightaware.com/1200 failed: connection refused
May 23 09:23:20 piaware piaware[610]: reconnecting in 68 seconds...
May 23 09:23:50 piaware piaware[610]: 1144 msgs recv'd from beast-splitter (935 in last 1m); 0 msgs sent to FlightAware
May 23 09:24:28 piaware piaware[610]: Connecting to FlightAware adept server at piaware-ipv6.flightaware.com/1200
May 23 09:24:29 piaware piaware[610]: Connection to adept server at piaware-ipv6.flightaware.com/1200 failed: connection refused
May 23 09:24:29 piaware piaware[610]: reconnecting in 53 seconds...

Is this a DNS problem?

Reboot does not help.

1 Like
2

UPDATE

>ping -6  piaware-ipv6.flightaware.com

Pinging piaware-ipv6.flightaware.com [2620:13d:c000:11::196] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2620:13d:c000:11::196:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

So temporary solution appears to be:

 $ piaware-config adept-serverhosts "piaware-ipv6.flightaware.com piaware.flightaware.com"
Set adept-serverhosts to piaware-ipv6.flightaware.com piaware.flightaware.com in /boot/piaware-config.txt:86

 $ sudo systemctl restart piaware
1 Like
3

You should have posted it in this sub-forum. The experts are looking at it more often:

Latest FlightAware/ADS-B Flight Tracking topics - FlightAware Discussions

Maybe @obj is able to check it

2 Likes
4

Thanks for the advice @foxhunter - I’ve moved it accordingly.

2 Likes
5

The default config will try both v4 and v6 addresses – if you have connectivity for both, you probably want to just leave it at the default and not override adept-serverhosts at all. (At some point in the past you’ve overridden this to be v6-only)

I’m looking into what’s gone wrong on the v6 side.

4 Likes
6

Thank you @obj
I had one site configured for v4 and another for v6.
The latter failed connection around 3am on 23rd May - fortunately the alert email warned me, so streak left intact.

1 Like
7

Should be fixed now, sorry for the hassle!

3 Likes