Getting ERROR 403:Forbidden when installing PiAware on a fresh install

FlightAware ADS-B Flight Tracking
1

The screenshot shows the entire error. This is on a brand new fresh install. I have another receiver running on my network, but to me it wouldn’t makes sense for that to be the issue even if that is one of the only thing I can think of. Only other thing that comes to mind is content blockers or firewalls. I disabled my firewall to avoid that issue as well. Any ideas how to get past this?

Untitled
Untitled1049×153 64.7 KB

2

Update plus extra information. The screenshot was for a rpi4. I tried again with a rpi3 and same thing happened. Additionally, updating my currently active piaware device works no problem. I don’t know if this information means anything, but there it is.

3

Hey there –

Out of curiosity, do you get the same error on your existing pi setup when you run sudo apt update?

That error has started happening to my existing install, which leads me to believe there is a challenge on the flightaware package side…

4

It does not happen on the already existing setup. Only on the new attempts.

5

Hey,
I’m having similar issue when trying to update:
$ sudo apt update
Err:1 http://flightaware.com/mirror/raspbian/raspbian bullseye InRelease
403 Forbidden [IP: 2606:4700:4400::ac40:9437 80]
Err:2 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
403 Forbidden [IP: 2606:4700:4400::ac40:9437 80]
Err:3 http://flightaware.com/mirror/raspberrypi/debian bullseye InRelease
403 Forbidden [IP: 2606:4700:4400::ac40:9437 80]

6

Same for me on two existing RPIs…

Err:1 http://flightaware.com/mirror/raspbian/raspbian bullseye InRelease
403 Forbidden [IP: 172.64.148.55 80]
Err:2 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
403 Forbidden [IP: 172.64.148.55 80]

7

[SOLVED]

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

image
image964×469 23.1 KB

 

1 Like
8

Can’t speak for the OP but for Bullseye I had already made that change and I’m still getting the same error message when running sudo apt-update

The only difference between http and https is I get 5 URLs attempted rather than 4, the extra is…

Ign:4 https://www.flightaware.com/adsb/piaware/files/package bullseye InRelease

9

I don’t have any Pi with Bullseye. All of my 3 Pi’s have Bookworm, and changing http to https has solved the problem on all the three Pi’s, and sudo apt update completes smoothly without any Error message.

10

abcd was on a track, but there are two more files to edit on my pi3 / bullseye:

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

Use sudo nano, sudo vi or any other editor of your choice, find lines starting with deb http:// and replace to deb https://

11

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

2 Likes
12

Thanks.
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 is 64-bit RaspberryPi OS Bookworm

13

My issue seems to be resolved. Thank you for whatever you did!

1 Like