Menu not updating ?

[NEXUSBE]

Hello,

I’ve had netboot.xyz for quite some time, but I’m having an issue with the menu not updating

I have the latest version of the menu, but when I boot through PXE, I still get a message saying that I’m using an older version

I suspect that I might not have the correct permissions to write the files. However, I can edit the files through the web interface and download no problemo, and there are no errors showing up in the logs

Am I missing something ?

[tk1475]

The v2.0.88 in that header isn't the menu version. It's the version of the bootloader (the .efi / .kpxe iPXE binary) the machine booted. The bootloader sets version (roles/netbootxyz/templates/disks/netboot.xyz.j2: set version {{ boot_version }}), and menu.ipxe only prints ${version} and compares it with its own version. So your menus are 3.0.3, but the client still gets a 2.x bootloader over TFTP, and that's where the "older version" message comes from.

"Upgrade Menus" in the webapp does download the new bootloaders. They go to /config/menus/remote/ and are then copied into /config/menus/, which is the TFTP root (upgrademenu() / layermenu() in the webapp's app.js). Some things to check:

1. Old binaries in local/: anything in /config/menus/local/ is copied over the remote files after an upgrade. An old netboot.xyz.efi there will win every time.

   docker exec netbootxyz ls -l /config/menus/ /config/menus/local/ /config/menus/remote/

   The .efi/.kpxe files in /config/menus/ should have today's date.
2. Ownership: dnsmasq runs with --tftp-secure --user=nbxyz, and in that mode it only serves files owned by the user it runs as. If the copy failed because of permissions, you're left with the old files. Make sure the /config volume is writable by the container's PUID/PGID.
3. Is the client actually booting from this container? Look for the transfer in docker logs netbootxyz (dnsmasq logs every TFTP "sent ..." line). If you don't see it when the machine boots, the DHCP option 66/67 (next-server 192.168.1.240 / filename) points to another TFTP server or an old copy of the file.

Once the client really gets the 3.0.3 netboot.xyz.efi, the header shows v3.0.3 and the message goes away.