I have installed the piaware, flightradar24 and pi-hole on my pi3, stretch.
The piaware creates a webpage at address Pi_IP:8080 or Pi_IP/dump1090
That should not interfere with the Pi_IP/admin at port 80... but it did. Now the Pi_IP/dump1090 page shows a generic Pi-hole page "Pi-hole: Your black hole for Internet advertisements".
Pi_IP:8080 generates
"[ERROR]: Unable to parse results from queryads.php: Unhandled error message (Invalid domain!)"
Note that Pi_IP:8754 is correctly showing the FR24 stats.
Any ideas how to solve this conflict (probably in lighttpd)
What does your /etc/lighttpd/lighttpd.conf file look like? Can you cat that file and post the results here for us to look at. And a pihole -d debug token would help us a lot.
# Pi-hole: A black hole for Internet advertisements
# (c) 2017 Pi-hole, LLC (https://pi-hole.net)
# Network-wide ad blocking via your own hardware.
#
# Lighttpd config for Pi-hole
#
# This file is copyright under the latest version of the EUPL.
# Please see LICENSE file for your rights under this license.
###############################################################################
# FILE AUTOMATICALLY OVERWRITTEN BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE: #
# /etc/lighttpd/external.conf #
###############################################################################
server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite"
)
server.document-root = "/var/www/html"
server.error-handler-404 = "pihole/index.php"
server.upload-dirs = ( "/var/cache/lighttpd/uploads" )
server.errorlog = "/var/log/lighttpd/error.log"
server.pid-file = "/var/run/lighttpd.pid"
server.username = "www-data"
server.groupname = "www-data"
server.port = 80
accesslog.filename = "/var/log/lighttpd/access.log"
accesslog.format = "%{%s}t|%V|%r|%s|%b"
index-file.names = ( "index.php", "index.html", "index.lighttpd.html" )
url.access-deny = ( "~", ".inc", ".md", ".yml", ".ini" )
static-file.exclude-extensions = ( ".php", ".pl", ".fcgi" )
compress.cache-dir = "/var/cache/lighttpd/compress/"
compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" )
# default listening port for IPv6 falls back to the IPv4 port
include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
# Prevent Lighttpd from enabling Let's Encrypt SSL for every blocked domain
#include_shell "/usr/share/lighttpd/include-conf-enabled.pl"
include_shell "find /etc/lighttpd/conf-enabled -name '*.conf' -a ! -name 'letsencrypt.conf' -printf 'include \"%p\"\n' 2>/dev/null"
# If the URL starts with /admin, it is the Web interface
$HTTP["url"] =~ "^/admin/" {
# Create a response header for debugging using curl -I
setenv.add-response-header = (
"X-Pi-hole" => "The Pi-hole Web interface is working!",
"X-Frame-Options" => "DENY"
)
$HTTP["url"] =~ ".ttf$" {
# Allow Block Page access to local fonts
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
}
# Block . files from being served, such as .git, .github, .gitignore
$HTTP["url"] =~ "^/admin/\.(.*)" {
url.access-deny = ("")
}
# Add user chosen options held in external file
include_shell "cat external.conf 2>/dev/null"
That looks fine, try accessing the PiAware page as you normally would, and then check /var/log/lighttpd/access.log and /var/log/lighttpd/error.log for any 404 errors. The generic dark page is a result of a 404 response from lighttpd when trying to view that page.
The debug token shows that lighttpd is open on port 80 and 8080, so there is either another lighttpd daemon running or there's another configuration file that tells it to listen on the 8080 port.
It should be the piaware webpage...
Anyway, on the logs, with scp, I get:
Permission denied.
Error code: 3
Error message from server: Permission denied
You might want to check with Oliver on PiAware and ask him where he sets the configuration for lighttpd with that package. You need sudo access to see the logs, they are privileged files.
Thanks, when I get a few minutes I'll take a look and see. But for now, it does look like there's an external.conf file or another configuration file that is adding the 8080, if you can get in to see the access.log and error.log files it would help out tracking down where the hang up could be.
If you can get the actual logs, enable it for a short time, then it's going to be a whole lot easier. What I think is happening is that the URL is http://<pi>/flightawarepage/ and it just redirects http://<pi>/flightawarepage to that other URL with the trailing slash. That can be caught in the 404 mechanism and instead of rewriting the URL with the trailing slash and redirecting, it's being handled as a file not found and tripping up in the Pi-hole 404 setup.