[Bug] Transfer Error Hypervisor Migration XCP-NG -> PVE over local LAN

[tuxpowered]

Describe the bug

After correctly starting a Hypervisor Migration (Thank you, @MrMasterbay), the migration starts and runs for a little while then exits with the following:

[21:21:48] Phase: planning
[21:21:48] Source VM: WinSVR (106)
[21:21:48] Found 1 disk(s), total 60.0 GB
[21:21:48] Target VMID: 107
[21:21:48] Phase: transfer
[21:21:48] Transferring WinSVR 0 (60.0 GB)
[21:21:50] Allocated local-zfs:vm-107-disk-0
[21:24:54] FAILED: Transfer error: ("Connection broken: BrokenPipeError(32, 'Broken pipe')", BrokenPipeError(32, 'Broken pipe'))
[21:24:54] Phase: failed

I tried a few times, even restarted the systems and tried again with the same errors.
On the target PVE i do see a disk being created..

The failure almost always happens at the 2nd check box sometimes a little past it. It never makes it much past step 2.

Looking at the pool I can see about 11Gb was transferer

zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 85.8G 631G 104K /rpool
...
rpool/data/vm-107-disk-0 11.6G 631G 11.6G -
rpool/var-lib-vz 1.75G 631G 1.75G /var/lib/vz

(Not sure what other logs to grab)

Steps to Reproduce

1. Start hypervisor Migration
2. Analyze VM
3. Select target resources
4. Start Migration

Expected behavior

For the file(s) to be copied.

Logs

Environment

• PegaProx Version: 0.9.13
• Installation Method: ct image
• OS: Proxmox
• Browser: Safari
• Behind Reverse Proxy? No
• UI? Corporate

Checklist

[x ] I have searched existing issues to make sure this is not a duplicate
[ x] I am using the latest version of PegaProx

[MrMasterbay]

We did quite a lot of hardening in that area can't say for certain if I did that or if there happend just something.
Could you also throw me an support bundle in here? So I can scout it trough?

[MrMasterbay]

for the docs #545 lol :)

[tuxpowered]

Yeah, the original ticket-bot closed it and I couldn't

pegaprox_support_20260612_215906 2.zip

reopen it so i made a duplicate. (sorry)