Yesterday I had guests and we were out in the sun all day. In the evening I tried v3.2.0 on a public server (without restarting the server) and the same problem appeared again, different widths of the websdr front end parts, no frequency, no S meter.

I returned v3.1.1 on the public server, v3.2.0 still runs just fine on the test server. I note that the test server runs on Ubuntu 24.0.4 WITHOUT OpenCL and with an RSP1A receiver (that's my public port 8906).

This morning I downloaded the latest version v.3.2.0 on Debian Trixie and it has the same phenomen, the same problem as on the main server. Debian Trixie has OpenCL just like the public server on Ubuntu 24.0.4.

I only use OpenVPN when I'm at work, there's Fortinet there that prevents me from accessing dynamic domains (they "forgot" to block the vpn port).

PhantomSDR has been behind the nginx proxy server for months, everything worked fine until the latest version of phantom. I don't think nginx has any effect on the broken appearance of v.3.2.0.

I personally don't care which user uses which frequency, internally sometimes I give the command netstat -tuan | grep internal_ip_of_my_local_server:80'
Then with whois ip_from_user I see from which country the user came.

On v3.2.0 I like the new Spectrum look, I'm interested in AGC, I don't need statistics.
I am not interested in detailed statistics.

I've been professionally maintaining a computer network for several years and I'm tired of looking at and analyzing log files.

73!

Very good Darko, I'm very glad to read it!
Maybe the problem with users is the fact that you are behind a VPN. Can you please try this file in backend to see if it could solve the problem? If not, may I have some details about your VPN?
Don't forget to recompile backend and restart server.

QuoteTried to fix the problems Darko has mentioned, I've doubled checked all the backend files. AI has found some issues, fixed and all new uploaded again.
I hope there will be not any problems now with any OS....

It works fine on Debian 13 (Trixie) and Ubuntu 24.0.4 now. Thanks to the development team for the quick and successful fix. 

There is a small problem when I want to stop websdr via systemd, it takes maybe 20 seconds:

root@minipc:/home/darko/PhantomSDR-Plus# service websdr status
● websdr.service - PhantomSDRPlus WebSDR
     Loaded: loaded (/etc/systemd/system/websdr.service; disabled; preset: enabled)
     Active: deactivating (final-sigterm) since Fri 2026-05-01 07:40:16 CEST; 1min 24s ago
    Process: 349780 ExecStart=/home/darko/PhantomSDR-Plus/start-websdr.sh (code=killed, signal=TERM)
   Main PID: 349780 (code=killed, signal=TERM)
      Tasks: 5 (limit: 18771)
     Memory: 311.6M (peak: 320.3M)
        CPU: 11min 13.474s
     CGroup: /system.slice/websdr.service
             └─349784 build/spectrumserver --config config-rx888mk2.toml

svi 01 07:34:26 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:27 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:28 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:29 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:30 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:31 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:32 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:33 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:34:34 minipc start-websdr.sh[349784]: write_users_json: cannot open frontend/dist/users.json.tmp
svi 01 07:40:16 minipc systemd[1]: Stopping websdr.service - PhantomSDRPlus WebSDR...
root@minipc:/home/darko/PhantomSDR-Plus# ps aux | grep spectrumserver
root      400661  0.0  0.0   9580  2404 pts/2    S+   07:41   0:00 grep --color=auto spectrumserver
root@minipc:/home/darko/PhantomSDR-Plus#
That slows down the reboot for those 20 seconds, of course.
Not a big problem, I expect the server to restart as rarely as possible. 

73!

Tried to fix the problems Darko has mentioned, I've doubled checked all the backend files. AI has found some issues, fixed and all new uploaded again.
I hope there will be not any problems now with any OS....

In case you are looking for the different interfaces:

Standard port = Uber own interface, mine Heppen is set to port 80
Kiwi port = 8073
Websdr.org port = 8901
Hermes P2 port = 1234

So example:

https://websdr.heppen.be

You cannot view this attachment.

http://websdr.heppen.be:8901

You cannot view this attachment.

http://websdr.heppen.be:8073

You cannot view this attachment.

For port 1234 you need xxxHPSDR software, but I do not know how many users at the same time.

Well, it is maybe a good idea to include in the github all the previous versions in .zip, free to anyone that he wants to experiment.
As I can see there is no way to upload the file here, so I am going to do this.

So, now you can find all versions here:
https://github.com/sv1btl/PhantomSDR-Plus/tree/main/archives

QuoteWhat a pity Darko. I cannot think something that it could help you.

My servers are on Ubuntu 24.0.4. I'll try to install v3.2.0 on Debian 13 (Trixie) today. I have Ubuntu servers, maybe I have something that interferes with the normal operation of v3.2.0.

Everything is fine, we are testing. 

QuoteDo you want me to send you the zip of v.3.1.1

.
I have only compiled backup v3.1.1, please send me zip. Thanks!

QuoteCan you please send me your .toml file?

My config-rx888mk2.toml:
[server]
port=8905 # Server port
html_root="frontend/dist/" # HTML files to be hosted
otherusers=1 # Send where other users are listening, 0 to disable
#threads=2
#threads=8 #2
#threads=8 #4 #2

[websdr]
register_online=true  #false # If the SDR should be registered on https://sdr-list.xyz then put it to true
register_urls=[
  "https://sdr-list.xyz/api/update_websdr",
  "http://list.novasdr.fun/api/update_websdr"] # One or more directory endpoints that accept the same JSON payload
name="9A7AOF PhantomSDR+" # Name that is shown on https://sdr-list.xyz
antenna="Active Loop" # Antenna that is shown on https://sdr-list.xyz
grid_locator="JN86da" # 4 or 6 length Grid Locatlr shown on https://sdr-list.xyz and for the Distance of FT8 Signals
hostname="http://9a7aof.ddns.net" # If you use ddns or something to host with a domain enter it here for https://sdr-list.xyz

[limits]
audio=100
waterfall=100
events=100

[input]
sps=60000000 # Input Sample Rate
#fft_size=1048576
#fft_size=2097152
fft_size=4194304 # FFT bins for spectral analysis (very large for ultra-high sample rates)
#fft_size=8388608
#fft_size=16777216
#fft_threads=12 #16 #12 #8 #2
brightness_offset=-2 # Waterfall brightness offset. Reduce to negative if you see black regions in the waterfall
frequency=0 # Baseband frequency
signal="real" # real or iq
accelerator="opencl" #"none" # Accelerator: none, cuda, opencl, mkl
audio_sps=12000 # Audio Sample Rate
audio_compression="flac" # flac or opus
waterfall_size=1024 #2048
waterfall_compression="zstd" # zstd or av1
#smeter_offset=4
smeter_offset=5 # digital-only S-meter offset
analog_smeter_offset=5 # analog-only S-meter offset


[input.driver]
name="stdin" # Driver name
format="s16" # Sample format: u8, s8, u16, s16, u32, s32, f32, f64

[input.defaults]
frequency=3675000 # Default frequency to show user
modulation="LSB" # Default modulation

73!

What a pity Darko. I cannot think something that it could help you.
The newer version is now on:
http://lu5dnpwebsdr.sytes.net:8901/
http://hamradio.sv2yj.live:9002/
and me http://phantomsdr.no-ip.org:8900/
Soon it will be installed and on the other two servers here in Greece, and we'll see if there will be some kind of problems.

Do you want me to send you the zip of v.3.1.1 or you already have a backup?

P.S. Can you please send me your .toml file?

QuoteWell, the repo has now the new repo, all clean, without the older files. Maybe something I've messed writing the newer files over the older ones. Please retry.

Today I did a clean install again on both the test (RSP1A) and the public server (RX888MK2).

On the test server there is no frequency or S meter, it shows that the Spectrum slider is on even though it is not, parts of the server are of different widths...

On the public server after the first start I got a normal image in Chrome on two computers, on Firefox the same phenomen as on the test server, everything scattered, no frequency or S meter, unusable.

I entered my local network at home via VPN, tried to connect to the public server, in both Chrome and Firefox the same problem, no S meter, no frequency, parts of the PhantomSDR-Plus are of different widths, the Spectrum slider is on, no spectrum above the waterfall..

I did not edit anything, all scripts are original. I will leave the public server at v3.2.0 today.

73!

PS:
Restarting v3.2.0 via systemd scripts takes a very long time, sometimes I have to kill the spectrumserver process manually as root. I never had this problem with the previous version.
When I tried to switch from the correct analog to digital S-meter, the same error appeared, no frequency, no S-meter, the PhantomSDR-Plus sections are of different widths, the Spectrum slider is on and there is no spectrum above the waterfall...

Darko, 9a7aof

Tried a lot to reproduce your problem Darko, but not success. Clean install to my test server, at least 2-3 times. Every time no problem with install (with the corrected install.sh), and the server starts always.
Have you tried to reload your server after the first running? A simple refresh to the webpage, nothing else!
Well, the repo has now the new repo, all clean, without the older files. Maybe something I've messed writing the newer files over the older ones. Please retry.