Hello,
In my attempt to switch to HTTPS for the Fog server, I encountered the same issue of the keyboard being disabled in the iPXE menu. After several unsuccessful tests, I consulted Copilot. After reviewing all the scripts and .h files, it indicated that the issue stemmed from the size of the iPXE.efi file I was using. It was too large due to all the necessary modules for HTTPS, causing iPXE to deactivate the USB keyboard functionality during loading. Consequently, I opted for snponly.efi instead, and now the keyboard works perfectly.

I modified the script buildipxe.sh :

sed -i ‘s+#define USB_HCD_USBIO+//#define USB_HCD_USBIO+g’ config/usb.h
sed -i ‘s+#define USB_KEYBOARD+//#define USB_KEYBOARD+g’ config/usb.h
sed -i ‘s+//#define USB_EFI+#define USB_EFI+g’ config/usb.h

May I propose a change in the console.h : Could you set the keyboard map to “dynamic” instead of “us” ? That way we can easily set our language in default.ipxe

//#define KEYBOARD_MAP us // Default US keyboard map
#define KEYBOARD_MAP dynamic // Runtime selectable keyboard map

@Greg-Plamondon I’m going to try delving into this but I’ve been very busy with other things and just haven’t gotten around.

I do appreciate the patience and assistance.

The changes you were doing that fixed the problem, please implement them again and you should be back to functional

Once that is done, do you mind doing a diff between that file and the relevant file in the git repository side:

Files I think you changed were under: <path>/<to>/<installer>/packages/service/<servicename>/<servicefile>

I’m not seeing any issues on my test systems.

not really sure why it isn’t working either.

I believe you were editing the files in /opt/fog/service/<servicename>/<servicefile>

So you would do:

diff -u <path>/<to>/<installer>/packages/service/<servicename>/<servicefile> /opt/fog/service/<servicename>/<servicefile>

more informations:

if I install a linux on the computer, then deploy the debian image on it: it’s OK
And the I can deploy the Ubuntu image with no problems

The issue only happend after i’ve deployed a Windows 11 image and then the debian image.

In order to make the WIndows image works, i had to do
cp refind.efi refind_x64.efi
(or I have a freeze with rEFInf -Initializing…"

Xavier

@Tom-Elliott apologies for the delay but here is what I see in the error log when this occurs:

For context the 'Client IP Detected as <IP ADDRESS> is a small modification to the Subnet Groups plugin which I log the IP of the client checking in, this is working as intended.

The ‘PHP Fatal error’ is what I only see when we have the chain loading error.

I can confirm this is working on: 1.5.10.1734 as I have rolled back any sites to this version and have seen no issues.

[Mon Feb 23 15:07:55.208763 2026] [proxy_fcgi:error] [pid 501804] [client 10.9.209.159:33595] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:08:27.815241 2026] [proxy_fcgi:error] [pid 501806] [client 10.9.209.159:1025] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:09:00.456158 2026] [proxy_fcgi:error] [pid 501802] [client 10.9.209.159:1555] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:09:33.088040 2026] [proxy_fcgi:error] [pid 501802] [client 10.9.209.159:6935] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:10:05.672334 2026] [proxy_fcgi:error] [pid 501803] [client 10.9.209.159:16900] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:10:38.336356 2026] [proxy_fcgi:error] [pid 571479] [client 10.9.209.159:43335] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496' [Mon Feb 23 15:11:10.976801 2026] [proxy_fcgi:error] [pid 501803] [client 10.9.209.159:36391] AH01071: Got error 'PHP message: SubnetGroup Hook: Client IP Detected as 10.9.209.159; PHP message: PHP Fatal error: Uncaught ValueError: min(): Argument #1 ($value) must contain at least one element in /var/www/fog/lib/fog/image.class.php:496\nStack trace:\n#0 /var/www/fog/lib/fog/image.class.php(496): min()\n#1 /var/www/fog/lib/fog/image.class.php(389): Image->getPrimaryGroup()\n#2 /var/www/fog/lib/fog/bootmenu.class.php(1472): Image->getStorageGroup()\n#3 /var/www/fog/lib/fog/bootmenu.class.php(469): BootMenu->getTasking()\n#4 /var/www/fog/service/ipxe/boot.php(52): BootMenu->__construct()\n#5 {main}\n thrown in /var/www/fog/lib/fog/image.class.php on line 496'```

@rodluz 0f341e2a-1996-4ec7-91ac-4269fe20a31c-image.png

I’ve updated the iPXE on my proxmox server, still hangs on this message. Other VMs work fine, as they did with the older iPXE version.

I have just discovered that somehow all the MACs are changing sometime after the final successful DHCP lease.
My DHCP server is set to only answer to specific MACs, so if I add in the “new” one, it works.
No idea how this is happening, I’ve never seen MACs just suddenly change like this.
It sucks that now I have another MAC per server to deal with, but at least it’s working.

I’m also interested in knowing if a solution exists.

@Greg-Plamondon
Hi,

we got a dhcp server. The computer got network, the path to the efi file is connected.
I have no access to the dhcp settings that i could set the next-server or anything else.
But i think the efi file maybe is corrupt? i have tried to edit the efi file, but then the boot stick does not work anymore.

@deharter i could capture changing the image type , from “Single Disk - Resizeable” to “Multiple Partition Image - Single Disk (Not Resizeable)”

@Tom-Elliott

So f144ad5 is the last working commit. In case anyone else have the same problem, this is my script to grab it and modify so it works fine with EFI keyboard in some PCs as discussed here: https://forums.fogproject.org/topic/17870/fog-ipxe-menu-no-input. It also removes neverssl.com site because it’s down now so script hangs on checking internet connection. Don’t mind main sed part, it’s probably overcomplicated since I used ChatGPT for it, but it works fine so who cares 😉

#!/bin/bash # Checkout last working FOG project commit cd git git clone https://github.com/FOGProject/fogproject.git cd fogproject git checkout f144ad5a30bdab23be4d207b471ca80057e367fd # Modify functions.sh to remove non working neverssl.com site cd ~/git/fogproject/lib/common sed -i 's+http_sites=("neverssl.com" "httpbin.org")+http_sites=("httpbin.org")+g' functions.sh # Modify buildipxe.sh to grab last working ipxe commit and fix EFI USB drivers cd ~/git/fogproject/utils/FOGiPXE cat > transform_buildipxe.sed <<'SED' /^[[:space:]]*git pull$/a\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a /^ cd \${BASE}\/ipxe\/src\/$/c\ cd \${BASE}/ipxe/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe/src/ /^ cd \${BASE}\/ipxe-efi\/src\/$/c\ cd \${BASE}/ipxe-efi/\ git checkout 6cccb3bdc00359068c07125258d71ce24db5118a\ cd \${BASE}/ipxe-efi/src/ /^sed -i 's+#define[[:space:]]*USB_HCD_USBIO+\/\/\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/c\ sed -i 's+#define<----->USB_HCD_USBIO+//#define>USB_HCD_USBIO+g' config/usb.h /^sed -i 's+\/\/\#define[[:space:]]*USB_HCD_USBIO+\#define[[:space:]]*USB_HCD_USBIO+g' config\/usb\.h$/, /^sed -i 's+\/\/\#undef[[:space:]]*USB_EFI+\#undef[[:space:]]*USB_EFI+g' config\/usb\.h$ #sed -i 's+//#define\tUSB_HCD_USBIO+#define\tUSB_HCD_USBIO+g' config/usb.h\ #sed -i 's+//#undef\tUSB_KEYBOARD+#define\tUSB_KEYBOARD+g' config/usb.h\ #sed -i 's+//#undef\tUSB_EFI+#undef\tUSB_EFI+g' config/usb.h\ sed -i 's+//#define+#define+g' config/usb.h\ sed -i 's+#define USB_CMD+//#define USB_CMD+g' config/general.h SED sed -i -f transform_buildipxe.sed buildipxe.sh rm -f transform_buildipxe.sed # Start FOG install/update cd ~/git/fogproject/bin ./installfog.sh

Hello,

It’s working again.
I have update to the last version (1.6.0-beta.2273) but I’m not sure it’s fixed with this.
I have also clean DB using this : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

Thank you.

@george1421 said in PXE issues:

@Jamaal This problem is solvable but it make take some effort on your part.

Lets start with the basics.

For the DHCP IP zone where your pxe booting clients live, you need to set dhcp options 66 to the IP address of your fog server. And for dhcp options 67 that needs to be snponly.efi or snp.efi. With those settings configured on a MS Windows based dhcp server a pxe booting client should boot. Make sure on your dhcp server that is responding to bootp and dhcp requests. Its been a while since I messed with windows but on the dhcp server there should be a setting of dhcp bootp or both. Select both.

Now lets talk about WDS for a second. A WDS server can use dhcp options 66 and 67 as above, but it can also run a proxy dhcp service that tells the client to ignore the dhcp options and come talk to it for boot information after it gets an IP address for the dhcp server. This maybe called a netboot service or something like that on your WDS server. Its not part of the main WDS service. If this service is still enabled it will override any settings you make in dhcp for pxe booting.

So how do you figure this out to what’s wrong?

The easiest and most complicated issue is to identify what is flying down your network during the pxe booting process. You can do this with wireshark on a witness computer (computer not part of the pxe booting process). This witness computer can either be a ms windows or linux computer, the key is to have wireshark loaded. When you start up a capture use a capture filter of port 67 or port 68 or port 4011 That will limit what wireshark sees to only the dhcp packets. Make sure the witness computer is connected to the same subnet as the pxe booting computer.

Start the packet capture and then attempt to pxe boot the target computer. Continue to capture the packet until the pxe booting computer either reaches the fog iPXE menu or errors out. Then stop the capture.

In the top section you should see the DORA (discover, offer, request, and finally ack/nack) process. The process goes as follows:
Client -> Discovery
Server-> Offer
Client -> Request
Server -> Ack/Nack

In this process you are most interested in the one or more OFFER packets. In a normal network you should only see one OFFER packet. When WDS is involved you will see one OFFER packet from your main dhcp server and a second OFFER packet from your WDS server. If you are seeing the OFFER from your WDS server then you don’t have the proxy-dhcp service disabled, and that is causing your issue. If you are seeing two offer packets from two different dhcp servers, such as a primary / secondary setup make sure both dhcp server are configured to boot from FOG server.

Now what do you do if you only have one OFFER packet and its still not working. This is where you need to select the OFFER packet and then look at the data in the parameters box. There will be the bootp fields of next-server and boot-file these need to be configured for the fog server IP and snp.efi. Then in the dhcp options section options 66 and 67 need to be set correctly. If one or the other sections are not set correctly you will get random machines not booting while others are.

If you can’t figure it out save the packet capture file “be sure you only captured the dhcp process” and up load the file to a file share site and post the link here and one of us will take a look to see what’s wrong. But I think from what I covered here you should be able to figure out what the pxe booting client is being told to do incorrectly.

George,

I ran the idea with the system administrator at my job and of course he was doubtful (conceited), he turned off the server thinking that would solve the issue. I ended up looking at an older forum and made a USB with the ipce file and booted up the machines that were given me issues and that worked. You guys can close this and mark as resolved. Again, I appreciate your guidance on this.

Adding the menu manually with the above settings resolved the issue for me.