All of a sudden it looks like something is broken and I don’t know where to start to try to resolve it so if someone can assist I would really appreciate it
I tried a reboot of the physical device and now I cannot access the interface at all which is not a good sign.
Try a new power supply
Is your dongle connected properly ?
The system tells you that the connection with the dongle is lost.
Did the rasberry get a new IP adress ? Are you using a fixed ip on the system?
Yes I have reseated the dongle
Unfortunately after rebooting the device from the management page it totally dropped off my network and I have been unable to do anything with it since. I have swapped to a new power supply, connected it to a different switch port, replaced LAN cable
My other two PI’s show a red light and a intermittent green light but this one just shows a solid red light and no SD card access light.
I tried moving the micro SD to another know working Pi and rebooting it and that didnt help.
I am guessing the card is corrupt again which is the 2nd time in just a few weeks…
Which OS image you have written to the microSD card?
I am following the instructions here: ADSB.im and using the “Raspbian based image for all 64bit capable Raspberry Pi”
To ensure there isn’t an issue with that card I am replacing it with a brand new fresh in the packet MicroSD card.
1 Like
That is a good aproach to ascertain if the the problem is caused by microSD card or something else.
I had similar problem once, and when I tried to re-write the image, the RPi Imager gave error. Apparently it seemed the card has failed, but I decided to try full-format of card (i.e. over-write with zeros). For this purpose I used SD Card formator of SD Card foundation. After over-write format, the microSD card worked OK.
1 Like
After doing a full rebuild I have booted the Rpi with the newly written card. It is connected via ethernet and I can see it on my network but when I go to http://adsb-feeder.local to complete the setup I am unable to find it.
Maybe you can check in the router what the name of the new system is. It might be the case that the DNS is looking for the old system and that one is absent.
Another option is to reboot the router so the old dns entry is discarded. Once rebooted check if you can get to the new system.
If the system is online you can also get to it via the browser if you put in the correct IP address.
2 Likes
On the router it identifies as “ADSBFEED.Local” Also running an “Angry IP Scanner” it identifies correctly and is on the IP I would expect.
I have rebooted the router this morning to have another try and still no luck.
I have also tried browsing to the correct I.P. through the browser and get "This site can’t be reached
192.168.1.78 refused to connect.
Try:
-
Checking the connection
ERR_CONNECTION_REFUSED"
@davewill2010 This little guy is fighting you a lot 
My advice would be to restart again.
When you burn the image with the rapsberry Pi imager (highly recommended) make sure you enable SSH access to the system under the customisation options. Also set a user name and a password.
Use password authentication ans the option.
This will enable you to get into the system if needed so you can check what is going on on the Pi if the webserver of adsb-im doesn’t run.
Once done, boot up the system and see it you can reach it again via the hostname
If not, try to login via Putty on the IP adress with the username and password you created when burning the image.
If you’re certain it’s not the sd-card, maybe the pi is just broken.
Well the good news Tom is I did enable SSH and have been able to log into it over SSH.
Any ideas for where I go from here?
That was my thought also so I tried the microSD in a known working Pi and got the same results.
So you can login over SSH into the system that is the good news.
Now we have to investigate why the webserver isn’t responding.
When going to this page you should get a listing of the available adsb.im sites on your network
the support channel for the image is located here:
or maybe @dirkhh can assist you on this forum since he is he guy that created this setup and he would be far more knowledgeable about it then I am.
If you can ssh into the feeder image, you can check if the web UI is running
systemctl status adsb-setup
assuming that shows you the expected result (the second line in the output should start Active: active (running) the next thing to look at would be
tail -50 /run/adsb-feeder-image.log
any errors?
Hi Dirk,
From the first command I get the following: “Unit adsb-setup.service could not be found”
you are not logged into the adsb feeder image then.
I have switch’s any other two Rpis off to avoid any confusion so the only only left is the adab feeder.
Would you advise reimaging it?
Thanks
David