My title is wrong, should have been “no viable macs to use after switching to https”

Running Version 1.6.0-beta.5136 on ubuntu 26.04.1 LTS (apache 2.4.66-2 and php8.5-fpm).

I had everything working fine in http. I then reran the server installer to switch to https. As soon as I did that, when I would try to register (either quick or full) a new host from the pxe menu, I’d get the error “no viable macs to use”. This happened on 2 different architectures, each system only having a single ethernet port on the motherboard.

PXE boot was still happening over http, but I had (successfully) switched the server over to https. I nuked the .fogsettings file, re-ran the install script, selected http only and now everything works again.

I’m running FOG 1.6.0-beta.5115 on Ubuntu 26.04.1 with apache2.4.66-2 and php8.5.4-0 (mod_php, not php-fpm).

I’m just getting this setup in my environment, and I’ve successfully imaged and deployed a few thin clients (Dell Optiplex 3000 and Wyze 5070) with Windows 10 IoT images. I have a powershell script that runs after imaging that completed the setup in my environment. Specifically, this script changes the hostname and joins my AD. All of this works fine.

The problem I have is that the hostname in FOG doesn’t update when I update the hostname on windows. The Windows hostname baked into the Wyze 5070 image is ‘wyze1-5070’. That hostname gets registered with Fog after the initial imaging, because the image has fogclient on it. I then run the powershell script which changes the name and reboots, but fog still refers to it as wyze1-5070.

Is there any automatic way to have the fog hostname updated to match the windows hostname? I have the ‘Hostname Changer’ service setting enabled by default, but I think that’s for fog pushing hostname changes to the client, not the other way around.

Thank you