Communication ERROR: operation timed out, could not authenticate, obj error

[Tom Elliott]

When you see “Invalid security token” go to the GUI, locate the relevant host, click Reset Encryption Data.

[kverkiss]

@Tom-Elliott I have the exact same problem, started recently. I have also upgraded the fog server to a newer revision.

21-4-2016 16:24 Client-Info Version: 0.9.12
21-4-2016 16:24 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
21-4-2016 16:24 Data::RSA FOG Server CA cert found
21-4-2016 16:24 Middleware::Authentication Cert OK
21-4-2016 16:24 Middleware::Communication POST URL: http://10.10.2.250/fog/management/index.php?sub=authorize
21-4-2016 16:24 Middleware::Communication ERROR: Failed to POST data
21-4-2016 16:24 Middleware::Communication ERROR: De externe server heeft een fout geretourneerd: (417) Expectation Failed.
21-4-2016 16:24 Middleware::Authentication ERROR: Could not authenticate
21-4-2016 16:24 Middleware::Authentication ERROR: Object reference not set to an instance of an object.
21-4-2016 16:24 Service Sleeping for 120 seconds

[kverkiss]

@Tom-Elliott Besides I did all your provided steps as well, clearing the security token data.

[Tom Elliott]

@kverkiss What version of FOG are you running? Having the “exact same problem” is only relevant if you’re on the exact same version.

[kverkiss]

@Tom-Elliott Hi Tom, I do have revision 7248.

[kverkiss]

@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:

@Tom-Elliott Hi Tom, I do have revision 7248.

The only difference I have, for this revision there is not token.dat created in c:\windows\system32\

[Tom Elliott]

@kverkiss can you update and try again?

[kverkiss]

@Tom-Elliott Different errors this time:

 21-4-2016 17:04 Client-Info Version: 0.9.12
 21-4-2016 17:04 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
 21-4-2016 17:04 Data::RSA FOG Server CA cert found
 21-4-2016 17:04 Data::RSA ERROR: Certificate validation failed
 21-4-2016 17:04 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid)
 21-4-2016 17:04 Middleware::Authentication ERROR: Could not authenticate
 21-4-2016 17:04 Middleware::Authentication ERROR: Certificate is not from FOG CA
 21-4-2016 17:04 Service Sleeping for 120 seconds
 21-4-2016 17:05 Bus Registering ParseBus in channel Power
 21-4-2016 17:05 Bus Became bus client
 21-4-2016 17:05 Bus Registering OnNotification in channel Notification
 21-4-2016 17:05 Bus Registering OnUpdate in channel Update```

[Tom Elliott]

Found a rather nasty (unknown bug), can you update again?

[kverkiss]

@Tom-Elliott Rev 7252:

 21-4-2016 17:13 Client-Info Version: 0.9.12
 21-4-2016 17:13 Middleware::Communication URL: http://10.10.2.250/fog/management/other/ssl/srvpublic.crt
 21-4-2016 17:13 Data::RSA FOG Server CA cert found
 21-4-2016 17:13 Data::RSA ERROR: Certificate validation failed
 21-4-2016 17:13 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: Kan de handtekening van het certificaat niet controleren. (NotSignatureValid)
 21-4-2016 17:13 Middleware::Authentication ERROR: Could not authenticate
 21-4-2016 17:13 Middleware::Authentication ERROR: Certificate is not from FOG CA
 21-4-2016 17:13 Service Sleeping for 120 seconds
 21-4-2016 17:14 Bus Registering ParseBus in channel Power
 21-4-2016 17:14 Bus Became bus client
 21-4-2016 17:14 Bus Registering OnNotification in channel Notification
 21-4-2016 17:14 Bus Registering OnUpdate in channel Update

[Tom Elliott]

@kverkiss that means your ca changed. Fog doesn’t do that automatically. Do you have the original servers CA information somewhere?

[kverkiss]

@Tom-Elliott I could do a rollback to an older version. I did update the certificate because this server had an IP change.

[Tom Elliott]

@kverkiss updating keys would’ve been fine but from the looks of things it also recreated the ca information. Rolling back would not solve the problem unless you have a snapshot from before the ip changed or before you updated the ca information.

[kverkiss]

@Tom-Elliott Hi Tom,
I just did a rollback over VMware to our server backup from last night. It is working fine now. Now I have updated the the most recent revison and no errors show up. I am currently monitoring if the problem reappears.

[Joe Schmitt]

@kverkiss The --recreate-keys option for the installer re-configures the certificates to your new IP, but --recreate-CA resets the identity. This will “block” all clients from communicating with the server.

[kverkiss]

@Jbob Thanks for the information!

[kverkiss]

@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:

@Jbob Thanks for the information!

The problem has been resolved. Thanks for all help.