Sorry to resurrect an old thread. I ran into this issue today and have found a resolution (at least in my case).

I had an image that was quite old that I wanted to update. The client I wanted to image was from a completely different system (a VM). I cloned over top the existing image with the VM. I got the same exact 504 error and it would eventually fail to update the database.

I created a new image in fog and assigned the new host that new image. Went through flawlessly.

It’s weird because I’ve done this in the past on multiple occasions and never had an issue. It was more than likely I created the older image (that I was just trying to clone over) on v1.5.9. I did update to v1.5.10 a couple months ago.

So if you have this same problem, try creating a new image if overwriting an old image fails with the 504 error.

@Pinki This sounds like a layer 7 firewall is in between FOG server and the client/host. Sometimes alles the transfer of init.xz but more often blocks it.

The later error is due to the firewall not allowing connections on random network ports which are used by NFS.

Either way you need to talk to your network/security team and see if they can help.

@george1421 Hello !
Thanks you so mush ! It worked ! 🤗 🤗

Have a good day,
Pinki

@JackWallington Please answer George’s questions first. As well let me add this one. Do you have a D-Link DGS-3620 switch between your HP desktop and the FOG server? If not you still might check to see if some kind of DOS attack prevention is enabled on a switch connecting those two - more information see here.

hello,
I couldn’t find a solution to unlock my situation, I tried many things on promox and on fog, without succes again. So I decided to start a new install on another post, separated from the proxmox and it’s working fine. I think I’ll keep this solution so, thanks for your help and sorry to leave an unsolved issue, see you later !