FlightAware is no longer working after installing WingBits

Hi all,

I have my flightaware ADSB running on RPi on Ubuntu OS and on Docker using a docker compose file. I decided to try out to send my data also to WingBits and since I could not find a docker compose file, I decided to install it using the method mentioned on their website. Data is being sent to them and that part is working, but now my all other docker containers for FA, FR24, etc are not working.

Complain to them that their install doesn’t install an independent feed client which gets beast data from port 30005.

Until they manage that, i’d recommend removing what you installed.
I believe

sudo systemctl disable --now readsb

should do the trick.

1 Like

Just want to update my experience. I installed Wingbits on RPi 3+ with existing Piaware, FR24feed, and ADSB Exchange without any problem. I installed the client using the script provided on their dashboard.

Update: Looks like Wingbits status on the dashboard is quite delay. Now it is offline. Will check and update again.

Update: On bare metal installation, Wingbits does not work with Piaware or Flightradar24. I have to use the Balena-ads-b project instead. However, this project still does not support GPS location and, in my case, there is a timing issue that Piaware dropped my MLAT.

Run journalctl -xe to see the cause. I also can’t connect to Flightaware because its certificates have expired.

Piaware does NOT use GPS for timing, even if it is intalled and working properly.

Timing problem reported by Piaware is generally a USB or low voltage issue.

1 Like

I have 2 units, one has CA issue. The other one still running OK.

I also had this on my Pi since last many hours, but is gone now.

Couple of hours ago

 

Now

1 Like