I may have inadvertently blocked something! Here is my piaware-status output:
$ piaware-status
PiAware master process (piaware) is running with pid 29858.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.
no program appears to be listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.
got 'couldn't open socket: connection refused'
dump1090 is NOT producing data on localhost:30005.
...
$
The lighttpd response on port 80 is the 403 error. (Port 8080 is fine).
How can I restart the specific services (excluding the UAT ones) since reboot doesn’t seem to help?
When nothing makes sense for me, I usually try the Brutal but Effective method, Start at a new Flightaware Piaware image or Raspberry Pi image and install Piaware and Dump1090 on a different MicroSD card. Edit the /boot/piaware-config.txt file with your login details and your feeder-id info. You can rework the older sd card on the side to get something to work later, but you ensure your hardware / antenna/ cables are working. Just what I had to do a couple of times when something just did not work. Have fun with the hobby. You got this.
@astrodeveloper, full agreement because the rebuilding one works flawlessly if the feeder-id is handy. However, I was hoping to learn some troubleshooting tips.
I have two receivers. The one that is working (as expected) lets lighttpd respond with a PiAware text string on port 80. Something must have flipped the errant receiver for its lighttpd to return HTTP 403.
