@Mr_K This seems to be a routing issue:

Your fog server lives at 192.168.0.3

Your machine is getting an IP of 192.168.1.148

Your router providing 192.168.1.X is likely unable to route 192.168.1.X -> 192.168.0.X

@neodawg Can you provide the systems php error log, for Alma I think its RPM based so you would -> go to the page and see this -> get the last 100 lines or so (sudo tail -n 100 /var/log/php-fpm/www-error.log) This should tell us where it’s failing.

If you’re also able, can you tell us what version of FOG you’re running?

(Login to fog, bottom right hand corner should tell you the version you’re running.)

Fresh install using ver1.5.10.1826

Works perfectly. Can register hosts as normal

Maybe a bug with 1.6.0… hopefully if anyone else experiences this issue this might help

@Tom-Elliott Thanks for the clarification! I’ll try upgrading to the latest stable version, I was planning on doing this anyway.

I’ll look into the Persistent Groups plugin and see how it works!

@gabriel-pissoto

I often record this with a phone then you can pick out the error in that micro flash of text.
I think most of the time picking a different X.pxe file resolves this for me.

Please check memory of computer with memtest86+ 8.0

https://www.memtest.org/

@heix75 No.

Not because it’s not a QOL improvement (it is) but because what you see in 1.5.x.x is NOT what is the end goal.

If you want to see what the UX is moving toward install the version of FOG on working-1.6.

You’ll understand (I hope), then, why I’m saying this.

I have the same HP Z2 G1i – it works for me with
sanboot.PNG
“SANBOOT”
The BIOS also seems very finicky to me—I even disabled all NVMe devices and Windows and enabled only network boot—but Windows resets the setting. Setting a BIOS password didn’t change anything.

@Infojoe I forgot an important information : version 1.5.10.1826

@lucamathuse No, I would not move the files manually yet.

If the capture reports “Cloned successfully” but the task remains In-Progress, then the capture itself may have finished, but the post-capture process is not completing correctly. Under normal conditions, the host should finish the task and then reboot or shut down automatically based on your settings.

So, before moving anything by hand, I would want to know whether the host is actually stuck there indefinitely or whether it is still finishing something in the background. If it never updates the task status, that could also explain why your image set ends up incomplete or inconsistent.

@lucamathuse
I don’t remember if it’s related to Win11 we have this in our postdownload script :

if [ -n "$hd" ]; then if [ "$hd" = "/dev/nvme0n1" ] ; then partsys=$hd'p2' partdata=$hd'p3' else partsys=$hd'2' partdata=$hd'3' fi

We use Virtualbox, install classic WIndows 11, disable Bitlocker, and capture with FOG with image set to “Multiple Partition Image - All Disks”
My folder capture :

d1.mbr d1p1.img d1p2.img d1p3.img d1p4.img d1.partitions d1.size

Maybe try capture debug to see which partition FOG get during your capture

@lucasgfaj have you turned off secure boot?

@mashina Ah, thank you for that and sorry for my denseness. Indeed this is a bug and I’ve replicated and figured out where this is occurring.

I have pushed a few mroe adjustments in an attempt find and fix more bugs (thanks AI review and whatnot)

Please pull and let me know if there’s any other issues.