FOG 1.5.10 HTTPS WOL restart indefinitely in menu

[Cyrock]

Hello
I use FOG for many years and all was good.
i installed debian 11 with FOG 1.5.10 and HTTPS (i think that’s the problem).
All seems good.
But when i WOL my PC, boot pxe works and when the menu appear, they restart indefinitely.
boot hard disk 3, 2, 1… and 3, 2, 1…
I must use CTRL+ALT+SUPPR to reboot.
If i use a normal boot, everything is good.

Have you an idea ?

[Cyrock]

@Sebastian-Roth

Yes with EFI exit type = REFIND_EFI
it works perfectly
Thxs

[Cyrock]

This post is deleted!

[Cyrock]

@Cyrock
I have migrate from fog 1.5.9 client 0.11.19 without https.
export images, hosts, group.
have you an idea ?
thxs

[Sebastian Roth]

@Cyrock Possibly you have more than one topic mixed up in this post. The picture shows the fog-client log from a machine while WOL and PXE booting is not directly connected to the fog-client at all. Let’s try to get this sorted:

But when i WOL my PC, boot pxe works and when the menu appear, they restart indefinitely.
boot hard disk 3, 2, 1… and 3, 2, 1…
I must use CTRL+ALT+SUPPR to reboot.

Do you see this behavior with different hardware or is it just happening/you only have one model of machines? I think I have heard of PCs behaving differently when being started via the WOL magic packet compared to switching it on manually. This is not something caused by FOG I reckon. Please download a WOL tool of you choice (e.g. WakeOnLan Tool 2, WakeMeOnLan, PingTool, …) and see if this causes the same loop. Pretty sure you see the same thing. In this case you can try updating the BIOS/UEFI firmware or talk to your mainboard manufacturer and it’s firmware suppliers.

fog-client log: Middleware::Response Invalid security token

This is caused by an old security token in the database most of the time. In the FOG web UI go the the host object you grabbed the log from and you should see the “Reset Encryption” button there just above the hostname and MAC address(es): https://i.imgur.com/2Egs7O2.png

[Cyrock]

@Sebastian-Roth
I found a solution that I don’t really like.
Before I had a FOG 1.5.9 server with client in 0.11.19 WITHOUT https
I exported hosts.xml then reintegrated it into my new FOG server in 1.5.10 on debian 11 with the activation of https which was not enabled before.
BIOS update does not change.
Reset encryption for the host does not work.
When I say it doesn’t work, I mean the WOL which is no longer functional.
By taking the PC out of the base and re-entering it, WOL works again.
250 computers to redo, wouldn’t there be another possibility?
THANKS

[Cyrock]

I express myself badly, sorry
the WOL works, the computer starts but hangs on the FOG menu which allows to boot on the hard disk.
When I launch a WOL, the FOG menu loops continuously and computer does not start.
I think it’s clearer and more precise.

[Sebastian Roth]

@Cyrock There is no need to remove and re-add all hosts. I am sure it’s just a particular setting causing the problem. Most probably it’s the Host BIOS Exit Type or Host EFI Exit Type (depending on the machine being UEFI or a legacy BIOS type.

Just play with those settings and I am sure you can make it work.

[Cyrock]

@Sebastian-Roth

Yes with EFI exit type = REFIND_EFI
it works perfectly
Thxs