Observations with Failed Status

Hi,

I realized this morning (2020-12-11 00:11:00 UTC) that my observations are getting failed status. Even with my station online.

journalctl -f -u satnogs-client.service gave these errors:

-- Logs begin at Tue 2020-12-08 21:17:01 -03. --
dez 11 09:15:36 pu2lvm satnogs-client[319]:     return request('get', url, params=params, **kwargs)
dez 11 09:15:36 pu2lvm satnogs-client[319]:   File "/var/lib/satnogs/lib/python3.7/site-packages/requests/api.py", line 61, in request
dez 11 09:15:36 pu2lvm satnogs-client[319]:     return session.request(method=method, url=url, **kwargs)
dez 11 09:15:36 pu2lvm satnogs-client[319]:   File "/var/lib/satnogs/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
dez 11 09:15:36 pu2lvm satnogs-client[319]:     resp = self.send(prep, **send_kwargs)
dez 11 09:15:36 pu2lvm satnogs-client[319]:   File "/var/lib/satnogs/lib/python3.7/site-packages/requests/sessions.py", line 643, in send
dez 11 09:15:36 pu2lvm satnogs-client[319]:     r = adapter.send(request, **kwargs)
dez 11 09:15:36 pu2lvm satnogs-client[319]:   File "/var/lib/satnogs/lib/python3.7/site-packages/requests/adapters.py", line 529, in send
dez 11 09:15:36 pu2lvm satnogs-client[319]:     raise ReadTimeout(e, request=request)
dez 11 09:15:36 pu2lvm satnogs-client[319]: requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='network.satnogs.org', port=443): Read timed out. (read timeout=45)

Also when I try curl https://network.satnogs.org the response is:

curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

However, wget works.

Even restarting the station, I am still receiving failed status in all observations. But I already get more than 200 fine observations in the last days.

Can anyone point me a solution? Could be my API token expired?

Best Regards,

Jose Damico (PU2LVM)

Hm… on a similar problem people here suggest running sudo update-ca-certificates --fresh. Does this solves the issue?

Your API key has not expired.

1 Like

Worked fine! Thanks, I guess i will add a script in cron, to do it.

1 Like