Hello strange issue I have at the moment, when I try to connect to my PI using the local Ip on my home network all I get is its unreachable. But the IP address is showing up as the correct one in my router WiFi connections page & it’s still feeding FA, FR24 & ADSBX. Anyone shed any light. I have rebooted it via the cog settings on my FA page and it works for a period of time and starts doing it again. I can’t access Graphs1090, ADSBX ot tar1090 locally
Are you connecting tot the Pi via Ethernet (wired) or Wireless ?
Is the Pi equipped with a fixed IP adres or is it getting an adress from the router (DHCP) adress ?
What is the IP adress shown on the FA stats page ?
Is that the expected IP adress ?
Can you ssh in? ping it?
Check the lighttpd logs if you can ssh in.
IP is static, connected by 5G band WiFi, IP address on FA stats page is the expected one I set up as static.
Connects on ssh & putty using the IP that’s set to it. Don’t know how to access light tpd will have to research that one.
Just using Piaware 7.2 image on it. But it is back up on local IP now but for how long I don’t know.
Some additional thoughts, is the frequency used in 5G the best one for your environment ?
Since you are using Wi-Fi, do you have one or multiple accespoints ? If more then one, are the network settings an exact match ?
Just trying to eliminate the most common errors 
It’s just the 1 access point in use which is the standard router, everything was fine before I went away on 8th Aug. Nothing network based has changed.
1 Like
If you want to enable the logging of lightttpd here’s the needed steps, since it isn’t enabled by default.
This doesn’t apply.
The following should be sufficient:
sudo journalctl -u lighttpd -e
Thanks, I stand corrected then 
The below was what I got using light tpd sudo from weidehopf
Linux piaware 5.10.92-v7l+ #1514 SMP Mon Jan 17 17:38:03 GMT 2022 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Aug 25 17:01:53 2022 from 192.168.0.14
pi@piaware:~ $ sudo journalctl -u lighttpd -e
-- Boot 18a11d3ec62f494f9227fe6ea87dceac --
Jul 06 16:50:53 piaware systemd[1]: Starting Lighttpd Daemon...
-- Boot 4235c929a1404eb5b850855e2be1f62e --
Jul 06 16:50:54 piaware systemd[1]: Started Lighttpd Daemon.
-- Boot 18a11d3ec62f494f9227fe6ea87dceac --
Jul 06 16:50:54 piaware systemd[1]: Started Lighttpd Daemon.
-- Boot 4235c929a1404eb5b850855e2be1f62e --
Jul 06 17:38:25 piaware systemd[1]: Stopping Lighttpd Daemon...
Jul 06 17:38:25 piaware systemd[1]: lighttpd.service: Main process exited, code=exited, s>Jul 06 17:38:25 piaware systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jul 06 17:38:25 piaware systemd[1]: Stopped Lighttpd Daemon.
Jul 06 17:38:25 piaware systemd[1]: lighttpd.service: Consumed 1.298s CPU time.
-- Boot 7acfa05ad6824c3b921861d04e1a273c --
Jul 06 17:38:34 piaware systemd[1]: Starting Lighttpd Daemon...
Jul 06 17:38:35 piaware systemd[1]: Started Lighttpd Daemon.
Jul 12 16:06:19 piaware systemd[1]: Stopping Lighttpd Daemon...
Jul 12 16:06:19 piaware systemd[1]: lighttpd.service: Main process exited, code=exited, s>Jul 12 16:06:19 piaware systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jul 12 16:06:19 piaware systemd[1]: Stopped Lighttpd Daemon.
Jul 12 16:06:19 piaware systemd[1]: lighttpd.service: Consumed 57.574s CPU time.
Jul 12 16:06:19 piaware systemd[1]: Starting Lighttpd Daemon...
Jul 12 16:06:20 piaware systemd[1]: Started Lighttpd Daemon.
Jul 12 16:52:28 piaware systemd[1]: Stopping Lighttpd Daemon...
Jul 12 16:52:28 piaware systemd[1]: lighttpd.service: Main process exited, code=exited, s>Jul 12 16:52:28 piaware systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Jul 12 16:52:28 piaware systemd[1]: Stopped Lighttpd Daemon.
Jul 12 16:52:28 piaware systemd[1]: lighttpd.service: Consumed 2.698s CPU time.
Jul 12 16:52:28 piaware systemd[1]: Starting Lighttpd Daemon...
Jul 12 16:52:28 piaware systemd[1]: Started Lighttpd Daemon.
Aug 22 20:46:52 piaware systemd[1]: Stopping Lighttpd Daemon...
Aug 22 20:46:52 piaware systemd[1]: lighttpd.service: Main process exited, code=exited, s>Aug 22 20:46:52 piaware systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Aug 22 20:46:52 piaware systemd[1]: Stopped Lighttpd Daemon.
Aug 22 20:46:52 piaware systemd[1]: lighttpd.service: Consumed 3min 33.931s CPU time.
-- Boot b8398794696f431a98ac2412e890fa95 --
Aug 22 20:47:00 piaware systemd[1]: Starting Lighttpd Daemon...
Aug 22 20:47:01 piaware systemd[1]: Started Lighttpd Daemon.
Aug 25 16:58:54 piaware systemd[1]: Stopping Lighttpd Daemon...
Aug 25 16:58:54 piaware systemd[1]: lighttpd.service: Main process exited, code=exited, s>Aug 25 16:58:54 piaware systemd[1]: lighttpd.service: Failed with result 'exit-code'.
Aug 25 16:58:54 piaware systemd[1]: Stopped Lighttpd Daemon.
Aug 25 16:58:54 piaware systemd[1]: lighttpd.service: Consumed 15.135s CPU time.
-- Boot 068f7e1c103c4752bfe6503f8c95c736 --
Aug 25 16:59:03 piaware systemd[1]: Starting Lighttpd Daemon...
Aug 25 16:59:04 piaware systemd[1]: Started Lighttpd Daemon.
lines 166-210/210 (END)
That seems normal enough.
So when it’s not available, can you connect with ssh or ping it?
Not right now but when you have the issue.
Well when it was unreachable today via IP on graphs ect I could ssh it, But once i rebooted to restore graphs and it went down again I couldn’t ssh, until I rebooted it again. I will try again when it next goes down and see what happens.
If you ping it, does it come back as “unreachable” or “timed out”? Those can imply difference situations.
Right so currently I cannot access the IP of the PI again, nor can I SSH into it either, the below is the ping test in CMD. Yet the feeder is still sending data to FA, FR24 & ADSBX and the local IP is the correct one on FA feeder page,
That looks like a webserver issue and not a network issue. Packages are not getting lost ( you got 4 replies) but the response isn’t what is expected.
Did you define the dns server correctly on the Pi ?
Maybe you can show the result of the command ifconfig on the pi and ipconfig/all in a cod terminal on the computer ?
They should match
So I have checked the ipconfig from the computer (cant post it as its my work computer and don’t know what can be used on the cmd results that can be used to try and access it) I have checked the PIaware config.txt file and the DNS matches at 8.8.8.8 & 8.8.4.4
PI ifconfig
Funny you mention webserver as when I try to access tar1090 I do get the yellow warning box about backend/webserver/device not working correctly
When I check
sudo nano /etc/resolv.conf
I find
# Generated by resolvconf
nameserver 192.168.1.1
192.168.1.1 is my gateway (Wifi router). My router in turn is set to “get DNS from ISP” (AT&T in my case), so I presume that if my Pi tries to look for something inside my LAN the IP is resolved by my router (who assigned the IP address), and if it’s something out on the web, then my router passes the request on to whatever DNS my ISP specifies.
If you have the DNS for the Pi pointing directly (and only) to 8.8.8.8 outside your network, how would the Pi know where to feed internal data? It can resolve external (to your LAN) addresses - like FA’s - but internal to the LAN things would get lost. (Maybe - I’m pushing the boundary of my network admin knowledge).
Perhaps add your local router IP to the DNS on the Pi?
@tomvdhorst am I making any sense?
The DNS on the router is also set to 8.8.8.8 and 8.8.4.4 and the default gateway is the router IP address of 192.168.0.1 as was originally set at the time of instaling and from 1st day of feeding 112 days ago, nothing networking has changed only the fact I have come back from holiday recently, no new Internet devices have been added for months. Up until the last 2 to 3 days it’s worked without issues. I just don’t understand why it’s suddenly started to do it. My other PI at a family members house is set up exactly the same way with static IP & the same DNS and that’s working fine.
You could change one of the 2 dns addresses to your gateway as said by @SDMark now it tries to resolve to the webserver via the google dns server. So change 8.8.4.4 to the gateway of your home network and see if the problem still exists.
Normally the first hop of dns resolving is in the internal network and then second hop is in the outside perimeter of the network.
If not effective you can revert back in an instant
That just means the website is cached but it can’t get live data.
So no it doesn’t mean you can connect to the pi.
Well you can always Ctrl-F5 … it will properly not work then.
That’s not what that ping says at all, he’s getting unreachable replies from his own box.
The statistics … are kinda misleading.
@Jonseyt23 post your piaware network config.
probably you set wrong broadcast or something.
and yes that can cause all kinds of unexpected / intermittent issues.
or maybe you recently added another device to the network and used the same IP?
or maybe you put the static IP in the DHCP range … that’s not good either.
2 Likes