First Start: satnogs-setup update with warning

Hello !

I’m new an i try install my Raspberry with the last Satnogs img.
I follow the wiki and for the initial setup:
sudo satnogs-setup
I try to update but i obtain this error:

and i don’t come back into the setup interface.

Other trouble:
I can’t check my satnogs-client version because i see: “unkown”

Thank you for your help!

Hi @vincent74 and welcome to the community!

Could you try to run, before getting into satnogs-setup the commands bellow:

apt-get update
apt-get upgrade

and let us know how it went?

Hello @fredy ,

Yes, I forgot to say that I also had two errors with these commands … (sorry)

With sudo apt-get update:

With sudo apt-get upgrade:
(See next post du to new user forum limitation)

sorry for my lack of precision

It looks like that there is a connection issue with connecting to the opensuse build server.

Could you try to run ping (use ctrl+c for exiting ping command after 2-3s).

Probably you have done this several times, but just in case, perform a reboot of the device and check again.


ping for the IP work too, but not in the update command:
(See second post due to new user limitation)

Hm… can you try what is described here too and let us know. It could be the signature issue.

Thank but unfortunately:

Space before InRelease is normal ?

In my web browser:
-> work

but ./ InRelease
-> don’t work

The syntax is not for browser but for apt, and it says on choose ./ (the current directory) the subfolder InRelease.

Not sure why it doesn’t work for you, as it says the connection failed my guess is that something goes wrong with the network. I’ve just run it on my station and this is what I got:

pi@raspberrypi:~ $ sudo apt-get update
Hit:1 buster InRelease
Hit:2 buster InRelease
Hit:3 trusty InRelease
Get:4 ./ InRelease [1,574 B]
Get:5 ./ Packages [59.9 kB]
Fetched 61.4 kB in 3s (24.3 kB/s)
Reading package lists... Done

Just in case… can you also check with the date command that the date and time is right?

thank you for your patience

Your suggestion is good, I had a problem on my network with my firewall box.
There was a rule (which I didn’t know by default) that blocks http links with ./
(Triggering conditions: A URL containing a dot-slash ("./") has been detected.)

I changed the rule for my raspberry and this problem now seems to be resolved.
Thank you very much for your help and the time spent.

1 Like

Glad to hear that is solved! :slight_smile:

1 Like