One last thing I would like to share with you.
From the moment you have a working v.3.2.0, you have now the opportunity to be shown on https://sdr.shbrg.nl/sdr/ AND on websdr.org map.
The modification is made in .toml file you use as follows (this is mine):

[websdr]
register_online=true # Enable directory registration updates
register_urls=[
  "https://sdr-list.xyz/api/update_websdr",
  "https://www.shbrg.nl/api/update_websdr"
  ] # One or more directory endpoints that accept the same JSON payload
name="SV1BTL CATsync PhantomSDR+" # Name that is shown on https://sdr-list.xyz and/or https://sdr-list.xyz/api/update_websdr
antenna="EndFed 160-10m." # Antenna that is shown on https://sdr-list.xyz
grid_locator="KM17VX" # 4 or 6 length Grid Locatlr shown on https://sdr-list.xyz and for the Distance of FT8 Signals
hostname="phantomsdr.no-ip.org" # If you use ddns or something to host with a domain enter it here for https://sdr-list.xyz

[websdr.org]
enabled    = true
public_host = "phantomsdr.no-ip.org"
public_port = 8900
qth        = "KM17VX"
description = "SV1BTL PhantomSDR+ Athens GR"
email      = "sv1btl@otenet.gr"
logo        = "logo.jpg" #located in frontend/public, you can replace it with your own

A recompile of frontend maybe is needed so logo.jpg to be placed in the folder "dist", and restart of the server of course.

You can try....

Well, I think,
I FOUND IT

Two wrong files in frontend/src and the syntax of markers.json.

In a bright new Ubuntu 24.04 the installation and running without problems.

P.S. about "statistics". Please check if a new folder "log" there are new generated files with extension .jsonl

P.S.2 markers.json generated by update-markers.sh, works for me, but then the syntax of markers.json is different.

markers.json
{
  "markers": [
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
    {
      "frequency": 100000,
      "name": "LORAN",
      "mode": "AM"
    },
......
  ]
}

mymarkers.json in frequencylist folder is in this format
[
    {
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
.....
    {
      "frequency": 28585000,
      "name": "28585",
      "mode": "USB"
    }
]

instead of the original markers.json, located in github:
{
  "markers": [
{
      "frequency": 77500,
      "name": "DCF77",
      "mode": "CW"
    },
......
    {
      "frequency": 28330000,
      "name": "FreeDV",
      "mode": "USB"
    }   
  ]
}


Confirmed!
Great job Darko, thank you. Without or empty "markers.json" release V3.2.0 runnig here very well too!

Best regards,
Hendrik

I found that markers.json crashes and distorts v3.2.0

I tried with markers.json generated by update-markers.sh, it crashes. I tried with manually generated markers.json, it crashes.

It only helps when I delete markers.json, then the page looks normal (without markers).

I turned off the proxy, the Users button seems to work, I'm not sure about the Stats button.

73!
Darko, 9a7aof

P.S.
http://orsat.ddns.net:8080/ and
http://lu5dnpwebsdr.sytes.net:8901/
does NOT have markers.json.
 

I will try my best

I just got word from Nathan, that Ubersdr registers automatically at sdr-list.xyz and it seems it's done from the uber-instance-list.

So we do not have to configure anything.

All Ubers online are registered. Not sure if need to say yes/no in the config, mine is set yes.

Hope to get more info later.

Quote from: magicint1337 on May 03, 2026, 04:55 PMHey, yes, ill take over on this Part then, i will credit SV1BTL and all other contributors for their work. Ill build the "master" version of all websdrs now. With everything combined. It may take some time tho but it will be as stable as possible with all features. As the goal of NovaSDR was exactly that, novasdr is extremly robust but lacks features. Which will now move into it then the 1.0.0 of novasdr will be released

I am looking forward to this dear Steven, and I wish you all the best from now on, to offer us a really stable and rich software!

Hey, yes, ill take over on this Part then, i will credit SV1BTL and all other contributors for their work. Ill build the "master" version of all websdrs now. With everything combined. It may take some time tho but it will be as stable as possible with all features. As the goal of NovaSDR was exactly that, novasdr is extremly robust but lacks features. Which will now move into it then the 1.0.0 of novasdr will be released

For me 3.2.0 is a masterpiece.

Stopping the dev is a good idea. Time is now to customise a stable release. 

One more time, congratulations Emmanuel for this fine job.

Since V3, phantom work like thousand dollars rigs !

If you can, try full size loops antennas

Thanks and 73's my friend

Hendrik, I will not abandon v.3.2.0, but I'll include v.3.1.1 also in the github in the folder archive.
Today I've made a virtual installation in Trixie 13 via VMware. Success, some minor issues, fixed, update GitHub, end!

You are right that "two steps forward and one step backward" is regular and normal in software development, specially when the development is not made by programmers, but by amateurs like me.

Anyway, I am glad that v.3.1.1 is working good for you (and Darko). To be honest, after this last try with v.3.2.0 I was thinking to stop the project, because I had not really something new to offer. Reality came to force me to stop anyway.

So, thank you very much all you partners and co-travellers to this long journey, from the very first release of PhantomSDR to today's versions. Your support, remarks, beta-testing, patient and giving courage were something precious for me to go on.

Please enjoy your software and I hope no more problems from now on. Let us concentrate now to receiving antennas, eliminating QRM, etc. etc.