[BUG] WSJTX MULTICAST not working

[fbertu]

Describe the Bug

WSJTX MULTICAST not working

To Reproduce

N/A

Expected Behavior

that it correctly takes the configuration and can read the data from the remote WSJTX.

Screenshots

Environment

• OS: Raspberry Pi OS]
• Browser: Chrome 146.0.7680.165
• OpenHamClock Version: 26.1.3
• Running As: Electron app

For Raspberry Pi Users

• Pi Model: Pi 4 4GB,
• Pi OS Version: "Debian GNU/Linux 12 (bookworm)"

Console Errors

n/a

Regards,
Fernando (LU9EOB)
73!

[fbertu]

[alanhargreaves]

OK, if you are running the wsjt-x relay from the server you don't need to worry about setting the multicast stuff in the client. That is for folks not running a server who have to download on and run one.

The setting you have in .env look like they should be ok.

Could you confirm for me that

• you have this address and port configured in wsjt-x
• you have other applications receiving packets with this multicast address

[alanhargreaves]

/assign

[fbertu]

Yes. I have other programs on my local network that receive the information sent by WSJTX via multicast.

So the IP address loaded is correct, since I use the same one in all the apps.

Regards,
Fernando.

[alanhargreaves]

The screen you are seeing is the screen that you get when we are waiting to receive our first decode.

I have a similar configuration (not on a pi)

alan@alans-mbp openhamclock % grep '^WS' .env
WSJTX_ENABLED=true
WSJTX_UDP_PORT=2237
WSJTX_MULTICAST_ADDRESS=224.0.0.1

and I get that screen when I'm not running wsjt-x or when it has not had any decodes for a while.

When you start openhamclock, do you see anything in the console log like:

[WSJT-X] UDP listener on 0.0.0.0:2237
[WSJT-X] Joined multicast group 224.0.0.1

with the address you are using displayed?

It should show up just before the logo.

[fbertu]

[image: image.png] El jue, 26 mar 2026 a las 21:51, Alan Hargreaves ***@***.***>) escribió:

…

*alanhargreaves* left a comment (accius/openhamclock#846) <#846 (comment)> The screen you are seeing is the screen that you get when we are waiting to receive our first decode. I have a similar configuration (not on a pi) ***@***.*** openhamclock % grep '^WS' .env WSJTX_ENABLED=true WSJTX_UDP_PORT=2237 WSJTX_MULTICAST_ADDRESS=224.0.0.1 and I get that screen when I'm not running wsjt-x or when it has not had any decodes for a while. When you start openhamclock, do you see anything in the console log like: [WSJT-X] UDP listener on 0.0.0.0:2237 [WSJT-X] Joined multicast group 224.0.0.1 with the address you are using displayed? It should show up just before the logo. — Reply to this email directly, view it on GitHub <#846?email_source=notifications&email_token=AHP523OTC7QE6MLCVB623DD4SXF77A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTHEZDQMBTGYZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4139280362>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHP523KEMZGVMWZUCORPSWL4SXF77AVCNFSM6AAAAACXBAMXV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZZGI4DAMZWGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Fernando Bertuccelli Cel: +54-911-4406-4060 LU9EOB

[fbertu]

Ahora cambie todo a 224.0.0.1, pero sigue sin funcionar.... El jue, 26 mar 2026 a las 22:17, Fernando Bertuccelli ***@***.***>) escribió:

…

[image: image.png] El jue, 26 mar 2026 a las 21:51, Alan Hargreaves (< ***@***.***>) escribió: > *alanhargreaves* left a comment (accius/openhamclock#846) > <#846 (comment)> > > The screen you are seeing is the screen that you get when we are waiting > to receive our first decode. > > I have a similar configuration (not on a pi) > > ***@***.*** openhamclock % grep '^WS' .env > WSJTX_ENABLED=true > WSJTX_UDP_PORT=2237 > WSJTX_MULTICAST_ADDRESS=224.0.0.1 > > and I get that screen when I'm not running wsjt-x or when it has not had > any decodes for a while. > > When you start openhamclock, do you see anything in the console log like: > > [WSJT-X] UDP listener on 0.0.0.0:2237 > [WSJT-X] Joined multicast group 224.0.0.1 > > with the address you are using displayed? > > It should show up just before the logo. > > — > Reply to this email directly, view it on GitHub > <#846?email_source=notifications&email_token=AHP523OTC7QE6MLCVB623DD4SXF77A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTHEZDQMBTGYZKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4139280362>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHP523KEMZGVMWZUCORPSWL4SXF77AVCNFSM6AAAAACXBAMXV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZZGI4DAMZWGI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Fernando Bertuccelli Cel: +54-911-4406-4060 LU9EOB

-- Fernando Bertuccelli Cel: +54-911-4406-4060 LU9EOB

[alanhargreaves]

Changing to 224.0.0.1 was something I was holding off asking you to try

The image in your earlier update did not upload. Did you see the server saying that it had joined the multicast group?

[alanhargreaves]

If you are going attach an image, it will likely work better if you do it at #846

[fbertu]

Continuo en español;
Lo que me extraña es que en la pagina web, en el panel de PSK Reporter - WSJTX-X sigue figurando la ip 127.0.0.1, y no la 224.0.0.1.

en la configuracion via web, figura 224.0.0.1

en el archivo .env tambien esta 224.0.0.1

y cuando reinicio el servicio, tambien aparece 224.0.0.1

Por lo tanto, sospecho que ese valor seteado en algun lado no lo estaria tomando y por ende quiere seguir escuchando en el 127.0.0.1.....

Si quieres que haga alguna prueba, quedo a disposicion.

Saludos!

[alanhargreaves]

You said:

I'll continue in Spanish;

For the record I am not a Spanish speaker, so I am relying on google translate

What I find strange is that on the website, in the PSK Reporter - WSJTX-X panel, the IP address 127.0.0.1 is still listed, and not 224.0.0.1.

Don't worry about that. When you are using the server multicast listened it's irrelevant. That text is actually hard coded. As I said previously, if you are running locally, the multicast setting for WSJT-X in the client don't have any effect. They are ONLY for if you are not running a server and have to download and run a seperate listener.

In the image I see that your server is listening to the multicast group.

I'm assuming that you are running on port 3000, so could I get you to have a look at localhost:3000/api/wsjtx either with a browser or something like the curl command and tell me if you get output?