"It works perfectly for AirNav and Fr24, "
If this is true and you’re trying to add to this already, you’re trying to add more decoders (dump1090-fa) and these are running. Stop. It won’t end well unless you know how to configure for net only mode.
Flightradar24 uses dump1090-mutability. Or data sources from an external decoders.
Airnav probably has one too.
Don’t need to add more if this is working.
No he has neither dump1090-mutability, nor dump1090-rb.
If these were running, they will show in the output of command pgrep -l dump1090 .
I have dump1090-fa running, and it appears in response to this command
Please see below what @jhosua1 has posted earlier.
Sure.
So tell me why he continues to enforce while flightaware is not working, that Fr24 and airnav do.
Not talking NOW that its been removed. But if the goal is to feed multiple sites. Not to use the narrow install instructions that don’t take that into account.
42.post later the fix is the same. Don’t mass install things one after the other using scripts if you are unsure on what it does.
Install one decoder. Configure another feeder for network only. Test/reconfigure. And so on.
This seems something to do with corruption in the OS.
I have already advised him to re-image his microSD card so that he gets a fresh clean copy of OS, then at first only install dump1090-fa and piaware and see if piaware now works ok. He can then proceed with installation of fr24 and rb24 feeders, one by one, checking with each install if all works OK.
Did you not see the original log? Multiple usb claim -6 errors. One map working while another feeder doesn’t.
Same all along.
This was due to conflict between dump1090-fa and readsb, not because of dump1090-rb or dump1090-mutability which never existed.
Or he’s just confusing the stations on the FA status pages.
It’s unlikely to be an OS error.
You’d have to look at the local piaware + dump1090-fa log to really even start to get to the issue.
In his post he has shown piaware log saying “no ADS-B data program is serving on port 30005”
The best option for him is to re-image microSD card and then as first step intall dump1090-fa and piaware, and nothing else. After he finds this is working OK, he can proceed with intallin other feeders, one at a time, and checking piaware.
Hello again. I used a formatted 32GB card and installed the Armbian operating system Armbian OS 24.2.0 Jammy and Ubuntu 22.04.3 LTS distribution with arm64. I verified that there was no ADS-B feed installed nor dump1090 or readsb decoder, so the operating system is clean. I started by installing Dump1090-fa without errors. Then I installed Piaware, where without noticing various errors during the long installation process that I put in images captured at the time. Afterwards, I indicated the Piaware site to the system to register my station and rebooted the system. Next, I installed Piaware-web and also installed sudo apt install rtl-sdr, which was not installed since it was a clean system. Conclusion: Air traffic is only received on the local website 192.168.2.92:8080 but none on ADS-B Flight Tracking - FlightAware as was the case before. On the local Piaware website it indicates in Red that there is no link with Radio 1090 or Mlat. Likewise on my Site I can see in the log [2025-03-14 19:23 CET] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s also as was the case before. I am including screenshots of some of the errors that occurred during the Piaware installation in case it is relevant to why it is not working correctly. I hope your help in solving the problem and this will be of use to us all. Regards
View your site statistics online
This will always take you to your first site.
I’ve reported this issue but i doubt it’s been fixed.
Thus as i assumed you’re looking at the incorrect station.
You should check the unique id on the stats page vs the local piaware log.
sudo journalctl -u piaware -e
@abcd567 he only showed piaware log from the website which is useless exactly because it can be from the incorrect station.
sudo journalctl -u dump1090-fa --no-pager -n5000 | curl -F'expires=24' -F"secret=" -F'file=@-' https://0x0.st
This should give you a link to the dump1090-fa log you can post here.
Might have the location, not sure.
Don’t post the link if it has the location and you don’t want to share.
So if you’re not looking at the wrong station, your SDR might have an issue on top of the previous issues of running multiple decoders.
It seems to have been resolved by a desperate attempt. I followed the Piaware installation tutorial manually and started seeing aircraft movement on the website ADS-B Flight Tracking - FlightAware. Finally, there is a link to dump1090-fa with Piaware. Although I wasn’t able to complete the entire linking process because the download link didn’t work when cloning the Piaware source code, I was able to continue with the rest of the process. The point is that this manual process worked better for me than the .sh installer I used initially.
If you don’t want to deal with the details of setting up various aggregators, take a look at this complete sd-card image: A simple way to feed ADS-B data
Thanks for the trouble. If I have this problem again, I could try the image you recommended. It would be interesting to know where the installation went wrong using the direct link to the dump1090-fa executables and software for computers like mine. The best option is certainly a manual step-by-step installation. Thanks for your help. I’ll keep an eye on it now and then start installing Fr24feeder and rbfeeder one by one, which was my intention: to have all three feeders.
Glad to know the issue is resolved.
Can you please provide link to the tutorial for manually installing Piaware? Thank you.
@wiedehopf
@w7psk
@oblivian
@LawrenceHill
As @jhosua1 has used piaware pre-built packages from my repository at Github and it gave him issues, I decided to test these packages by installing on Armbian Jammy.
I downloaded Armbian Jammy, wrote to a spare microSD card, slipped card into RPi model 4, powered up, and installed following pre-built packages from my Github repository:
All are working OK 
I’m glad my problem was solved with your help. It might also be useful for other users who are stuck like me and are using alternative devices with Armbian. Now, perhaps it’s time to review the preconfigured packages and see where there might be a glitch in the installation that’s causing it to not work properly. Great work! Keep up the good work!
