Fogclient and token.dat missing

[pbriec]

Hi everybody,

I’m going crazy. The Fog client doesn’t work anymore and i don’t know to solve this problem.
I’ve updated to latest fog 1.5.10.1629 on debian 11
I’m running fog client 0.13
here is the fog.log

05/12/2024 16:48:42 Main Overriding exception handling
05/12/2024 16:48:43 Main Bootstrapping Zazzles
05/12/2024 16:48:43 Controller Initialize
05/12/2024 16:48:43 Controller Start

05/12/2024 16:48:43 Service Starting service
05/12/2024 16:48:51 Bus Became bus server
05/12/2024 16:48:51 Bus Emmiting message on channel: Status
05/12/2024 16:48:51 Service Invoking early JIT compilation on needed binaries

---

--------------------------------Authentication--------------------------------

05/12/2024 16:48:51 Client-Info Version: 0.13.0
05/12/2024 16:48:51 Client-Info OS: Windows
05/12/2024 16:48:51 Middleware::Authentication Waiting for authentication timeout to pass
05/12/2024 16:48:51 Middleware::Communication Download: http://172.16.0.8/fog/management/other/ssl/srvpublic.crt
05/12/2024 16:48:52 Middleware::Authentication Cert OK
05/12/2024 16:48:52 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
05/12/2024 16:48:52 Middleware::Authentication ERROR: Could not get security token
05/12/2024 16:48:52 Middleware::Authentication ERROR: Le fichier ‘C:\Program Files (x86)\FOG\token.dat’ est introuvable.
05/12/2024 16:48:52 Middleware::Communication POST URL: http://172.16.0.8/fog/management/index.php?sub=requestClientInfo&authorize&newService
05/12/2024 16:48:52 Middleware::Response Invalid security token

Can anybody help me, please?
Snapins doesn’t work anymore, i can’t shutdown machines using Power management. It’s very annoying.

I’ve reboot server, client, it doesn’t change.

thanks in advance
Pierre

[raul]

I’ve solved this “Invalid security token” error before with two methods.

This error usually happens because the security trust between the node and the server is broken or the encryption keys don’t match.
First, try deleting the host from the FOG Web UI, then perform a Quick Registration on the client machine and run the install again, this resets the trust relationship from scratch.

If the token.dat is still missing after that, open services.msc, manually start the FOGService, and reboot the computer. Manually triggering the service often forces the client to check in and finally generate the missing token.dat file.

[JJ Fullmer]

@pbriec Sorry that your post got lost in the shuffle, I saw it pop up with @raul’s response.
I imagine/hope you got past this in the last year but just in case, the fix would most likely be resetting the host encryption from the web ui (removes some token related database entries on the host record) then restarting the fog service on the client.

If that didn’t do the trick, then restarting the fog service along with resetting the hots encryption should fix it.