Flightaware Status

[odhiambo0]

I am running piaware on Pi4B. Everything is submitting fine - piaware, fr24 and radabox.
When I visit http://172.16.17.106:800, I get this screen:

My question is - why is it not displaying any parameters?

The link at the bottom points to http://172.16.17.106:8000/skyaware/ which is broken. I need to edit some files, right?

[abcd567]

@odhiambo0

My question is - why is it not displaying any parameters?

 

What is the output of following commands:

uname -a

apt-cache policy piaware-web

 

[odhiambo0]

pi@hass:~ $ uname -a
Linux hass.wash.lan 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux
pi@hass:~ $ apt-cache policy piaware-web
piaware-web:
  Installed: 8.2
  Candidate: 8.2
  Version table:
 *** 8.2 500
        500 https://raw.githubusercontent.com/abcd567a/rpi/master ./ Packages
        100 /var/lib/dpkg/status
pi@hass:~ $

[obj]

What is the image that you are starting from?

How did you install piaware?

[odhiambo0]

I used this link:

https://github.com/abcd567a/rpi/blob/master/README.md

I am also aware of the official instructions at the following link:

https://flightaware.com/adsb/piaware/install 

Thank you.

[ua549]

I access the local SkyAware page at :8080, not 8000.

Try http://172.16.17.106:8080

[odhiambo0]

I am interested in seeing the values for the parameters in the original post.

PiAware Version:
Dump1090-fa version:
CPU Temperature:
System Load:
System Uptime:

I am aware that port 8080 has my piaware tracking details. I don’t have an issue with that.

[abcd567]

@odhiambo0

Linux hass.wash.lan 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux

Seems your OS is Kali Linux with penetration tool “wash”.

Please post output of following command

cat /etc/os-release

[odhiambo0]

I am using Raspberry Pi OS, Bullseye. wash.lan is my vanity domain name

pi@hass:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

pi@hass:~ $ cat /etc/debian_version
11.6

[abcd567]

@odhiambo0

I am using Raspberry Pi OS, Bullseye.

pi@hass:~ $ cat /etc/debian_version
11.6

Great!

I also use 64-bit Raspbian Bullseye on my Pi4 but my Debian ver is 11.5. I have No issues with piaware-web which I installed from same repository as you did. No issues when I see piaware-web at IP-OF-PI (without port number).

Instead of http://172.16.17.106:800/, try following address in your browser (without http:// and without port number)

172.16.17.106

If problem persists, clear browser cache and reload browser

 

 

 

[abcd567]

@odhiambo0

OK, downloaded latest Raspberry Pi OS Bullseye from Raspberry Pi foundation’s website:

2023-02-21-raspios-bullseye-arm64-lite.img.xz

imaged a spare microSD card with above 64-bit image, installed 64-bit pre-built packages of piaware, dump1090-fa, dump978-fa, and piaware-web from my PPA at Github https://github.com/abcd567a/rpi/blob/master/README.md

Everything including piaware-web working OK.

 

 

[odhiambo0]

I still don’t get the same screen as yours. I will have to purge everything and start afresh, I think.

[odhiambo0]

This is the screen output I am looking for.

[odhiambo0]

I have managed to resolve this issue.
Nginx was running on my Pi4B on port 80/443 and for some reason, the config (50-piaware.conf) was being installed in /etc/lighttpd/conf-available/, but not being activated in conf-enabled.
Once I fixed the port issues between lighttpd and nginx, I linked this file and restarted the daemon (I guess it’s called 'service; in Linux lingo) and everything is now okay.

The biggest problem seems to be myself here - being more competent and comfortable with Apache than with lighttpd and nginx

[eric1tran]

@odhiambo0 No this was good information. We’ve seen a few reports of this and will look into the root cause. Thanks!