WS per IP is WEB-SOCKETS per IP, meaning you can limit the number of sessions per IP.
Beware a websocket isn't a single session, it could be more.
Typical, no need to change it.

Did you put your markers in config/overlays/ ?

Also there is a mistake in your markers at the bottom:

      },
      {
      ]
}

that must be

        }
  ]
}

The last marker end with } but then you say , and {

The last marker should be this, including the end of the file:

        {
            "frequency": 439475000,
            "name": "ON0LG",
            "mode": "FM"
        }
  ]
}

As such they do not work. Also you need to zoom in quite a bit to see them.

Hello All
Whre are a discription of all functions / commands in the config.json

What is this fuction: "ws_per_ip": 50

Interesting is, that after a certain time, the NovaSDR goes into a sleep-mode.

And the markers with the file markers.json does not work in my case.

73 de HB9RYZ
Wolfgang

Hello magicint1337
Thanks for the NovaSDR v2.0 which is running excellent since months at our remote site in the Swiss Alps at 1'660m.
My NovaSDR ist listed at https://sdr-list.xyz/ but the access does not work.

This is the link of my NovaSDR behind my reverse-proxy server:
https://novasdr.rigiremote.ch/

I guess, there is problem with the port.

And this is the link of my PhantomSDR-Plus v1.5.4 also behind my reverse proxy server
This PhantomSDR-Plus is still my favorite :-)
https://phantomsdr.rigiremote.ch/

Phil helped me yersterday to get the latest version v0.3.7 of the NovaSDR with the brand new GUI running on a HP Mini PC EliteDesk with a RX888MK2 SDR at my home QTH with an attached Active Dipole.
http://sidler.homeip.net:9003/

Thank you very much for your work :-)

73 de HB9RYZ
Wolfgang

Hi all,

When you use the install script, and you select the Soapy-support, it will install Soapy.
This is not a problem unless you installed Soapy yourself because of unsupported drivers in the distro.
Like a Funcube or the RSP1A with 2.13 API drivers.
When you do this, you end up with 2 Soapies and it conflicts.

See all details here:

https://github.com/Steven9101/NovaSDR/issues/24

It's all described in there, but a simply way to see if you have 2 Soapies it testing this:

/usr/bin/SoapyUtil --help

If that respons, you have the distro install. Now test:

/usr/local/bin/SoapyUtil --help

If that responds too then you have two versions installed and you have to remove one of them.

See the github topic for more info.

But before you upgrade to 0.3.6 or newer, check if you have more then 1 Soapy installed. Else it will not work correctly or even fail to setup/configure/run.

I agree with Bas ON5HB.

I do believe it's better to remove depriciated, just list them as Phantom+ as there are no other versions.
Anything simply mark them as -Unknown version- when you don't know it.

Hi SV1BTL,

Just to clear things up since I am both the original maintainer of PhantomSDR+ and the admin of sdr-list.xyz the labels on the map aren't meant as a value judgment.

The SDR list API had to be extended so it can handle both older PhantomSDR+ instances and the newer NovaSDR ones at the same time. Both are welcome on the list, and I wanted a way to visually indicate which software an instance is running without requiring changes to all existing PhantomSDR+ installations.

The problem is that from the API side, I can't reliably detect whether an instance is running 1.5.4, 1.7.0, or some modified fork. There's simply nothing in the original PhantomSDR+ protocol that clearly identifies the exact version in a standardized way. So the categorization isn't about whether a specific server is actively maintained or not it's just a structural distinction based on software family and architecture.

When the original PhantomSDR+ repo was marked as deprecated, that reflected the shift in development focus toward NovaSDR. It doesn't mean community-driven PhantomSDR-Plus versions are obsolete or discouraged. It just marks the architectural transition.

There's no competition here, and there's definitely no attempt to downplay the ongoing work on PhantomSDR-Plus. The labeling was simply the cleanest technical solution without breaking compatibility or forcing updates on every existing Phantom installation.

Hope that clarifies the intention.

Definition of "deprecated" (from Google):

]What Does Deprecated Mean?
In the context of software development, deprecated refers to a feature, function, or practice that is disapproved of and discouraged from use. It is not yet removed from the software but is marked for potential removal in future versions. The term is derived from the verb deprecate, which means to express disapproval or to consider something as being of little value.
When a feature is deprecated, it typically means that there is a better or more efficient alternative available, and the deprecated feature may no longer be supported or maintained. Developers are encouraged to transition to the newer alternatives to ensure compatibility and avoid potential issues in the future.

As, I can see on the map https://sdr-list.xyz/ the OTHER instances of servers that they are NOT NovaSDR, are "Obsolete", "Legacy", "Deprecated" etc !...

Well the fact is that from the first version of PhantomSDR-Plus, there are many newer instances, because of the Open Source. PhantomSDR-Plus has been "jumped" in June 2025 from version 1.5.4 to v. 2.0.0 a version that didn't supported for the 6 months of its "life". And then the NovaSDR appeared as a totally new approach. My opinion is that the v.2.0.0 was only an unsuccessful "brake", because some useful futures of the v.1.5.4 were not included and nobody wanted to make this version to work more efficiently for the End User.

I have to inform the users of this forum that PhantomSDR-Plus is dynamically updated from the version 1.5.4 to the recent 1.7.0 (https://github.com/sv1btl/PhantomSDR-Plus), continuing the evolution of the older instances. Last update/upgrade took place last week, adding new features and focusing to the stability and performance. Much more have to be done, but the continuously updated server's software of "older" PhantomSDR-Plus is far away from the terms "Obsolete", "Legacy", "Deprecated" etc. So the label "Deprecated Software" which means "avoid to use", or "disapproval or to consider something as being of little value" is very far away from the Truth.

There is not any kind of competition here. Steven is doing a really great job with NovaSDR, as he did with PhantomSDR+ and the open source helps to modify the server's software. BUT, PhantomSDR-Plus is still alive, updated, upgraded and today is as "new" as NovaSDR is, because there are some people that support it and working on it, so the newer versions have nothing to do with the older ones.

So please, "Deprecated software, which is disapproved of and discouraged from use, as being of little value" is something that is not true. Of course, the map and the list belong to the admins, and they have the right to describe what they want to describe, but I feel the need to mention what the truth is.

Best Regards, Emmanuel, SV1BTL

Hi all,

There are benchmarks added to the novasdr program.
Here is an example:

time ./novasdr-server benchmark cpu-fft-complex 1024 1024000
Run fft_benchmark for: iterations=1024 fft_size=1024000 is_real=false accelerator=None ...

run ./novasdr-server benchmark --help to see all benches you can do.

It can help you decide what fft_size is best for your system and if it's faster via GPU or non-accelerated.

It slipped in a few weeks ago

root@Websdr:/opt/novasdr# ./novasdr-server benchmark --help
Run benchmark

Usage: novasdr-server benchmark [OPTIONS] <KIND> [ITERATIONS] [FFTSIZE]

Arguments:
  <KIND>        [possible values: cpu-fft-complex, cpu-fft-real, cl-fft-complex, cl-fft-real, vk-fft-complex, vk-fft-real, ssb]
  [ITERATIONS] 
  [FFTSIZE]     

The 'time' command will time how long very test takes.

All info to be found here.

https://github.com/Steven9101/NovaSDR/issues/22

As my usercount kept growing, but no users where online, or just a few.

I suspected it to be wrong as my router confirmed the traffic upload to be nothing, while Phil had 6mbit up....