Hi all,
I’ve updated the packages (“sudo apt-get update and sudo apt-get upgrade”) of my raspberry and now dump1090-fa and dump1090-fa2 show 404 error not found. I have tried to clear the browser cache with no luck.
Can someone help me?
Thank you
Change
URL “http://localhost/dump1090-fa”
To
URL “http://localhost/skyaware/”
The naming of the URL has changed in V 7.2
The default URL was switched to /skyaware a few releases back and /dump1090-fa was kept intact until now.
Version 7.2 does some cleanup and removes the interface at /dump1090-fa as we work towards unifying everything into one map.
1 Like
Which works only, if you’re trying to access it on the same device
Access via network requires the network adress, not “localhost”
1 Like
Now it works, thanks for the information!
Since I have two dump1090-fa instances (dump1090-fa and dump1090-fa2) how can I acess now the data from the dump1090-fa2?
How did you acces that previously ?
If you use them on the same Pi you could use Skyaware Anywhere (accessible from the feeder page) this will show all feeders combined in 1 view.
If you want to access the view separatly you will need to define a different port number in order to display it in a 2nd screen.
Previously I accessed it the following way:
Both feeders are on the same Pi.
Check this topic, that will lead you to a solution for your question
Please post output of following 4 commands
ls /etc/lighttpd/conf-available/89-*.conf
sudo nano /etc/lighttpd/conf-available/89-skyaware.conf
sudo nano /etc/lighttpd/conf-available/89-dump1090-fa.conf
sudo nano /etc/lighttpd/conf-available/89-dump1090-fa2.conf
Thanks for your help troublehoosting the issue.
pi@raspberrypi:~ $ ls /etc/lighttpd/conf-available/89-*.conf
/etc/lighttpd/conf-available/89-dump1090-fa2.conf
/etc/lighttpd/conf-available/89-skyaware.conf
**sudo nano /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")
# }
#}
---------
**sudo nano /etc/lighttpd/conf-available/89-dump1090-fa.conf** -> empty
---------
**sudo nano /etc/lighttpd/conf-available/89-dump1090-fa2.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.
alias.url += (
"/dump1090-fa2/data/" => "/run/dump1090-fa2/",
"/dump1090-fa2/" => "/usr/share/dump1090-fa/html/"
)
# redirect the slash-less URL
url.redirect += (
"^/dump1090-fa2$" => "/dump1090-fa2/"
)
# Listen on port 8181 and serve the map there, too.
$SERVER["socket"] == ":8181" {
alias.url += (
"/data/" => "/run/dump1090-fa2/",
"/" => "/usr/share/dump1090-fa/html/"
)
}
# Add CORS header
$HTTP["url"] =~ "^/dump1090-fa2/data/.*\.json$" {
setenv.add-response-header = ( "Access-Control-Allow-Origin" => "*" )
}
I also have a file named 88-tar1090.conf in that folder.
In ver7.2, following folder no more exist:
/usr/share/dump1090-fa/html/
It has been replaced by following folder:
/usr/share/skyaware/html/
To fix the problrm, do following
In file:
`/etc/lighttpd/conf-available/89-dump1090-fa2.conf
at two locations, replace:
dump1090-fa (shown in bold)
by
skyaware
Location-1
alias.url += (
“/dump1090-fa2/data/” => “/run/dump1090-fa2/”,
“/dump1090-fa2/” => “/usr/share/dump1090-fa/html/”
)
Location 2
$SERVER[“socket”] == “:8181” {
alias.url += (
“/data/” => “/run/dump1090-fa2/”,
“/” => “/usr/share/dump1090-fa/html/”
)
}
Now you can see map at ip-of-Pi/dump1090-fa2
Thanks again for your contribution, much appreciated!
Now I get:
- http://ip/dump1090-fa → “404 Not found” error
- http://ip/dump1090-fa2 → it works as expected
Use
For dump1090-fa 1: http://ip/skyaware/
For dump1090-fa 2: http://ip/dump1090-fa2/
If you want both to be similar (i.e. like below)
For dump1090-fa 1: http://ip/skyaware/
For dump1090-fa 2: http://ip/skyaware2/
Make further Modifications as shown below
In file: /etc/lighttpd/conf-available/89-dump1090-fa2.conf
In code below,
replace dump1090-fa2 (shown in bold, 2 places)
by
skyaware2
alias.url += (
“/dump1090-fa2/data/” => “/run/dump1090-fa2/”,
“/dump1090-fa2/” => “/usr/share/skyaware/html/”
)
After above modifications, the code will become:
alias.url += (
“/skyaware2/data/” => “/run/dump1090-fa2/”,
“/skyaware2/” => “/usr/share/skyaware/html/”
)
I have done the modifications you mentioned but now I get:
- http://ip/skyaware → it works as expected
- http://ip/skyaware2 → “404 Not found” error
Seems this is because the name of file was not changed. Please do this:
sudo lighty-disable-mod dump1090-fa2
cd /etc/lighttpd/conf-available/
sudo mv 89-dump1090-fa2.conf 89-skyaware2.conf
sudo lighty-enable-mod skyaware2
Done! You’re a master Sir!
It works 100%! Much much appreciated! I owe you a lot!
2 Likes
Glad to know your problem is solved.
One more thing. When you copy-paste code in forum, it’s format is bad, particularly comment lines (starting with # or ## ) are shown as Heading in bold and large font.
This bad text-formatting can be corrected by placing [code] and [/code] as follows
[code]
Code line 1
Code line 2
… … …
Code line n
[/code]
Now I will do this to your code quoted above, and you will notice the first line which appeared bold and large size fonts, will become normal and the # sign will reappear at it’s start
# server.modules += ( “mod_alias” )
alias.url += (
“/skyaware/data/” => “/run/dump1090-fa/”,
“/skyaware/data-978/” => “/run/skyaware978/”,
“/skyaware/” => “/usr/share/skyaware/html/”
)
NOTE: the [code] and [/code] will show only when you are typing. Once you press “Reply” button, it goes into hiding. It will re-appear if you edit the post.
Thanks for giving the tip!
I’ve edited my post to properly match the format which is supposed to be.
1 Like
Your post looks much better now.
One little drawback with this system is that if code has too many lines, only about 25 lines are directly visible, and one has to use scrollbar at right of code to scroll down/up to see the rest of the code. However this is not a big deal.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.