Fog Client fails to authenticate
-
Server
- FOG Version: SVN 6069
- OS: Ubuntu Linux 14.04.3
Client
- Service Version: 0.11.12
- OS: windows 10
Client fails to authenticate and preform any tasks Nor does the FOG webpage display the reset encryption button so I reset it by adding it to a group. Here is the fog log.
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 29/05/2017 11:24 Client-Info Version: 0.11.12 29/05/2017 11:24 Client-Info OS: Windows 29/05/2017 11:24 Middleware::Authentication Waiting for authentication timeout to pass 29/05/2017 11:26 Middleware::Communication Download: http://10.200.10.150/fog/management/other/ssl/srvpublic.crt 29/05/2017 11:26 Middleware::Authentication ERROR: Could not authenticate 29/05/2017 11:26 Middleware::Authentication ERROR: Value cannot be null. Parameter name: authority 29/05/2017 11:26 Middleware::Communication URL: http://10.200.10.150/fog/management/index.php?sub=requestClientInfo&configure&newService&json 29/05/2017 11:26 Middleware::Response Success 29/05/2017 11:26 Middleware::Communication URL: http://10.200.10.150/fog/management/index.php?sub=requestClientInfo&mac=3C:52:82:39:0F:52|98:54:1B:F4:84:AE|98:54:1B:F4:84:AF|98:54:1B:F4:84:B2&newService&json 29/05/2017 11:26 Middleware::Authentication Waiting for authentication timeout to pass 29/05/2017 11:27 Controller Stop 29/05/2017 11:27 Service Stop requested 29/05/2017 11:27 Bus Emmiting message on channel: Status 29/05/2017 11:27 Middleware::Authentication ERROR: Could not authenticate 29/05/2017 11:27 Middleware::Authentication ERROR: Thread was being aborted. 29/05/2017 11:27 Middleware::Communication ERROR: Could not contact FOG server 29/05/2017 11:27 Middleware::Communication ERROR: Thread was being aborted. 29/05/2017 11:27 Service ERROR: Unable to get cycle data 29/05/2017 11:27 Service ERROR: Thread was being aborted. -
@sebastian-roth I have been busy with other things and finally revisited this issue. Recreating the certificate and tokens fixed my authentication problem I may have and AD join issue but will troubleshoot further before I open a new topic on it.
-
Normally I see this kind of thing if the system dates are incorrect. Of course this doesn’t mean this is the case here, just stating what I normally see. Is it possible the FOG Server has fallen out of time and having issues because of this?
-
Not in this case I did find references to that being a possible solution I also went to the server directly and confirmed the cert is there and downloadable.
-
This is the first time we have tried to use the new client all our current installs are with the legacy client.
-
Ok I probably did something stupid I saw @Tom-Elliott response to https://forums.fogproject.org/topic/10168/linux-client-could-not-authenticate/3 and tried it on my server before I realized the steps were intended for the client not the server now my fog client log looks like this.
--------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 31/05/2017 13:22 Client-Info Client Version: 0.11.12 31/05/2017 13:22 Client-Info Client OS: Windows 31/05/2017 13:22 Client-Info Server Version: 1.4.0 31/05/2017 13:22 Middleware::Response ERROR: Unable to get subsection 31/05/2017 13:22 Middleware::Response ERROR: Object reference not set to an instance of an object. ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 31/05/2017 13:22 Client-Info Client Version: 0.11.12 31/05/2017 13:22 Client-Info Client OS: Windows 31/05/2017 13:22 Client-Info Server Version: 1.4.0 31/05/2017 13:22 Middleware::Response ERROR: Unable to get subsection 31/05/2017 13:22 Middleware::Response ERROR: Object reference not set to an instance of an object. ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 31/05/2017 13:22 Client-Info Client Version: 0.11.12 31/05/2017 13:22 Client-Info Client OS: Windows 31/05/2017 13:22 Client-Info Server Version: 1.4.0 31/05/2017 13:22 Middleware::Response ERROR: Unable to get subsection 31/05/2017 13:22 Middleware::Response ERROR: Object reference not set to an instance of an object. ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 31/05/2017 13:22 Client-Info Client Version: 0.11.12 31/05/2017 13:22 Client-Info Client OS: Windows 31/05/2017 13:22 Client-Info Server Version: 1.4.0 31/05/2017 13:22 Middleware::Response ERROR: Unable to get subsection 31/05/2017 13:22 Middleware::Response ERROR: Object reference not set to an instance of an object. ------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 31/05/2017 13:22 Client-Info Client Version: 0.11.12 31/05/2017 13:22 Client-Info Client OS: Windows 31/05/2017 13:22 Client-Info Server Version: 1.4.0 31/05/2017 13:22 Middleware::Response ERROR: Unable to get subsection 31/05/2017 13:22 Middleware::Response ERROR: Object reference not set to an instance of an object. 31/05/2017 13:22 Service Sleeping for 170 seconds -
@Joseph-Hales What you did on the fogserver shouldn’t impact anything.
On the main client’s however, would you mind uninstalling and reinstalling the client to see if that helps?
-
first step I did on client was uninstalled the client then I did the mono cleanup and update then i reinstalled the client but I will try again
-
After reinstall of client I am back to the original issue of value cannot be null.
-
Also note the Reset Encryption button never appears for the host but I can add it to a group and see it there.
-
@Joseph-Hales Group’s don’t know the status, so I make that button always present.
-
Upgraded server to latest SVN today 6072 same issue as shown below.
------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 12/06/2017 17:35 Client-Info Version: 0.11.12 12/06/2017 17:35 Client-Info OS: Windows 12/06/2017 17:35 Middleware::Authentication Waiting for authentication timeout to pass 12/06/2017 17:35 Middleware::Communication Download: http://10.200.10.150/fog/management/other/ssl/srvpublic.crt 12/06/2017 17:35 Middleware::Authentication ERROR: Could not authenticate 12/06/2017 17:35 Middleware::Authentication ERROR: Value cannot be null. Parameter name: authority ------------------------------------------------------------------------------ --------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ -
@Joseph-Hales Is this still an issue? Just wondering because we seem to have other reports on this.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
I had this exact error message - also imaging windows 10 and also first time with new client, coming from legacy. For me this worked:
Through FOG GUI:
1.) Reset encryption data
2.) Put the FQDN in WITH the .net or whatever appendage (honeygroveisd.net) <-----works but -----> (honeygroveisd) did not.
3.) Clear out the OU container fields completely and leave it blank.I made sure these settings were mirrored both in the group settings and in the global settings. After doing all of this it no longer gave me errors.
I highly doubt all of these were necessary but I was getting desperate
-
@JLE For this particular errors I doubt that any of your actions helped in solving this. I suspect you reinstalled and that just solved the issue. See my post here: https://forums.fogproject.org/topic/10562/active-directory-join-fails
-
@sebastian-roth Hmm. I definitely do not reinstall anything after sysprep. I run .\sysprep /generalize /oobe /unattend /shutdown and then capture. I have the fog service set to manual with recovery options set to restart it. After the images are deployed the batch file does a net start fogservice and then they join the domain.
-
@sebastian-roth I have been busy with other things and finally revisited this issue. Recreating the certificate and tokens fixed my authentication problem I may have and AD join issue but will troubleshoot further before I open a new topic on it.
-
@Joseph-Hales Ok, thanks for reporting back on this. Will mark this solved then. Feel free to open a new post on the AD issue if you can’t figure it out yourself.
