Client 11.9 Will not Install Fails at CA Certificates
-
From what I can tell, you currently have two versions of fog running on the same machine. Of course I can’t be sure.
When you go to the GUI, do you see 1.2.0 in the cloud or do you see the version and datetime information to the right of the Cloud icon?
To ensure all is okay, I might suggest:
sudo mv /var/www/fog{,_back} sudo mv /var/www/html/fog{,_back}Then rerun the installer:
(You should be able to use recreate-keys as well if you deem it necessary).
./installfog.sh -y --recreate-keys -
The 1.2.0 was at a previous company, this is the only FOG server here. The info is to the right of the cloud as it should be.
Also, forgot to put ./ in front of installfog.sh, so that’s my bad, sorry.
I was able to run the recreate keys command and still no luck.
Ran the command with the -y parameter and still nothing.
-
@jackiegl3350n Is there any logs with any further information?
I don’t know where, but I would think the C:\fog.log or even “zazzles.log (of which I don’t know where that would be at the moment)” that might have more useful information?
I’ve seen error’s like this occur due to timing as well.
For example, the FOG Server is set to local time, but the machine is set to pacific when it should be new york?
This would cause a failure because the times don’t match one another. Essentially, it would make the client machine think the certs are no longer valid as the server is “ahead”.
This can happen in reverse too I suppose.
-
Both client and server are set to Eastern time and show exactly the same time right down to the second.
I can’t find any log files on the client after running the installer.
-
Trying to hit up on chat, in hopes that I can help out.
-
All seems to be working now.
-
For future reference, our antivirus was blocking the application from communicating with the server.
-
Well that would make a ton of sense.
-
@jackiegl3350n said in Client 11.9 Will not Install Fails at CA Certificates:
For future reference, our antivirus was blocking the application from communicating with the server.
More details please, which antivirus product caused it, have you added an exclusion or how did you solve it?
Regards X23
-
We have Kaspersky. Apparently the System Watcher module was blocking the client from communicating with the server. When this was disabled, the client installed. However, the Firewall module in Kaspersky also blocked tasks from the server to be executed on the client (remote shutdown for example). The bottom article might help other Kaspersky users, though we haven’t tried this yet as of this posting.
