@Tom-Elliott
so I cannot use fog in the development branch - I need the snap in - the old one are not working anymore - I cannot upload new one.

@Tom-Elliott

I pulled latest dev-branch version 1.5.10.1856, re-run installer and snapins are working again.

Thank you very much for help.

Hello @Tom-Elliott

Sorry for the delay 😞

I checked what you told me to do. It appears I have a file that I didn’t check : /etc/php/8.4/fpm/pool.d/www.conf
I set display_error=off and now I don’t have all those warnings.

Thank you for your help.

This is perfect 🙂

@GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.

I will post back when I have an update.

Thanks!

@KMEH
Hi,
I don’t understand well evereything too, but thanks for your work and research on this.
On the last IPXE release 2.0 (https://github.com/ipxe/ipxe/releases), i see

Add support for UEFI Secure Boot via a dedicated iPXE shim.

Does this mean that if FOG include this last ipxe release, Secure Boot support for FOG will be handled automatically?

@Tom-Elliott just bumping this. Is there anything I can do to help? I have some experience building Linux kernels from a few years ago.

@Tom-Elliott
This is resolved in latest dev-branch version: 1.5.10.1853
Thanks.

@Infojoe I believe I pushed a fix for this already, but I’ll have to check again tomorrow morning.

@Infojoe right now this is understood (they typo I’ll get fixed in the morning, but the auth check is preventing inventory from sending, so fixing will be more likely deleting the auth check entirely again. This is where which side of the coin is needed. I’ll probably remove the line so things just work as they once did. Thanks for letting me know.

seems to work when copying the directory from another host over to /opt/fog-service and creating a runit file /etc/sv/fog-service/run with content

#!/bin/sh exec 2>&1 echo "Starting FOG Client..." exec mono-service /opt/fog-client/FOGService.exe -d /opt/fog-service -l /opt/fog-service/service.lock

@vanfifty1
I have some simelar Problems maby read the post
https://forums.fogproject.org/topic/18157/windows-11-65x-hp-z2-tower-g1i-update/2
My problem is/was that Fog uses sometimes the wrong nvme …

update the kernals on fog server / nodes

Hi,
I know this is a bit old, but I found it when I was searching for an answer to the following question:

I have prepared USB bootable image based in WinPE. I use it to boot from USB. I have this image in iso file and I use it to place it on USB with rufus software.

I wonder if I can use this tutorial of yours in exactly same way only to use my custom iso image instead of your mentioned WinPE.

I know this may be trivial question and I may just try it, but I am really only beginner in WinPE and fog project.

Thank you for your kind answer.
-r-

So I am alone ?

We can mark this closed. Turns out it was a old/bad snapin package on the old server. I set up Fog with a new DB and everything worked fine. Once I removed the snapins and exported and imported the DB again it all worked as expected.

Thanks for the help.

@Mr_K
Thanks for the help Tom. You got me pointed in the right direction. Everything is working now.

I did a complete Ubnutu and fog fresh install to make sure I wasn’t missing anything and noticed during the installation it was grabbing my WAN IP as the fog server IP and then somehow changing the fog server IP to my LAN IP. So when I clicked on the link from the terminal after it had finished it was 192.168.1.148 however everything was setup “certs, storage Ipxe” ect as my WAN IP 20.21.X.X.

All I had to do was just change the fog settings so the IP’s matched re ran the installer to grab the new files and everything is running perfect now.