Since the upgrade when on the home screen -
http:<IP_ADDRESS>, I select <goto 1090 skyaware map> I get redirected to <IP_ADDRESS>/dump1090-fa/ - and no map or stats are displayed. If I select from home screen, <goto 978 UAT Skyaware map> the display is normal, i.e. map and traffic.
What I tried - I did an install from the piaware image 3.8.1. I have tried disabling UAT receiver which didn’t help. I accidentally tried http://<IP_ADDRESS>:8080/ and that works
The server side thinks you have a dual 1090 and 978 setup; is that correct?
Hi
I actually have dual receivers, even if I disable the 978 uat, I still have the same problem.
Thanks
Jorge
Show the debug information for lighttpd and dump1090-fa please:
sudo journalctl --no-pager -u lighttpd
– Logs begin at Sun 2020-05-10 00:20:48 UTC, end at Sun 2020-05-10 15:51:45 UTC. –
May 10 00:21:42 piaware systemd[1]: Starting Lighttpd Daemon…
May 10 00:23:56 piaware lighttpd[494]: 2020-05-10 00:21:46: (plugin.c.190) Cannot load plugin mod_setenv more than once, please fix your config (lighttpd may not accept such configs in future releases)
May 10 00:23:57 piaware systemd[1]: Started Lighttpd Daemon.
May 10 00:23:58 piaware lighttpd[634]: 2020-05-10 00:23:57: (plugin.c.190) Cannot load plugin mod_setenv more than once, please fix your config (lighttpd may not accept such configs in future releases)
May 10 00:25:17 piaware systemd[1]: /lib/systemd/system/lighttpd.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/lighttpd.pid → /run/lighttpd.pid; please update the unit file accordingly.
pi@piaware:~ $ ls /etc/lighttpd/conf-enabled
50-piaware.conf 89-dump1090-fa.conf
88-dump1090-fa-statcache.conf 89-skyaware978.conf
pi@piaware:~ $ grep mod_setenv /etc/lighttpd/ -rnT
/etc/lighttpd/conf-available/89-skyaware978.conf: 24: server.modules += ( “mod_setenv” )
/etc/lighttpd/conf-available/89-dump1090-fa.conf: 24: server.modules += ( “mod_setenv” )
pi@piaware:~ $ sudo journalctl --no-pager -u dump1090-fa
– Logs begin at Sun 2020-05-10 00:20:48 UTC, end at Sun 2020-05-10 15:52:45 UTC. –
May 10 00:21:42 piaware systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 10 00:21:47 piaware dump1090-fa[499]: Sun May 10 00:21:47 2020 UTC dump1090-fa 3.8.1 starting up.
May 10 00:21:47 piaware dump1090-fa[499]: rtlsdr: using device #1: Generic RTL2832U (Realtek, RTL2832U, SN 00001090)
May 10 00:21:47 piaware dump1090-fa[499]: Detached kernel driver
May 10 00:21:47 piaware dump1090-fa[499]: Found Rafael Micro R820T tuner
May 10 00:21:47 piaware dump1090-fa[499]: rtlsdr: tuner gain set to 49.6 dB
May 10 00:21:47 piaware dump1090-fa[499]: Allocating 4 zero-copy buffers
Should be working.
Maybe use a current browser, there have been some reports about issues with old browsers lately.
@obj
maybe it’s Storage.setItem() - Web APIs | MDN ?
Not sure this was present before 3.8.1
@met00
Could you do the following:
Open your browser, press F12 and select the Console tab in the stuff that opens.
Then open the /dump1090-fa page and take a screenshot, post it here.
Hi, you are right, iit seems to be Chrome specific, I have tried on :
-
Chrome : Win 10 (Chrome V :Version 81.0.4044.138 (Official Build) (64-bit)) , Mac OS 10.15.4 (Chrome V - 81.0.4044.138), Ipad 13.3.1 (Chrome V 81.0.4044.124) - didn’t work
-
Edge : Win 10 - works
-Safari : Ipad & Mac - Work
The Chrome version seems to be the newest across all devices.
Thanks for your help.
Could you take the requested screenshot, it could help pinpoint the issue.
Also try if Ctrl-F5 will fix it.
Hi - here is the screenshot of the console - there was an error, I got this off the Mac. Hitting ctrl +f5 fixes the problem…
Did you modify config.js ?
@obj
I’d recommend something like this for config.js:
$HTTP["url"] =~ "config.js$" {
setenv.add-response-header += (
"Cache-Control" => "must-revalidate",
)
}
But for that you’d first have to fix the double mod_setenv from 1090 and 978.
Otherwise the module won’t work and it will have no effect.
Hi
No - I was having the issue under piaware 3.8.1 in rasbian stretch, I then did a completely new image from your site and still had the problem.
Thanks
Jorge
Not my site.
Well very strange.
I’ll go back to Ctrl-F5 as the first advice for local page problems again …
Thanks for your help, Ctrl F5 worked for me, I’ll keep an eye on it - at least I can access the pages on my site.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.