Pi-hole and piaware - lighttpd?

Help
61

What does /usr/share/dump1090-fa/html/ look like? Try going directly to a file via http://localhost:8080/...

62 
pi@raspberrypi:~ $ ls /usr/share/dump1090-fa/html/
config.js  dbloader.js  flags-tiny    images      jquery     markers.js  planeObject.js    script.js   style.css
db         flags.js     formatter.js  index.html  layers.js  ol          registrations.js  spinny.gif  test
63

And if you go directly to a file, such as http://localhost:8080/index.html?

64

I am logging in Pi via SSH from another computer. So not sure what localhost would do...
> pi@raspberrypi:~ $ http://localhost:8080/index.html?

-bash: http://localhost:8080/index.html?: No such file or directory

The rendering of the actual page is done on the remote browser.

65

I was using localhost in place of whatever the Pi's IP address or hostname is.

Also, you don't need to include the question mark at the end.

66

Ah. Going to :8080 or to :8080/index generates this on the local browser:
[ERROR]: Unable to parse results from queryads.php: Unhandled error message (Invalid domain!)

67

If you modify the 404 handler in /etc/lighttpd/lighttpd.conf to something else, does the error change?

68

Should I # it? what's the syntax to restart lighttpd?

69

sudo service lighttpd restart

70

I have # the 404 and I get:
403 - Forbidden

71

What does the access log look like?

72 
1528029861|127.0.0.1|GET /admin/scripts/pi-hole/php/queryads.php?domain=192.168.1.232:8080&bp HTTP/1.0|200|23
1528029861|192.168.1.232:8080|GET /index HTTP/1.1|200|126
1528029861|192.168.1.232:8080|GET /favicon.ico HTTP/1.1|200|568
1528029861|192.168.1.232:8080|GET /favicon.ico HTTP/1.1|200|568
1528052681|127.0.0.1|GET /admin/scripts/pi-hole/php/queryads.php?domain=192.168.1.232:8080&bp HTTP/1.0|200|23
1528052681|192.168.1.232:8080|GET / HTTP/1.1|200|126
1528052681|192.168.1.232:8080|GET /favicon.ico HTTP/1.1|200|568
1528052681|192.168.1.232:8080|GET /favicon.ico HTTP/1.1|200|568
1528052696|192.168.1.232|GET / HTTP/1.1|200|405
1528052696|192.168.1.232|GET /pihole/blockingpage.css HTTP/1.1|200|4127
1528052696|192.168.1.232|GET /admin/img/logo.svg HTTP/1.1|200|1649
1528052696|192.168.1.232|GET /admin/style/vendor/SourceSansPro/SourceSansPro-Regular.ttf HTTP/1.1|304|0
1528052696|192.168.1.232|GET /admin/style/vendor/SourceSansPro/SourceSansPro-Bold.ttf HTTP/1.1|304|0
1528052696|192.168.1.232|GET /favicon.ico HTTP/1.1|200|405
1528052696|192.168.1.232|GET /favicon.ico HTTP/1.1|200|405
1528052712|192.168.1.232|GET /dump1090.php HTTP/1.1|200|405
1528052712|192.168.1.232|GET /pihole/blockingpage.css HTTP/1.1|200|4127
1528052719|192.168.1.232|GET /dump1090.php HTTP/1.1|200|405
1528052719|192.168.1.232|GET /pihole/blockingpage.css HTTP/1.1|200|4127
1528056631|192.168.1.232:8080|GET / HTTP/1.1|403|345
1528056705|127.0.0.1|GET /admin/scripts/pi-hole/php/queryads.php?domain=192.168.1.232:8080&bp HTTP/1.0|200|23
1528056705|192.168.1.232:8080|GET / HTTP/1.1|200|126
1528056730|192.168.1.232:8080|GET / HTTP/1.1|403|345
73

What is the output of lighttpd -t -f /etc/lighttpd/lighttpd.conf

74

It is:
Syntax OK

75

How about lighttpd -t -f /etc/lighttpd/conf-enabled/89-dump1090-fa.conf

76

Same response
Syntax OK

77

You might want to ask about on a lighttpd forums since it seems like a complex lighttpd routing issue. Sorry we couldn't help you here, but it doesn't seem like a Pi-hole specific issue.

1 Like
78

Thanks for the help anyway!
You are a great group of developers here!

2 Likes
79

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.