# Really confused here **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [November 12, 2015, 4:45pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585 "2015-11-12T16:45:50Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Angelus](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/angelus/32/40739_2.png) [@Angelus](https://discussions.flightaware.com/u/Angelus)\ **Post date:** [November 12, 2015, 4:45pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/1 "2015-11-12T16:45:50Z")
I’m running dump1090-mutability 1.15~dev abd piaware 2.1.3. I’ve tried all the fixes on the previous discussions i.e. Edit /etc/default/dump1090-mutability # Port to listen on for Beast-format input connections. 0 disables. BEAST\_INPUT\_PORT=“30104” And I am STILL getting Beast-format results connection with localhost:30104: [Errno 111] Connection refused I’ve done this $ sudo piaware-config -mlatResultsFormat “beast,connect,localhost:30104 basestation,listen,31003” && sudo service piaware restart and nothing changes. I’m beginning to pull out what little hair i’ve got left 😢 Does anyone have any help please? ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [November 12, 2015, 4:48pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/2 "2015-11-12T16:48:56Z")
Did you restart dump1090-mutability after the config change? ---
**Author:** ![Angelus](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/angelus/32/40739_2.png) [@Angelus](https://discussions.flightaware.com/u/Angelus)\ **Post date:** [November 12, 2015, 4:51pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/3 "2015-11-12T16:51:36Z")
yes. I shutdown the RPi2 and did a clean reboot ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [November 12, 2015, 7:02pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/4 "2015-11-12T19:02:06Z")
Check which ports dump1090-mutability is actually listening on: sudo netstat -ntap | grep dump1090 and/or check /var/log/dump1090-mutability.log for errors. ---
**Author:** ![jvcdcarlos](https://avatars.discourse-cdn.com/v4/letter/j/3be4f8/32.png) [@jvcdcarlos](https://discussions.flightaware.com/u/jvcdcarlos)\ **Post date:** [November 12, 2015, 10:44pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/5 "2015-11-12T22:44:34Z")
sure it´s 30104? or 30004? ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [November 12, 2015, 11:13pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/6 "2015-11-12T23:13:49Z")
30104 is the current piaware default. But it doesn’t matter what you choose so long as you configure it the same on both sides (piaware and dump1090) ---
**Author:** ![Angelus](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/angelus/32/40739_2.png) [@Angelus](https://discussions.flightaware.com/u/Angelus)\ **Post date:** [November 13, 2015, 3:11pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/7 "2015-11-13T15:11:15Z")
I configured both to be 30104 and they worked for about 4 hours then the next day stopped working. I them re-configured them both to 30004 and it hasn’t thrown any more errors as of yet. Not sure if why 30104 stopped working or why it wont work now. ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [November 13, 2015, 3:30pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/8 "2015-11-13T15:30:58Z")
I would guess that you have another dump1090 version running (with a different configuration) that’s competing for the dongle. This will be obvious if you look at the logs as I suggested. ---
**Author:** ![Angelus](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/angelus/32/40739_2.png) [@Angelus](https://discussions.flightaware.com/u/Angelus)\ **Post date:** [November 13, 2015, 3:40pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/9 "2015-11-13T15:40:06Z")
It would be obvious if it were in fact true, which its not! ---
**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\ **Post date:** [November 13, 2015, 3:48pm UTC](https://discussions.flightaware.com/t/really-confused-here/17585/10 "2015-11-13T15:48:03Z")
If it is happening, it will be obvious from the logs. What **do** the logs say at the time when you saw problems? I mean, dump1090 doesn’t randomly change its port configuration for no reason so obviously something is going on there.