FlightAware Discussions

HTTP Error 0

All of a sudden the Piaware feed stopped working. The log shows HTTP error 0? On a RPi 4b (Buster) I have rebooted, reinstalled dump1090-fa and Piaware. The FR24 and PlaneFinder feeds are down as well. When I view the local web pages [local ip]:8754 and [local ip]:8080 there are about 100 aircraft being tracked. The router and firewall have been rebooted. The rest of the network functions are nominal. How do I resolve what appears to be a communications error between the RPi and the FA server?

pi@CS2:~ $ sudo systemctl status piaware
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset:
Active: active (running) since Tue 2021-01-05 12:17:10 EST; 1h 29min ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 839 (piaware)
Tasks: 3 (limit: 4915)
CGroup: /system.slice/piaware.service
├─ 839 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -status
└─6649 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 192.168.1.2

Jan 05 13:44:46 CS2 piaware[839]: reconnecting in 51 seconds…
Jan 05 13:45:37 CS2 piaware[839]: Connecting to FlightAware adept server at piaw
Jan 05 13:45:57 CS2 piaware[839]: Connection to adept server at piaware.flightaw
Jan 05 13:45:57 CS2 piaware[839]: reconnecting in 6 seconds…
Jan 05 13:46:03 CS2 piaware[839]: Connecting to FlightAware adept server at piaw
Jan 05 13:46:23 CS2 piaware[839]: Connection to adept server at piaware.flightaw
Jan 05 13:46:23 CS2 piaware[839]: reconnecting in 4 seconds…
Jan 05 13:46:27 CS2 piaware[839]: Connecting to FlightAware adept server at 70.4
Jan 05 13:46:29 CS2 piaware[839]: Connection to adept server at 70.42.6.198/1200
Jan 05 13:46:29 CS2 piaware[839]: reconnecting in 6 seconds…

sudo apt install mtr-tiny
mtr -T -r -c 5 -P 1200 70.42.6.198
mtr -T -r -c 5 -P 80 flightaware.com

That’s basically a traceroute using TCP on port 1200 which is what piaware is using to get to that IP.
Second one is a reference using port 80.
They both look similar for me (redacted the first few hops).

  9.|-- atl-b24-link.ip.twelve99.  0.0%     5  225.9 396.5 120.7 1256. 482.4
        atl-b24-link.ip.twelve99.net     
 10.|-- hou-b1-link.ip.twelve99.n  0.0%     5  342.9 324.9 305.3 342.9  13.5
 11.|-- internap-ic-345829-hou-b1  0.0%     5  329.8 333.0 305.5 346.4  16.5
 12.|-- border3.ae1-bbnet1.hou.pn  0.0%     5  137.9 138.4 136.9 139.5   1.0
        border3.ae2-bbnet2.hou.pnap.net  
 13.|-- edge1.ae1-edgenet.hou.pna  0.0%     5  140.3 140.0 138.6 141.0   0.9
 14.|-- net-superconnect-7.edge1.  0.0%     5  138.9 138.2 136.6 139.5   1.1
 15.|-- ???                       100.0     5    0.0   0.0   0.0   0.0   0.0
 16.|-- swane.hou.flightaware.com  0.0%     5  137.3 137.1 136.6 137.5   0.4
        atl-b24-link.ip.twelve99.net     
 10.|-- hou-b1-link.ip.twelve99.n  0.0%     5  321.9 320.0 305.0 335.6  10.9
 11.|-- internap-ic-345829-hou-b1  0.0%     5  332.9 332.9 325.4 344.1   6.9
 12.|-- border3.ae2-bbnet2.hou.pn  0.0%     5  138.2 137.5 136.4 138.2   0.8
        border3.ae1-bbnet1.hou.pnap.net  
 13.|-- edge1.ae1-edgenet.hou.pna  0.0%     5  138.8 138.7 137.8 140.4   1.0
 14.|-- net-superconnect-7.edge1.  0.0%     5  136.0 136.9 136.0 140.1   1.8
        lb-1.hou.flightaware.com         
 15.|-- lb-1.hou.flightaware.com  75.0%     4  180.2 180.2 180.2 180.2   0.0

Also it would probably be interesting to see the log without it being cut off.

sudo journalctl -u piaware | tail -n20

Honestly it looks like the box just doesn’t have internet access for whatever reason.

You are right. The box (cs2) is fine on all parts of the local network, but it cannot get to the external network by name or ip. Traces and pings simply return errors. I inserted my backup mSD and the results were the same. Next I flashed a new mSD card with Etcher; put SSH and wpa_supplicant.conf in the boot directory. When I booted the RPi no network adapters were found.

I can connect to/from Germany from the other devices on my network over a TOR circuit in a circle - 35.137.242.144 to 89.233.43.74 to 51.38.69.210 to 185.220.101.212 to 35.137.242.144.

I’m a Windows guy so I know very little about Buster. I’m at a loss on how to proceed.

Did you have following line in wpa_supplicant.conf?

country=DE

If not, add it and try again.

 

I believe I discovered the issue. The gateway ip address is corrupted. That said, I don’t know how to correct the gateway ip address in the RPi.

It should get that via dhcp?
If you have a static IP setup somehow … then that’s where you need to fix the gateway.
Is it a piaware sd-card image or just Raspbian?

just raspbian use raspi-config?

sudo raspi-config

I finally got it sorted today. The issue was caused by a router firmware update from my service provider. The box that failed was the only one not using DHCP. Thanks for your help.