I am following the FR24 online instructions to install an FR24 feed for a PiAware system. The install script fails. System is a Pi4b with 4GB RAM, 32GB SD running the latest PiAware image. Here is the output (note, this is my first post so I have obfuscated the urls (with “xxx”) in this output in case it gets blocked).
pi@piaware:~ $ sudo bash -c “$(wget -O - xxx/install_fr24_rpi.sh)”
–2023-11-07 23:25:51-- xxx/install_fr24_rpi.sh
Resolving repo.feed.flightradar24 (xxx)… 52.217.232.80, 52.216.145.197, 52.217.0.166, …
Connecting to repo.feed.flightradar24 (xxx)|52.217.232.80|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 1428 (1.4K) [application/x-sh]
Saving to: ‘STDOUT’
- 100%[=================================================>] 1.39K --.-KB/s in 0s
2023-11-07 23:25:51 (41.0 MB/s) - written to stdout [1428/1428]
Hit:1 xxx/mirror/raspbian/raspbian bullseye InRelease
Hit:2 xxx/adsb/piaware/files/packages bullseye InRelease
Hit:3 xxx/mirror/raspberrypi/debian bullseye InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
dirmngr is already the newest version (2.2.27-2+deb11u2).
0 upgraded, 0 newly installed, 0 to remove and 109 not upgraded.
bash: line 29: /etc/apt/keyrings/flightradar24.gpg: No such file or directory
–2023-11-07 23:25:58-- xxx/flightradar24.pub
Resolving repo-feed.flightradar24 (repo-feed.flightradar24.com)… 104.16.59.181, 104.16.58.181, 104.16.60.181, …
Connecting to xxx (xxx)|104.16.59.181|:443… connected.
HTTP request sent, awaiting response… 200 OK
Length: 5287 (5.2K) [application/x-mspublisher]
Saving to: ‘STDOUT’
- 0% 0 --.-KB/s in 0s
Cannot write to ‘-’ (Broken pipe).
pi@piaware:~ $