The FOG client needs to be included in the reference image (with the service disabled) before you capture it. Posts deployment you would use the setupcomplete.cmd file to reenable the service. This keeps the fog client for executing commands to early in the OOBE install process that causes an install failure.
With that said you can include (inject) the fog client install post imaging with a fog post install script. This script would (in concept) copy the msi from the fog server to the target computer and then append the msi install commands to the setupcomplete.cmd file that will be executed once the OOBE process is complete. But the FOG server does not do this out of the box.
The default location of the certificate on the server I think is /opt/fog/snapins/ssl and if this isn’t where you have it because you did custom stuff, you probably need to set the correct path via the Web interface for the storage node. It should be labeled something along the lines of ssl or CA or cert or something.
If you’ve not done anything custom, you probably are putting in the wrong server address during the fog client installation. This is the most likely issue.