Raspberry Pi 3A+ Debian 9.0.1 add-on Update Error [RESOLVED]

Hey there –

Running Raspberry Pi 3A+, Debian Bullseye, Add-on package 9.0.1

It looks like the signature file has busted for the bullseye add-on update.

When I type: sudo apt update

I now get an error:

Err:1 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
403 Forbidden [IP: 2606:4700:4400::6812:27c9 80]
Hit:2 https://repo-feed.flightradar24.com flightradar24 InRelease
Hit:3 Index of /raspbian bullseye InRelease
Hit:4 Index of /debian bullseye InRelease
Reading package lists… Done
E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bull seye/InRelease 403 Forbidden [IP: 2606:4700:4400::6812:27c9 80]
E: The repository ‘http://flightaware.com/adsb/piaware/files/packages bullseye I nRelease’ is no longer signed.
N: Updating from such a repository can’t be done securely, and is therefore disa bled by default.
N: See apt-secure(8) manpage for repository creation and user configuration deta ils.

It seems like this was an issue back in Oct 2023. It worked fine the other day when I ran it, but now is giving me the error. My plan is to hang on and see if it resolves, but am curious if anyone else is having the problem…

David

2 Likes

Open file flightaware-apt-repository.list for editing:

sudo nano /etc/apt/sources.list.d/flightaware-apt-repository.list

In this file you will see following line at the bottom:

deb [ signed-by=/usr/share/keyrings/flightaware-archive-keyring.gpg ] http://flightaware.com/adsb/piaware/files/packages bullseye piaware

Comment-out this line, i.e. place a # just at start of line left of deb, as shown by red arrow in screenshot attached below

Next copy paste following line just below the above line, and save file

deb [ trusted=yes ] http://flightaware.com/adsb/piaware/files/packages bullseye piaware

 

After saving file, issue update command

sudo apt update

 

Hey abcd567 –

Thank you for the quick response!

No joy.

cat flightaware-apt-repository.list

> # This file is automatically generated by the flightaware-apt-repository package
> # to point to the correct FlightAware repository for the currently installed Debian OS.
> # Any changes made to this file will be lost when flightaware-apt-repository is reconfigured.
> #
> # To disable generation of this file:
> #   purge the flightaware-apt-repository package; or
> #   set ENABLED=no in /etc/default/flightaware-apt-repository; or
> #   rename this file to /etc/apt/sources.list.d/flightaware-apt-repository.list.disabled
> 
> #deb [ signed-by=/usr/share/keyrings/flightaware-archive-keyring.gpg ] http://flightaware.com/adsb/piaware/files/packages bullseye piaware
> deb [ trusted=yes ] http://flightaware.com/adsb/piaware/files/packages bullseye piaware

results in:

sudo apt update
Err:1 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
403 Forbidden [IP: 2606:4700:4400::ac40:9437 80]
Hit:2 https://repo-feed.flightradar24.com flightradar24 InRelease
Hit:3 Index of /debian bullseye InRelease
Hit:4 Index of /raspbian bullseye InRelease
Get:5 https://pkgs.tailscale.com/stable/raspbian bullseye InRelease
Reading package lists… Done
E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bullseye/InRelease 403 Forbidden [IP: 2606:4700:4400::ac40:9437 80]
E: The repository ‘http://flightaware.com/adsb/piaware/files/packages bullseye InRelease’ is no longer signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Would deleting the keyring force creation of a new one?

David

OK, try this:

sudo apt update --allow-unauthenticated

 

Hey there –

Same error when I try --allow-unauthenticated. This is fascinating to me. I appreciate your suggestions and am open to any others that you have. Thanks for lending me a hand!

I updated flightaware a few days ago, so I imagine I am not that far out of update. I am happy to hang out and see if it resolves from the flightaware packages end. It was just such a curious error that happened out of nowhere…

David

[SOLVED BY HACK]

sudo nano sudo nano /etc/apt/sources.list.d/flightaware-apt-repository.list

In the file opened, in following line changed http to https

deb [ signed-by=/usr/share/keyrings/flightaware-archive-keyring.gpg ] http://flightaware.com/adsb/piaware/files/packages bookworm piaware

Saved File, then successfullyu ran command sudo apt update , no Error messages.

Click on Screenshot to See Larger Size

 

2 Likes

Hello, I have same problem here, but this does not fix it.
Roberto

Do yo have Bookworm, Bullseye or Buster?
I have Bookworm on my 3 Pi’s and the https fix worked on all three.

Hello, I have buster.
I did update list file but apt is trying to get files with http not https

pi@piaware:~ $ sudo apt update
Err:1 http://flightaware.com/mirror/raspbian/raspbian buster InRelease
  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
Err:2 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease                                                          
  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
Hit:3 http://repo.feed.flightradar24.com flightradar24 InRelease                                                                     
Err:4 http://flightaware.com/mirror/raspberrypi/debian buster InRelease
  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
Hit:5 https://apt.rb24.com buster InRelease   
Reading package lists... Done
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
E: The repository 'http://flightaware.com/mirror/raspbian/raspbian buster InRelease' is no longer signed.
E: Failed to fetch http://flightaware.com/mirror/raspbian/raspbian/dists/buster/InRelease  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
E: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/bullseye/InRelease  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
E: The repository 'http://flightaware.com/adsb/piaware/files/packages bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch http://flightaware.com/mirror/raspberrypi/debian/dists/buster/InRelease  403  Forbidden [IP: 2606:4700:4400::6812:27c9 80]
E: The repository 'http://flightaware.com/mirror/raspberrypi/debian buster InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
pi@piaware:~ $

Bingo! Renaming http: to https: worked for me. Thank you very much!

David

Thanks for the report and @abcd567 for the workaround. Checking with our Operations team.

2 Likes

Ok this should be resolved. Let us know if you continue to see the issue

3 Likes

Thanks @eric1tran

It is resolved now.
I removed the workaround (i.e. changed https back to http), and ran “sudo apt update”, and the update completed without any error messages.

My OS on 3 RPi Model 4 are 64-bit RaspberryPi OS Bookworm

@eric1tran Thank you! I removed the work around, and it is also working correctly. Can you tell us what the fix was? Was it the same issue as back in Oct 2023?

@abcd567 Thank you so much for your help! You are very generous with your time and expertise. I appreciate you helping me!

David

Apprently it seems to be same issue as in Oct 2023. Please see below the quote from Oct 2023 post by Oliver (@obj):

1 Like

That’s correct, we’ve been moving things over to Cloudflare and the ADS-B mirror/install links seemed to have broken in the process. The Ops guys just fixed it.

3 Likes

@eric1tran Thanks for letting us know what the fix was. I find that so interesting. And thank you to the Ops guys for all the behind the scenes magic making it happen.

David

It seems to be broken again… I’m getting all the same errors listed above, and none of the fixes help.

1 Like