Certificate is not from FOG CA
-
What is the Middleware Commuinication? How can I debug Middleware? (i also tried to remove and reinstall the client).
Michael
-
@holzfisch Can you delete the Trusted CA that you have for the FOG Server that’s labeled as:
192.168.1.14CAThen go to http://192.168.1.14/fog/management/other/ca.cert.der in Chrome or Firefox (as IE will just display the file as if it’s plain text) and install THAT certificate?
This should fix your registry issue. You might have to reset the encryption data for the hosts that were affected as well, but ultimately you should be good to go after that. The CA Name in the Certificate Manager should be: “FOG Server CA”
Middleware is the new name of the CommunicationHandler class. It was renamed because, while it does deal with communication, it’s essentially the Middle man of the Client to Server communications and data operations to move in between the other modules. It IS middleware and was named more appropriately.
@Jbob I believe has a debugger function already created and setup on the forums. I’ll update this post with the link that shows where to download the file and how to use it.
Here is the Link to the forum post:
https://forums.fogproject.org/topic/5074/ad-join-rename-on-client-0-8-1/5 -
Be sure to install that ca.cer.der file under Local System and as a Trusted Root Certificate Authority. What happened is that the client “pinned” an old format of the CA certificate that Tom released for a few versions in hopes of multiple FOG server support but was removed shortly after.
-
Thanks for the answers. Removed the old certificate under “Trusted Root Certificate Authority”. Installed the new (“Trusted Root Certificate Authority”. )(http://192.168.1.14/fog/management/other/ca.cert.der). It has still the name 192.168.1.14CA. After installing it still the problem stays the same:
--------------------------------Authentication--------------------------------
08.06.2015 11:29 RegistryHandler 64 bit registry detected
08.06.2015 11:29 Client-Info Version: 0.8.3
08.06.2015 11:29 Middleware::Communication URL: http://192.168.1.14/fog/management/other/ssl/srvpublic.crt
08.06.2015 11:29 Middleware::Communication ERROR: Could not download file
08.06.2015 11:29 Middleware::Communication ERROR: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
08.06.2015 11:29 Middleware::Authentication ERROR: Could not get security token
08.06.2015 11:29 Middleware::Authentication ERROR: Die Datei “C:\Windows\system32\token.dat” konnte nicht gefunden werden.
08.06.2015 11:29 Middleware::Authentication ERROR: Could not authenticate
08.06.2015 11:29 Middleware::Authentication ERROR: Das System kann die angegebene Datei nicht finden.did something go wrong with a upgrade?
i get the file (http://192.168.1.14/fog/management/other/ssl/srvpublic.crt) ,when using chrome.Please help
-
Debugger ist not working with client 084 (from the mentioned post).
There is no encryption data to delete. (see screenshot).
greetings
Michaelfog.log
-
Tried: delayed start of the fog service . (Problem after downloading returns - started a new posting)
Michael
-
Linux version 3.13.0-51-generic (buildd@lamiak) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #84-Ubuntu SMP Wed Apr 15 12:08:34 UTC 2015
Description: Ubuntu 14.04.2 LTS
FOG Version: SVN 3537
Clients: Windows 8.1
FOG Client Version: 0.8.4Hi!
Problem is not solved:
fog.7z
Get this error after download from server. (fog.log as attachment)10.06.2015 10:12 Client-Info Version: 0.8.4
10.06.2015 10:12 Middleware::Communication URL: http://192.168.1.14/fog/management/other/ssl/srvpublic.crt
10.06.2015 10:12 Middleware::Authentication ERROR: Could not get security token
10.06.2015 10:12 Middleware::Authentication ERROR: Die Datei “C:\Windows\system32\token.dat” konnte nicht gefunden werden.
10.06.2015 10:12 Data::RSA ERROR: Could not verify certificate is from CA
10.06.2015 10:12 Data::RSA ERROR: Der Wert darf nicht NULL sein.
Parametername: certificate
10.06.2015 10:12 Middleware::Authentication ERROR: Could not authenticate
10.06.2015 10:12 Middleware::Authentication ERROR: Certificate is not from FOG CA
Installed client 084 (removed manually install dir) . then it worked for the cloning client. After uploading i had the same problem.
Why do i get always 192.168.1.14CA?
Where do i delete the encryption data for the client? There is no button on the web-interface?Removed it and installed http://192.168.1.14/fog/management/other/ca.cert.der but certificate stays 192.168.1.14CA.
Tried the debugger (admin rights) in the fog folder, but it is not working.
thanks for the time helping me.
Michael
-
After a while i get “Error multiple hosts returned for list of mac addresses” (virtual box is installed so the mac is sometimes the same on the clients - had the same problem with early versions of the old client).
--------------------------------HostnameChanger-------------------------------
10.06.2015 15:14 Client-Info Version: 0.8.4
10.06.2015 15:14 HostnameChanger Running…
10.06.2015 15:14 Middleware::Communication URL: http://192.168.1.14/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=00:22:FB:2B:FF:A2|00:21:70:F6:44:E0|08:00:27:00:6C:21||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
10.06.2015 15:14 Middleware::Communication Unknown Response: Error multiple hosts returned for list of mac addresses -
@holzfisch said:
Installed client 084 (removed manually install dir) . then it worked for the cloning client. After uploading i had the same problem.
Why do i get always 192.168.1.14CA?
Where do i delete the encryption data for the client? There is no button on the web-interface?Removed it and installed http://192.168.1.14/fog/management/other/ca.cert.der but certificate stays 192.168.1.14CA.
Tried the debugger (admin rights) in the fog folder, but it is not working.
thanks for the time helping me.
Michael
Do you have an idea how to get the right certificate? I always get 192.168.1.14CA?
Michael
-
Problem solved. It was an issue with the installer.
-
I know this thread is quite old, but I wanted to include another possible cause because Google searches seem to bring you back to this thread.
I was experiencing the same issue with my Windows 7 Fog clients, and resetting the encryption data did nothing. It turned out to be the time was quite off on the client, so it was never able to authenticate with the Fog server. Once the time was corrected, the client connected and everything worked fine (hostname, join, etc.).
Just in case someone else runs into this issue, hopefully this can save you some time.
