# Issue with new setup

**URL:** <https://discussions.flightaware.com/t/issue-with-new-setup/17454>\
**Category:** ADS-B Flight Tracking\
**Created:** [October 15, 2015, 9:25am UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454 "2015-10-15T09:25:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![agleave](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/agleave/32/78205_2.png) [@agleave](https://discussions.flightaware.com/u/agleave)\
**Post date:** [October 15, 2015, 9:25am UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454/1 "2015-10-15T09:25:15Z")

</div>

Hi, I have installed PiAware on my Raspberry Pi, it is connecting to Modesdeco2 which is outputting --beast 30005. Data is appearing on the My ADS-B page however I do have 2 issues. I am unable to access it locally, port [192.168.1.6:8080](http://192.168.1.6:8080) just says this page cannot be displayed, I have tried rebooting it however it still doesn’t let me connect locally.

The other issue is when i look at the logs, I see lots of the same message: mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused. Below is a bigger snippet of my log.

Any idea what is causing these issues.

Thanks

[2015-10-15 10:08 BST] 36577 msgs recv’d from modesdeco2 (727 in last 5m); 36522 msgs sent to FlightAware  
[2015-10-15 10:08 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:08 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:09 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:09 BST] mlat(1057): Receiver status: connected  
[2015-10-15 10:09 BST] mlat(1057): Server status: synchronized with 38 nearby receivers  
[2015-10-15 10:09 BST] mlat(1057): Receiver: 151.2 msg/s received 2.6kB/s from receiver  
[2015-10-15 10:09 BST] mlat(1057): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.4kB/s UDP to server  
[2015-10-15 10:09 BST] mlat(1057): Results: 52.7 positions/minute  
[2015-10-15 10:09 BST] mlat(1057): Aircraft: 9 of 13 Mode S, 22 of 28 ADS-B used  
[2015-10-15 10:09 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:10 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:10 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:11 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:11 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:12 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:12 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:13 BST] 37232 msgs recv’d from modesdeco2 (655 in last 5m); 37177 msgs sent to FlightAware  
[2015-10-15 10:13 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:13 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:14 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:15 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused  
[2015-10-15 10:15 BST] mlat(1057): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

---

<div class="post-metadata">

**Author:** ![PeterHR](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/peterhr/32/114359_2.png) [@PeterHR](https://discussions.flightaware.com/u/PeterHR)\
**Post date:** [October 15, 2015, 11:49am UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454/2 "2015-10-15T11:49:20Z")

</div>

see [ads-b-flight-tracking-f21/piaware-2-1-3-released-t36047.html](https://discussions.flightaware.com/t/piaware-2-1-3-released/17363)

---

<div class="post-metadata">

**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:** [October 15, 2015, 1:16pm UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454/3 "2015-10-15T13:16:55Z")

</div>

Both port 8080 and port 30104 are provided by dump1090 in a standard piaware setup. If you have replaced dump1090 with modesdeco then you would need to configure modesdeco appropriately if you still want those ports.

---

<div class="post-metadata">

**Author:** ![agleave](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/agleave/32/78205_2.png) [@agleave](https://discussions.flightaware.com/u/agleave)\
**Post date:** [October 15, 2015, 1:24pm UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454/4 "2015-10-15T13:24:24Z")

</div>

Thanks PeterHR, that did solve the issue with the errors. Tuned out i needed to add --avrmlat 30104 to my startup command on Modesdeco2, as soon as it was started with that then the errors stopped.

Thanks obj, that answers my question with regards to local access, I was thinking port 8080 was giving access to a PiAware page, didn’t realise it was trying to take me to a dump1090 page. I have access to the Modesdeco2 page so that will be fine (via a different port).

Thanks Again

---

<div class="post-metadata">

**Author:** ![joelwiley](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/joelwiley/32/115128_2.png) [@joelwiley](https://discussions.flightaware.com/u/joelwiley)\
**Post date:** [October 15, 2015, 5:24pm UTC](https://discussions.flightaware.com/t/issue-with-new-setup/17454/5 "2015-10-15T17:24:36Z")

</div>

Welcome to this ‘interesting’ world. Be sure to look at some of the threads in the ADS-B Flight Tracking for a wealth of background information.
