Hey all. I have my Piaware up and running. I have the feeder ID. dump1090 is producing data on the localhost. It shows Piaware is connected to FlightAware. Faup1090 is connected to ADS-B Receiver. But I am unable to access the UI to Piaware. It should be 192.168.1.110. But it does not show up. Previously, I had Pihole running on the Pi. But I have disable systemctl on Pihole. But still the page won’t load.
I’ve seen some posts on modifying the lighttpd.conf file but I’m not sure which part is needed to change. Should I just change the port to something else?
Any help on this would be much appreciated. Thanks.
The reason you dont see UI at 192.168.1.110 is that piaware-web is not installed. You dont need to configure anything. Simply install piaware-web by following command, and you will see interface at 192.168.1.110
Ok. I’ve rebooted the Pi. I am still able to access the Piaware-web via the Pi’s IP address although I’m wondering if it’s still the cache from the previous one. The Flight Aware logo doesn’t appear anymore and sometime the IP address just won’t load. Maybe I should add the web-port 8080 back into the Piaware.conf?
The CLI shows Piaware is connected to Flight Aware as shown in the previous post.
Also, there were a couple of these services that weren’t running. PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
There are two config files for piaware. Compare with files on your Pi
(1) /etc/lighttpd/conf-available/50-piaware.conf
# Allows access to the piaware status file, and
# does translation rewrites for the landing page
alias.url += (
"/status.json" => "/run/piaware/status.json"
)
server.modules += ( "mod_rewrite" )
$HTTP["language"] =~ "(en)" {
url.rewrite = ( "^/translations/lang.js$" => "/translations/%1.js" )
}
else $HTTP["language"] =~ ".*" {
url.rewrite = ( "^/translations/lang.js$" => "/translations/en.js" )
}
(2) /etc/lighttpd/conf-available/89-skyaware.conf
# Allows access to the static files that provide the dump1090 map view,
# and also to the dynamically-generated json parts that contain aircraft
# data and are periodically written by the dump1090 daemon.
# Enable alias module
#
## This module is normally already enabled in lighttpd, so you should not
## need to uncommment this line.
## There are some cases (e.g. when installing this on a Raspberry Pi
## that runs PiHole) in which the module has been removed from the
## default configuration, and the dump1090-fa web interface no longer
## loads properly.
## If this is what you are experiencing, or if you see messages in your
## error log like:
## (server.c.1493) WARNING: unknown config-key: alias.url (ignored)
## then uncommenting this line and then restarting lighttpd could fix
## the issue.
## This is not enabled by default as standard lighttpd will not start if
## modules are loaded multiple times.
#
# server.modules += ( "mod_alias" )
alias.url += (
"/skyaware/data/" => "/run/dump1090-fa/",
"/skyaware/data-978/" => "/run/skyaware978/",
"/skyaware/" => "/usr/share/skyaware/html/"
)
# redirect the slash-less URL
url.redirect += (
"^/skyaware$" => "/skyaware/"
)
# Listen on port 8080 and serve the map there, too.
$SERVER["socket"] == ":8080" {
alias.url += (
"/data/" => "/run/dump1090-fa/",
"/data-978/" => "/run/skyaware978/",
"/" => "/usr/share/skyaware/html/"
)
}
# Add CORS header
server.modules += ( "mod_setenv" )
$HTTP["url"] =~ "^/skyaware/data/.*\.json$" {
setenv.set-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
# Uncomment this section to enable SSL traffic (HTTPS) - especially useful
# for .dev domains
## Listen on 8443 for SSL connections
#server.modules += ( "mod_openssl" )
#$HTTP["host"] == "piaware.example.com" {
# $SERVER["socket"] == ":8443" {
# ssl.engine = "enable"
# ssl.pemfile = "/etc/ssl/certs/combined.pem"
# ssl.ca-file = "/etc/ssl/certs/fullchain.cer"
# ssl.honor-cipher-order = "enable"
# ssl.cipher-list = "EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH"
# ssl.use-sslv2 = "disable"
# ssl.use-sslv3 = "disable"
#
# alias.url += (
# "/data/" => "/run/dump1090-fa/",
# "/" => "/usr/share/skyware/html/"
# )
# }
#}
#
## Redirect HTTP to HTTPS
#$HTTP["scheme"] == "http" {
# $HTTP["host"] =~ ".*" {
# url.redirect = (".*" => "https://%0$0")
# }
#}
The 89-skyware.conf, which by the way, does not load when I click on the button to go to the Skyaware Map, looks the same also. The uncommented section were the same.
It seems Pi-hole has srewed your lighttpd configuration. As fixing the screwed configuration is not easy for a novice and requires expertise, this leaves you with following options:
(1) Accept to live without UI
OR
(2) Re-image microSD card with latest image.
OR
(3) Purge piaware, dump1090-fa, piaware-web and lighttpd, then reinstall fresh copies from apt. Please note purging will remove the apps as well as all screwed configurations.
Hi. I hit my max 18 msg for the day. It wouldn’t let me respond anymore. But I was able to try to purge first before needing to refresh the image. And I’m happy to tell you that the purge actually worked. My node is online now. Thank you!
