Client can't discover local server after update to 2.5.34

Hi there,
I updated my UrBackup Server on Ubuntu 24.04.3 LTS (GNU/Linux 6.8.0-88-generic x86_64) from version 2.5.33 to 2.5.34 (noble amd64). I also updated my Client on Windows from 2.5.25 to 2.5.26 via the internal update tool. Since then the Client doesn’t connect to the Server anymore. Neither the new 2.5.26 than the old client 2.5.25 on my other Windows PC. I didn’t change any config files manually.

I installed Wireshark on my Client-PC (Client with 2.5.26) and I can see the Broadcast Messages from the Server:

7080	99.868850	192.168.178.XX	255.255.255.255	UDP	60	35623 → 35622 Len=1

but there is no reply from the Client.
This is the client (debug) log:

2025-12-22 17:22:39: Loaded -fileserv- plugin
2025-12-22 17:22:39: Loaded -fsimageplugin- plugin
2025-12-22 17:22:39: Loaded -cryptoplugin- plugin
2025-12-22 17:22:39: SQLite: recovered 24 frames from WAL file C:\Program Files\UrBackup\urbackup\backup_client.db-wal code: 283
2025-12-22 17:22:39: FileSrv: Backup privileges set successfully
2025-12-22 17:22:39: FileSrv: Backup privileges set successfully (SE_SECURITY_NAME
)2025-12-22 17:22:39: FileSrv: Backup privileges set successfully (SE_RESTORE_NAME)
2025-12-22 17:22:39: urbackupserver: Server started up successfully!
2025-12-22 17:22:39: FileSrv: Binding UDP socket at port 35622…
2025-12-22 17:22:39: FileSrv: done.
2025-12-22 17:22:39: FileSrv: Disabling new behavior…
2025-12-22 17:22:39: Started UrBackupClient Backend…
2025-12-22 17:22:39: Filesystem. Vol=“\?\Volume{xxxxx}" Name=”" Type=“ntfs” VPaths=1 Size=1023264419840
2025-12-22 17:22:39: Filesystem is System partition. Skipping…
2025-12-22 17:22:39: FileSrv: Binding ipv6 UDP socket at port 35622…
2025-12-22 17:22:39: FileSrv: done.
2025-12-22 17:22:39: Filesystem. Vol=“\?\Volume{xxxx}" Name=”" Type=“ntfs” VPaths=0 Size=821030912
2025-12-22 17:22:39: FileSrv: Disabling new behavior…
2025-12-22 17:22:39: FileSrv: Servername: -Alex-Yoga-
2025-12-22 17:22:39: GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
2025-12-22 17:22:39: Do not automount is set2025-12-22 17:22:39: System partition is set
2025-12-22 17:22:39: Bootable flag set for volume
2025-12-22 17:22:39: FileSrv: Server started up successfully
2025-12-22 17:22:39: FileSrv: UDP Thread started
2025-12-22 17:22:39: Found potential candidate: \?\Volume{xxx}\ Score: 3
2025-12-22 17:22:39: Filesystem. Vol=“\?\Volume{xxx}" Name=”" Type=“fat32” VPaths=0 Size=100663296
2025-12-22 17:22:39: GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775808
2025-12-22 17:22:39: Do not automount is set2025-12-22 17:22:39: Bootable flag not set for volume
2025-12-22 17:22:39: Found potential candidate: \?\Volume{xxx}\ Score: 3
2025-12-22 17:22:39: Selected volume \?\Volume{xxx}2025-12-22 17:22:39: System dir: C:\WINDOWS
2025-12-22 17:22:39: Volpath: \.\C:2025-12-22 17:22:39: EFI partition with type UUID {xxx}
2025-12-22 17:22:39: EFI System Partition is at \?\GLOBALROOT\Device\Harddisk0\Partition1
2025-12-22 17:22:39: urbackupserver: No available slots… starting new Worker
2025-12-22 17:22:39: ClientService cmd: STATUS DETAIL#pw=xxx
2025-12-22 17:22:39: ClientService cmd: STATUS#pw=xxx
2025-12-22 17:22:39: ClientService cmd: STATUS DETAIL#pw=xxx
2025-12-22 17:22:39: ClientService cmd: STATUS#pw=xxx
2025-12-22 17:22:40: ClientService cmd: STATUS DETAIL#pw=xxx
2025-12-22 17:22:40: Looking for old Sessions… 0 sessions
2025-12-22 17:22:40: Internet mode not enabled
2025-12-22 17:22:41: ClientService cmd: STATUS DETAIL#pw=xxx

after that the last line is repeated every second but no message about a discovery of the Server…
I also tried to reinstall the client from the UrBackup webinterface but no changes.

Thank you for any help
Greetings Alex

I think I was able to identify and solve the issue.

The problem was caused by the Windows Firewall settings blocking the communication between the UrBackup server and client. After changing the local network (where both server and client are located) from “Public” to “Private” in the Windows network/firewall settings on the client, the client was able to connect to the server again and the backup started successfully.

What surprises me, however, is that before updating UrBackup (both server and client), the network on the client was also set to “Public” and everything worked fine.
Is it possible that the client installation or update changed or tightened the firewall rules in some way?