I've no success with the new install.sh.

I'm back to 3.11 and everything running well. Emmanuel, also 3.11 is a wonderful piece of software!
Many thanks for your impact and a lot of work behind that. Software delopment is sometime like the first steps on the own feet - two steps forward and one time backward. 

Don't put the 3.2.0 at the can - is have some very interresting ideas.

Stay brave, Hendrik

Hello Manolis   

I think that issues of our fiends comes from VPN / reverse proxy and other...
In my mind theses safeguard are useless.
Phanthom is a standalone server without interest for hackers.

Now I will test my GUI mods and put 3.2.0 in production on the main server.
Sticked on Bookworm as a very stable release.

French and Spanish version of the Analog.svelte are in progress.
I will use moded version switch to change the language.
An other little mod: a button to go on https://hamdash.com
A fantastic App for propag prediction / meteo / cluster and a lot of other things useful for Hams.
This mod is in use on my main server.

I look for a faster UC ($$$! ) and will stick on 3.2.0 for a long time.
It's now the good season to work outside on a new fractal loop about 200M or more.
An interesting challenge to make the thing boadband and dual polarisation !

73's

 

Thank you Eric!
I have to say that this thing is already a nightmare!... 
I've done the last 3 hours:
- a clean install to my pc (ubuntu 24.04)
- a clean install to my test server (bookworm)
- a clean install to a friend's server (SV2YJ - Ubuntu 22.04)
No problems at all.
I am speechless... I have nothing more to add!..

Hello Guy's

3.2.0 compile and work without problem on my dev server running Debian 12 Bookworm.

It's an old Core I3 and RX-888 

You can test at http://orsat2.ddns.net:8080

73's

Ok, I think there is nothing more to do about it. I cannot reproduce the problem in my pc's, the newer server is installed in some other pc's too and it is working there, so I give up.

The latest github includes version 3.1.1, the latest stable for you Darko and Hendrik too.

This was the last update/upgrade of the PhanromSDR. No sense to try more updates, from the moment that the last version cannot work for everyone.

Hope enjoy the journey.

It is really a problem that the communication is only through the forum, but can you both retry with this install.sh?
I downloaded the latest from github, it was 3 minutes old, ran install.sh, nothing, the page crashes, I had to physically restart the computer, I couldn't kill the spectrumserver process (Debian 13 Trixie).

On a public computer, on Ubuntu 24.04, I first installed directly from github, the page crashed, no S meter, no frequencies. After that, I installed the latest install.sh from the forum, the same thing, everything crashed.

I think it would be a good idea to disable all scripts that are not absolutely necessary for the normal operation of PhantomSDR (statistics, users, support for websdr.org). The method of elimination might be able to find the cause of our troubles with v3.2.0.

Again, for the umpteenth time, I'm going back to v3.1.1 

73!

Very sorry about this.
It is really a problem that the communication is only through the forum, but can you both retry with this install.sh?

Also no luck with release 3.2.0.

I got here some of the same issues like Darko. After start:
- Volume is zero -> Display shows 50 %
- Mode is set to "USB" -> tml says modulation="AM"
- spectrum switch is on -> spectrum is off
- the frequency is only to see after mode switch (before set to 0)
- none by the 4 kinds of S-Meter is to see
- the yellow marker shows not the choosen frequency (middle of the band) but the RX tuning is OK
- no markers to see
- the "spectrumserver" needs now a long time (15 seconds) to finish

It seems the init is not runnig trough. Any ideas to detect the bug?

I use here Ubuntu 24 server with a fresh running install.sh.
http://mellesdr.rqhk191saz25euus.myfritz.net/

Best greetings from Berlin,
Hendrik

QuoteUntil yesterday Darko, your v.3.2.0 was working excellent on public server, except users, which were always with an IP address 127.0.0.1 That's way I've asked about your VPN.

The explanation for 127.0.0.1 is simple, nginx is on the same computer as PhantomSDR-Plus. It's a trick I borrowed from the Openwebrx distribution for RPI maintained by Stanislaw.
It converts the public port of Openwebrx (usually 8073) to port 80 on the same computer. That way I can reach the server locally without specifying an additional port, everything runs on port 80.

My VDSL router does NAT, so external port 8905 is sent to port 80 of the local PhantomSDR-Plus computer. Nginx converts that port 80 to local port 8905 and everything works, except printing a list of users with IP number 127.0.0.1

That's why I use that command in the command line to see the public IP addresses of users. My config for nginx looks like this:

[codeserver {
    listen 80 default_server;
    listen [::]:80 default_server;

    # SSL configuration

#    listen 443 ssl default_server;
#    listen [::]:443 ssl default_server;

    # Note: You should disable gzip for SSL traffic.
    # See: https://bugs.debian.org/773332

#    gzip off;

    # Read up on ssl_ciphers to ensure a secure configuration.
    # See: https://bugs.debian.org/765782
    #
    # Self signed certs generated by the ssl-cert package
    # Don't use them in a production server!

    include snippets/snakeoil.conf;

    set $upstream 127.0.0.1:8905;
        #set $upstream 127.0.0.1:6081;
        #set $upstream 192.168.3.11:8074;
       
    location / {
        proxy_pass http://$upstream;
        proxy_http_version 1.1;
        proxy_buffering off;

        # required for websockets
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
}
]

The problem with the actual IP number of the user in my case could perhaps be easily solved if the script instead of port 8905 looks at the traffic on ethernet port 80 of the computer where Phantom is running.

I repeat, these statistics mean nothing to me personally, I look at it from the command line. If there is a problem with traffic to and from my Phantom server , my provider is legally required to keep the log files, let the competent authorities ask them.   

And yes, from Croatia I can't connect the servers in Germany and Finland, it's been going on for months, since a colleague from Germany suggested that you add band-config.js to the src directory. I never, ever managed to connect to his server as a user.

Somehow it seems to me that the new statistics scripts want to retrieve something from the Internet that is inaccessible to me from Croatia, the form is not filled out and it distorts the entire front end of the new PhantomSDR server. (This is just my layman's opinion)

In the end, we are not professionals,
we are not pressed for deadlines, this is just fun.

73!

Until yesterday Darko, your v.3.2.0 was working excellent on public server, except users, which were always with an IP address 127.0.0.1 That's way I've asked about your VPN.
Anyway, trying to reproduce the problem you've mentioned has failed many times. Greek servers already running the newest version, the same in Argentina and Germany. I am waiting also Paulus to find time for a clean test install to his test server.