FlightAware Discussions

Piaware 3.7.1 'couldn't open socket: connection refused'

My setup is OrangePi Zero running Armbian with Dump1090-mutability with piaware, using FlightAware ProStick Plus v1.0.

I had no issues with an older version (3.6.3). In fact the disk image still works:

However, on upgrading to latest version (3.7.1), I get:
got 'couldn't open socket: connection refused':

Is this a bug/regression or I need to do something to fix this…


Normal output.

The error will hopefully be cleaned up at some point to reduce confusion.

I forgot to add… I’m not able to feed to FlightAware, most probably due to this reason.
As in, while setting up a new receiver I couldn’t claim it (by visiting https://flightaware.com/adsb/piaware/claim) - I get “No receiver found” or something similar.

I’m almost sure that error is no related to your problems.
This is my output:

PiAware master process (piaware) is running with pid 685.
PiAware ADS-B client (faup1090) is running with pid 7661.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 28699.
Local ADS-B receiver (dump1090-fa) is running with pid 7628.

dump1090-fa (pid 7628) is listening for connections on port 30005.
no program appears to be listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.

got 'couldn't open socket: connection refused'
dump1090 is producing data on localhost:30005.

Your feeder ID is 

Let’s check the output for this command, should tell us more:

sudo journalctl -u piaware | grep -v 'reported location\|--lat\|feeder ID'

Could it be you can’t claim the receiver because it’s already associated with your account?
It will remember the feeder-id when upgrading to a new version.


Is the feeder not in the dropdown menu?

The more likely problem might be that you are not receiving any aircraft?
Have you checked the local map? http://pi/dump1090

Okay… Let me check…