Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  B

  Thank you. I updated working-1.6 today and re-ran installfog.sh.

  The server is now running:

  FOG 1.6.0-beta.5362 iPXE v2.0.0-fog.8

  I can also confirm that the agent enrollment fix works. Before the update /fog/agent/v1/enroll was returning HTTP 308. After the update it returns HTTP 202 and the agent appears under “Pending agents” in the FOG web interface.

  However, I can still reproduce the UEFI boot problem, and I was able to narrow it down further.

  The newly generated /tftpboot/default.ipxe from beta.5362 is 979 bytes. With this file the UEFI client successfully downloads default.ipxe but then stops immediately after:

  default.ipxe... ok

  I tested this with both:

  ipxe.efi secureboot/snponly-shimx64.efi

  The result is the same with both.

  I then replaced only default.ipxe with my older copy from 2026-07-24 (479 bytes), without changing the current FOG installation or iPXE binaries.

  With the old default.ipxe:

  secureboot/snponly-shimx64.efi boots correctly ipxe.efi also boots correctly the FOG menu appears normally after the timeout the machine continues into Windows normally Legacy BIOS clients also continue to work normally

  So the problem appears to be reproducibly related to the contents of the newly generated default.ipxe, rather than the EFI boot binary itself.

  For reference:

  Working default.ipxe from 2026-07-24:

  Size: 479 bytes SHA256: 8e19bb03144b530567f08d2c0c173ab5b7c2df3e013e484b6ef19cf4f805e503

  New beta.5362 generated default.ipxe:

  Size: 979 bytes SHA256: 11e0b7aa8c3cee380756bd6903fa149a9b7a3e3a58386aa2e8a62908106fa1a1

  The diff shows several additional parameters in the new file, including serial/asset/Secure Boot parameters, additional NIC parameters, and this line:

  isset ${netX/mac} && param macboot ${netX/mac} ||

  For now I have left the old 479-byte default.ipxe in place because it restores normal booting.

  If useful, I can provide both complete default.ipxe files or test a patched version if you would like me to test a specific change.

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184 Topics

  825 Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  T

  @ahaeder No:

  The idea of fog client is to rename the host based on what you name the computer within FOG, not the other way around.

  If you want it to be a specific name, and you have the FOG Client installed, set the wanted name in the FOG UI, and the host will change automatically.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  T

  @Valer I think we need to understand what this plugin is doing.

  CSS isn’t something we’ve allowed to be injectable though it could be.

  You can still use your own CSS but that’s more at the FOG Configuration -> FOG Setting -> FOG_THEME, but you would need to put it on your server in a location you type the path too here.

  https://docs.fogproject.org/en/latest/development/plugin-development

  This is a good toolkit for understanding how to build your own plugin.