SatNOGS Client v2.1 release

fredy · November 18, 2025, 9:56am

Warning: Please read the notes and updates below before attempting any update!

UPDATE 2025-11-28 8:40 UTC:

Warning: Users running image with architecture armhf will have issues with upgrading. For now they should keep the old version. We are working on solving this issue.
Users with arm64 image are not affected but may get warnings in their log about matplotlib that can be ignored.
To find out which architecture you use you can run dpkg --print-architecture

SatNOGS Client v2.1 is released!

With this release (together with releases on various other components of the station software) we continue the work of the dockerized version and its architecture. Also we add support for LSF’s PHASMA mission for UHF and S-band. We also enhance the integration as addon for gr-satellites and fix various bugs and issues.

Notes:

Unfortunately there are still missing features in the dockerized version, you can find them in Missing_features section. Most notable the non-support of rotators and non-support of pre and post scripts. If you use/need any of these we suggest you not update to this version!
If you run the legacy version (non-dockerized one) then you can upgrade, if you don’t miss any of the missing features by following these instructions.
To find out if you run the legacy version, connect with ssh to your station and run sudo docker ps -a, if there is an error or doesn’t show any response listing a couple of containers then you are on the legacy version.
Alternatively you can setup your station from scratch for moving to the dockerized version, again if you don’t miss the missing features.
If you run the dockerized version, as described in Updating SatNOGS Software section.
Finally for those that know what they do, there is an alternative installation that could be unstable so not suggested to the average user. It can be found in Manual Installation of SatNOGS station stack (latest development versions, no docker, May 2025) ($4842563) · Snippets · librespacefoundation / SatNOGS / satnogs-docs · GitLab and it is a manual installation of the software. This may allow you to use the missing features but use it with caution as it is unstable. If you choose it, have in mind that you may need to install udev rules on your own for the sdr devices.

Thanks to everyone that helped with this release, it is a first and important step for moving to the next architecture of the station software that will bring nice features in combination with changes in SatNOGS Network and DB, stay tuned!

bali · November 18, 2025, 2:57pm

this is important. especially for sdr that have builtin bias-tee and connected to LNA without bias-tee support, or direct connected to short antenna like qfh, eggbeater

f6fkq · November 18, 2025, 10:12pm

This 2.1 version was installed from scratch this afternoon on my F6FKQ-UHF station. It works and solved the connection issue I had before with the version 1.9.x. Thank you for your outstanding support.

kerel · November 19, 2025, 3:04pm

Release Notes: satnogs-client 2.1

HS318 · November 20, 2025, 1:24am

I have just tried updating but the stanogs-client keeps restarting and not showing as online. any ideas as to why?

I have update all api keys and checked https paths and they are correct.

kerel · November 20, 2025, 2:27am

To diagnose, check the whole error log with sudo docker logs satnogs_satnogs-client. If this does not provide any new clue about whats happening, I recommend to raise the debug level to INFO. See the wiki page Client troubleshooting on how to do that. Feel free to ask more questions or discuss any news here!

HS318 · November 20, 2025, 5:45am

Many thanks I think I will start from new as multiple errors, this is just some of the issues.

ImportError: Error importing numpy: you should not try to import numpy from
its source directory; please exit the numpy source tree, and relaunch
your python interpreter from there.
Traceback (most recent call last):
File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 24, in
from . import multiarray
File “/usr/local/lib/python3.11/dist-packages/numpy/core/multiarray.py”, line 10, in
from . import overrides
File “/usr/local/lib/python3.11/dist-packages/numpy/core/overrides.py”, line 8, in
from numpy.core.\_multiarray_umath import (
ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 130, in
from numpy.**config** import show as show_config
File “/usr/local/lib/python3.11/dist-packages/numpy/**config**.py”, line 4, in
from numpy.core.\_multiarray_umath import (
File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 50, in
raise ImportError(msg)
ImportError:
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.
We have compiled some common reasons and troubleshooting tips at:

https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

* The Python version is: Python3.11 from “/usr/bin/python3”
* The NumPy version is: “1.26.4”
  and make sure that they are the versions you expect.
  Please carefully study the documentation linked above for further help.
  Original error was: libopenblas.so.0: cannot open shared object file: No such file or directory
  The above exception was the direct cause of the following exception:
  Traceback (most recent call last):
  File “/usr/local/bin/satnogs-client”, line 5, in
  from satnogsclient import main
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/**init**.py”, line 11, in
  from satnogsclient.scheduler.tasks import status_listener
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/scheduler/tasks.py”, line 15, in
  from satnogsclient.observer.observer import Observer
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/observer/observer.py”, line 17, in
  from satnogsclient.artifacts import Artifacts
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/artifacts.py”, line 5, in
  import h5py
  File “/usr/local/lib/python3.11/dist-packages/h5py/**init**.py”, line 33, in
  from . import version
  File “/usr/local/lib/python3.11/dist-packages/h5py/version.py”, line 17, in
  import numpy
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 135, in
  raise ImportError(msg) from e
  ImportError: Error importing numpy: you should not try to import numpy from
  its source directory; please exit the numpy source tree, and relaunch
  your python interpreter from there.
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 24, in
  from . import multiarray
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/multiarray.py”, line 10, in
  from . import overrides
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/overrides.py”, line 8, in
  from numpy.core.\_multiarray_umath import (
  ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory
  During handling of the above exception, another exception occurred:
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 130, in
  from numpy.**config** import show as show_config
  File “/usr/local/lib/python3.11/dist-packages/numpy/**config**.py”, line 4, in
  from numpy.core.\_multiarray_umath import (
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 50, in
  raise ImportError(msg)
  ImportError:
  IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
  Importing the numpy C-extensions failed. This error can happen for
  many reasons, often due to issues with your setup or how NumPy was
  installed.
  We have compiled some common reasons and troubleshooting tips at:
  https://numpy.org/devdocs/user/troubleshooting-importerror.html
  Please note and check the following:
* The Python version is: Python3.11 from “/usr/bin/python3”
* The NumPy version is: “1.26.4”
  and make sure that they are the versions you expect.
  Please carefully study the documentation linked above for further help.
  Original error was: libopenblas.so.0: cannot open shared object file: No such file or directory
  The above exception was the direct cause of the following exception:
  Traceback (most recent call last):
  File “/usr/local/bin/satnogs-client”, line 5, in
  from satnogsclient import main
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/**init**.py”, line 11, in
  from satnogsclient.scheduler.tasks import status_listener
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/scheduler/tasks.py”, line 15, in
  from satnogsclient.observer.observer import Observer
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/observer/observer.py”, line 17, in
  from satnogsclient.artifacts import Artifacts
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/artifacts.py”, line 5, in
  import h5py
  File “/usr/local/lib/python3.11/dist-packages/h5py/**init**.py”, line 33, in
  from . import version
  File “/usr/local/lib/python3.11/dist-packages/h5py/version.py”, line 17, in
  import numpy
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 135, in
  raise ImportError(msg) from e
  ImportError: Error importing numpy: you should not try to import numpy from
  its source directory; please exit the numpy source tree, and relaunch
  your python interpreter from there.
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 24, in
  from . import multiarray
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/multiarray.py”, line 10, in
  from . import overrides
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/overrides.py”, line 8, in
  from numpy.core.\_multiarray_umath import (
  ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory
  During handling of the above exception, another exception occurred:
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 130, in
  from numpy.**config** import show as show_config
  File “/usr/local/lib/python3.11/dist-packages/numpy/**config**.py”, line 4, in
  from numpy.core.\_multiarray_umath import (
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 50, in
  raise ImportError(msg)
  ImportError:
  IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
  Importing the numpy C-extensions failed. This error can happen for
  many reasons, often due to issues with your setup or how NumPy was
  installed.
  We have compiled some common reasons and troubleshooting tips at:
  https://numpy.org/devdocs/user/troubleshooting-importerror.html
  Please note and check the following:
* The Python version is: Python3.11 from “/usr/bin/python3”
* The NumPy version is: “1.26.4”
  and make sure that they are the versions you expect.
  Please carefully study the documentation linked above for further help.
  Original error was: libopenblas.so.0: cannot open shared object file: No such file or directory
  The above exception was the direct cause of the following exception:
  Traceback (most recent call last):
  File “/usr/local/bin/satnogs-client”, line 5, in
  from satnogsclient import main
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/**init**.py”, line 11, in
  from satnogsclient.scheduler.tasks import status_listener
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/scheduler/tasks.py”, line 15, in
  from satnogsclient.observer.observer import Observer
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/observer/observer.py”, line 17, in
  from satnogsclient.artifacts import Artifacts
  File “/usr/local/lib/python3.11/dist-packages/satnogsclient/artifacts.py”, line 5, in
  import h5py
  File “/usr/local/lib/python3.11/dist-packages/h5py/**init**.py”, line 33, in
  from . import version
  File “/usr/local/lib/python3.11/dist-packages/h5py/version.py”, line 17, in
  import numpy
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 135, in
  raise ImportError(msg) from e
  ImportError: Error importing numpy: you should not try to import numpy from
  its source directory; please exit the numpy source tree, and relaunch
  your python interpreter from there.
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 24, in
  from . import multiarray
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/multiarray.py”, line 10, in
  from . import overrides
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/overrides.py”, line 8, in
  from numpy.core.\_multiarray_umath import (
  ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory
  During handling of the above exception, another exception occurred:
  Traceback (most recent call last):
  File “/usr/local/lib/python3.11/dist-packages/numpy/**init**.py”, line 130, in
  from numpy.**config** import show as show_config
  File “/usr/local/lib/python3.11/dist-packages/numpy/**config**.py”, line 4, in
  from numpy.core.\_multiarray_umath import (
  File “/usr/local/lib/python3.11/dist-packages/numpy/core/**init**.py”, line 50, in
  raise ImportError(msg)

fredy · November 20, 2025, 6:23am

@HS318, If possible, starting from scratch seems to be the easiest solution to move to the new version.

However for future reference and possible debugging, can you tell us which version you ran and how did you perform the update to this version?

Thank you!

HS318 · November 20, 2025, 5:19pm

Hi it was a older Legacy version docker v1. my client version was 1.8.1

At first I ssh, logged in and then loaded satnogs-setup and ran the update.

after this I then ran curl -sfL https://satno.gs/install | sh -s –

after updating I was still getting a msg to update to docker v2 but I could still enter the satnogs-setup up and updated my basic setttings but after this it would not connect and the client would then restart.

[DEPRECATION WARNING]: community.docker.docker_compose has been deprecated.
This module uses docker-compose v1, which is End of Life since July 2022.
Please migrate to community.docker.docker_compose_v2. This feature will be
removed from community.docker in version 4.0.0. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.

fredy · November 20, 2025, 6:34pm

@HS318 thanks for the details, these are very helpful!

@Acinonyx any idea? Maybe it needed and apt-get update and apt-get upgrade maybe?

HS318 · November 20, 2025, 7:28pm

Success the fresh install is up and running and connected.

HS318 · November 21, 2025, 12:44am

I’m still having issues with getting the waterfall to display, any ideas what may be wrong?

fredy · November 21, 2025, 8:06am

With a quick look the configuration looks good. Check Troubleshooting - SatNOGS Wiki and copy paste here the logs, maybe there is an error that causes the waterfall issue.

PE0SAT · November 21, 2025, 8:26am

The value antenna: "rx", should be capital RX

Jan | PE0SAT

HS318 · November 21, 2025, 4:23pm

Fantastic, thank you that has fixed it. Always something simple like being upper or lower case.

PE0SAT · November 24, 2025, 1:31pm

Manual SatNOGS-client docker container(s)

For those with SatNOGS-client, Linux and docker experience I have made a docker compose template that can be found at the following location.

This was created for my own, already present docker host and the curl -sfL https://satno.gs/install | sh -s -- solution would fail because the OS was different and docker already installed.

The steps that are automatically done by the script like installed /etc/udev/rules.d/files for you specific SDR devices and settings permissions should be done manually if you use the template.

Read the readme.txt file and download the docker compose file, afterwards edit the compose file all <station ID> values to your specific configuration.

Jan | PE0SAT

bali · November 25, 2025, 3:02am

lsf/LSF-GUIDE.md

main

# Guide for LSF satnogs-client with docker compose

## Intro
This is aimed for those who want to try out the client in docker and thinks it's a bit too complicated.<br>
I will try to explain the basic concepts and how to get up and running.<br>
My preferred distro is Debian 11 (bullseye) and this guide will be tailored for it, but there should only be small differences to others.<br>

## Basic description of Docker
[Official overview](https://docs.docker.com/get-started/overview/)

***Images*** are usually hosted on a registry, for example hub.docker.com, from where you can pull them to your system.
They are the complete software bundled to run an application, in this case a debian image and a lot of packages installed that is required for satnogs-client.<br>
***Container*** is the running instance of an image and is basically an isolated environment where you run the app.
They are always start fresh from the image and can be modified, but it's non-persistent so after a stop any changes are lost.<br>
***Volumes*** is either a persistent storage for containers or bind-mounted to your host for configuration or storage.

***Compose*** This is the main difference from the [old guide](../GUIDE.md), where everything is controlled with the [docker-compose](docker-compose.yml).
In this file all the different services (essentially containers) are specified and all it's settings and relationships between them.
The containers exist on a separate network in this configuration, so rigctld runs in its own container and the satnogs-client talks to it over this network.
What this means is that you don't need a bunch of scripts to start/stop/update everything.

This file has been truncated. show original

ea5wa · November 26, 2025, 9:55pm

Hi there:

Maybe someone could help me…..

I had try to update from 1.8.1 to 2.1 without success. I’m using this link: https://wiki.satnogs.org/Raspberry_Pi

Process takes so long but finalize without any error (as far as I can see), but checking if the container is running, the result is “No such container satnogs_satnogs-client”

Then, after a long long time…. I have satnogs-setup

After setting up, nothing happens and my station is offline

Any help is appreciated

fredy · November 27, 2025, 9:38am

@ea5wa what do you get when running sudo docker ps -a?

PE0SAT · November 27, 2025, 11:56am

Hi @ea5wa

I wish it was different but updating from 1.8.1 with Debian bullseye as the host OS will cause problems if you use the curl -sfL https://satno.gs/install | sh -s -- method. It is possible to get the 2.1 client running but that needs a lot of manual actions and knowledge.

So for now, note all your settings and start with a fresh install and the run the curl command.

Jan | PE0SAT