<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FOG Server : Certificate validation failed]]></title><description><![CDATA[<p dir="auto">Hello,<br />
Just moved my FOG-server to version 1.5.10.2482   on Debian 13.5</p>
<p dir="auto">used  “./installfog.sh -y -C”</p>
<p dir="auto">During installation/update  the process was uncapable to generate new certificates , giving this kind of error-message “Cannot read Secure Boot signing file: /opt/fog/pki/secureboot/leaf/sign.key”</p>
<p dir="auto">The Google’s IA showed me a way to generate manually those certificates</p>
<p dir="auto">But now, the computer-stations still cannot communicate well with the server</p>
<p dir="auto">Middleware::Communication Download: <a href="http://fogserver/fog/management/other/ssl/srvpublic.crt" target="_blank" rel="noopener noreferrer nofollow ugc">http://fogserver/fog/management/other/ssl/srvpublic.crt</a><br />
Data::RSA FOG Server CA cert found<br />
Data::RSA ERROR: Certificate validation failed<br />
Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Thumbprints did not match.<br />
Middleware::Authentication ERROR: Could not authenticate<br />
Middleware::Athentication ERROR: Certificate is not from FOG CA</p>
<p dir="auto">Also I noticed that folder /var/www/fog/management/other/ssl/ does not contain the file srvpublic.crt   although downloading of that file works. Is it a redirection inside Apache configuration ?</p>
<p dir="auto">Should I completely destroy my server and build a new one  to fix the problem ? Already spent many hours vannishing trying to fix it by myself.</p>
]]></description><link>http://forums.fogproject.org/topic/18299/fog-server-certificate-validation-failed</link><generator>RSS for Node</generator><lastBuildDate>Mon, 02 Nov 2026 15:41:03 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18299.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 02 Nov 2026 14:18:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to FOG Server : Certificate validation failed on Mon, 02 Nov 2026 15:07:51 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49783">@fgaudin</a> Do not rebuild the server. The <code>-C</code> flag caused this, and you can recover from it.</p>
<p dir="auto"><code>-C</code> means <code>--recreate-CA</code>. It deletes the FOG root CA and makes a new one. It also deletes the Secure Boot keys under <code>/opt/fog/pki/secureboot</code>. Each FOG Client stored the old CA when it was installed. The new server certificate is signed by a different CA, so the client says “Certificate is not from FOG CA”. This is expected after <code>-C</code>.</p>
<p dir="auto">Do these steps:</p>
<ol>
<li>Remove the certificates that you made by hand. They are not part of the FOG chain, and they add a second problem.</li>
<li>Run the installer again without <code>-C</code>: <code>./installfog.sh -y</code>. The installer makes the missing pieces from the new CA.</li>
<li>On each Windows client, open <code>certlm.msc</code>. Go to Trusted Root Certification Authorities &gt; Certificates. Delete “FOG Server CA”. Restart the FOGService. The client then gets the new CA from the server. If that does not work, reinstall the FOG Client on that computer.</li>
</ol>
<p dir="auto">About <code>srvpublic.crt</code>: Apache does not redirect it. On Debian the web files are in <code>/var/www/html/fog/</code>. Look in <code>/var/www/html/fog/management/other/ssl/</code>.</p>
<p dir="auto">If step 2 shows “Cannot read Secure Boot signing file” again, post the full installer command and the log from <code>bin/error_logs/</code> in your fogproject folder.</p>
]]></description><link>http://forums.fogproject.org/post/158920</link><guid isPermaLink="true">http://forums.fogproject.org/post/158920</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Mon, 02 Nov 2026 15:07:51 GMT</pubDate></item></channel></rss>