RROR - 401 Client Error: Unauthorized for url

I decided to reload my statnogs ground station software from scratch and it is not connecting to the network. I have checked and set the API key from my ground station dashboard carefully, but this does not seem to be the problem.
Here is the error…

pi@raspberrypi:~ $ systemctl status satnogs-client
● satnogs-client.service - SatNOGS client
Loaded: loaded (/etc/systemd/system/satnogs-client.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2023-09-02 17:59:32 UTC; 6min ago
Main PID: 400 (satnogs-client)
Tasks: 4 (limit: 1596)
CPU: 9.156s
CGroup: /system.slice/satnogs-client.service
└─400 /var/lib/satnogs/bin/python /var/lib/satnogs/bin/satnogs-client

Sep 02 17:59:44 raspberrypi satnogs-client[400]: r = adapter.send(request, **kwargs)
Sep 02 17:59:44 raspberrypi satnogs-client[400]: File “/var/lib/satnogs/lib/python3.9/site-packages/requests/adapters.py”, line 565, in send
Sep 02 17:59:44 raspberrypi satnogs-client[400]: raise ConnectionError(e, request=request)
Sep 02 17:59:44 raspberrypi satnogs-client[400]: requests.exceptions.ConnectionError: HTTPSConnectionPool(host=‘network.satnogs.org’, port=443): Max retries exceeded with url: /api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&a>
Sep 02 18:00:49 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
Sep 02 18:01:45 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
Sep 02 18:02:45 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
Sep 02 18:03:46 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
Sep 02 18:04:45 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
Sep 02 18:05:47 raspberrypi satnogs-client[400]: satnogsclient.scheduler.tasks - ERROR - 401 Client Error: Unauthorized for url: https://network.satnogs.org/api/jobs/?ground_station=201&lat=38.555972&lon=-78.062523&alt=186
lines 1-19/19 (END)

Here is my configuration…
{
“versions”: {
“satnogs-client”: “1.8.1”,
“satnogs-client-ansible”: “202209101521”,
“satnogs-flowgraphs”: “1.4-1”,
“gr-satnogs”: “2.3.1.1-1”,
“gr-soapy”: “2.1.3.1-1”,
“gnuradio”: “3.8.2.0-14”,
“satnogs-config”: “0.13.2”
},
“state”: {
“is-applied”: true,
“pending-tags”: null
},
“system”: {
“date”: “2023-09-02T17:53:27.049429+00:00”,
“distribution”: {
“DESCRIPTION”: “Raspbian GNU/Linux 11 (bullseye)”,
“RELEASE”: “11”,
“CODENAME”: “bullseye”,
“ID”: “Raspbian”
},
“pending-updates”: true,
“platform”: {
“system”: “Linux”,
“node”: “raspberrypi”,
“release”: “5.15.61-v7+”,
“version”: “#1579 SMP Fri Aug 26 11:10:59 BST 2022”,
“machine”: “armv7l”
},
“memory”: {
“total”: 966930432,
“available”: 780263424,
“percent”: 19.3,
“used”: 130113536,
“free”: 484859904,
“active”: 140042240,
“inactive”: 267153408,
“buffers”: 37814272,
“cached”: 314142720,
“shared”: 737280,
“slab”: 37191680
},
“disk”: {
“total”: 15336914944,
“used”: 3787243520,
“free”: 10871656448,
“percent”: 25.8
}
},
“configuration”: {
“satnogs_antenna”: “RX”,
“satnogs_api_token”: “[redacted]”,
“satnogs_rf_gain”: “32.8”,
“satnogs_rx_samp_rate”: “2.048e6”,
“satnogs_soapy_rx_device”: “driver=rtlsdr”,
“satnogs_station_elev”: “186”,
“satnogs_station_id”: “201”,
“satnogs_station_lat”: “38.555972”,
“satnogs_station_lon”: “-78.062523”
}
}

Any ideas?

This is still likely the api key, no additional spaces, directly copied and pasted ?
The only headers used is the token/api key.

Yep, I hate to admit it, but it was indeed the key…

Thank you for pushing me back in the right direction…

Bob, KO2F

1 Like