Thank you both for your help! George and I were messaging back and forth and my DHCP policies and scopes were pretty messed up. Looking back I have no idea how it worked before. After completely changing them the machines are booting into FOG again just fine. Appreciate the quick responses!

@sebastian-roth Also, when we changed the subnet of the FOG server we didn’t create a new Server. I changed the IP values inside our original FOG server and reran the FOG Installer for the IP addresses to be changed throughout. After I ran the installer, I didn’t do anything with the certs inside the FOG server.

@sebastian-roth I tried installing the 0.11.20 version.

@sebastian-roth I might just change the settings.json to the correct IP address and keep the FOG Client at 0.11.19. We’ll see if that fixes it for us.

@sebastian-roth The error states “Unable to install CA Certificate” and just looked at the fog.log and it was there right at the top. The FOG client is still pointing to the old IP address for the FOG Server. If you still want the logs posted, I can.

@sebastian-roth You’re incredible. I really appreciate you taking the time to explain this to me. I’ve been using FOG quite often and even merged it to another subnet and got it up and running again through the help of the forum here and wiki. And yes, re-reading what I stated above I didn’t really have a direct question. My brain was fried and kind of all over the place after researching, apologies there. The reason I was wanting to update this cert was because I thought maybe it was the reason why we cannot upgrade to the newest FOG Client version. We are on 0.11.19 I think? But when trying to install the newer client I get a certificate error. (I can get the specific error once I get back to work tomorrow). Upon deployment, auto-join to the domain stopped working for us so I was hoping upgrading to the newest version might just fix it. From my understanding, once the machine is imaged, the FOG Client does post tasks like auto-joining to the domain?

I am very green to FOG and I have inherited this from the old system admin who is now gone. We have three certificates on the clients/workstations -

• FOG Project CA - expires 2029
• FOG Project - expired last year
• FOG Server CA - expires 2029

I’ve been reading the Wiki for HTTPS (https://wiki.fogproject.org/HTTPS) and I see there are three certificates on the server -

• ca.cert.pem
• srvpublic.crt
• .srvprivate.key

When I go to each of the locations where the above certs are stored I see the original files that were generated by the FOG installer. Should I be seeing the FOG Project CA, FOG Project, and FOG Server CA instead? I see now that if you rerun the installer it will overwrite your custom certificate files. I’m guessing after upgrading from 1.5.8 to 1.5.9 these were overwritten? I guess my question is, what should I do from here? Do I need to recreate the CA’s with ./installfog.sh --recreate-ca or what else should I do?

Thanks!

Thank you both for your help! George and I were messaging back and forth and my DHCP policies and scopes were pretty messed up. Looking back I have no idea how it worked before. After completely changing them the machines are booting into FOG again just fine. Appreciate the quick responses!

@george1421 Whoops, my bad. I got the capture filter set this time instead of doing a display filter. Also, when I sent the picture earlier I was replying back to Sebastian Roth’s comment. What’s the best way to send you the pcap file? I’m unable to upload it here.

@george1421 I did a filter for both 67 and 68 and I didn’t get anything back (tcp.port eq 67) and I also did a search for the PxE booting machine’s ip address (ip.addr eq 10.0.2.217 and also did source ip.src eq 10.0.2.217 to see if I saw anything from this machine) and nothing matched my results in Wireshark. The ip address of the third machine I was using is 10.0.2.90 so they’re on the same subnet.

@sebastian-roth The error message is the same as before that I posted earlier.
https://i.imgur.com/LrkYp1d.png