Is the client rejecting the custom CA going to cause problems?
-
At the behest of my IT Sec department, I installed their custom CA and certs on the FOG server. This makes browsers happy and when connecting to the web interface and more importantly gets their vulnerability scanner to leave me alone.
However, I’m seeing the following error in the client log:
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 5/13/2026 3:39:24 AM Client-Info Version: 0.13.0 5/13/2026 3:39:24 AM Client-Info OS: Windows 5/13/2026 3:39:24 AM Middleware::Authentication Waiting for authentication timeout to pass 5/13/2026 3:41:24 AM Middleware::Communication Download: https://fho-fog/fog/management/other/ssl/srvpublic.crt 5/13/2026 3:41:24 AM Data::RSA ERROR: Certificate validation failed 5/13/2026 3:41:24 AM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Thumbprints did not match. 5/13/2026 3:41:24 AM Middleware::Authentication ERROR: Could not authenticate 5/13/2026 3:41:24 AM Middleware::Authentication ERROR: Certificate is not from FOG CA 5/13/2026 3:41:24 AM Client-Info ERROR: Failed to authenticate, will not run Module Looper.Based on what I can tell from this guide, this is normal behavior as the client is unable to recognize the custom CA without recompiling the client (which I would rather not bother with anyway). What isn’t clear is if this means that the client will continue to work as it should despite not trusting the CA.
Can I safely ignore this error?