Stuck on pinning server
-
Hello,
I’ve got a problem during client installation.
My server FOG has this address IP : 192.168.39.243
From the client i can ping the server from IP address
During installation, it stucks on “pinning server” then fail with “cannot install certificate”.This problem occurs only when i try to use IP address, it works fine if i use the short dns name.
I’m using Fog server 1.5.8
Fog client 0.11.19
Windows 10 1909Have you got an explanation ?
Thanks for your help.Pascal
-
@plegrand Do I remember correctly. You have a HTTPS setup?!
The 0.11.19 fog-client did not have the option to pinn to a HTTPS only FOG server. Please download the latest client and give that a try: https://github.com/FOGProject/fog-client/releases/tag/0.12.0
-
@Sebastian-Roth No it’s on http only
-
@Sebastian-Roth
My fog server has this ip addresse: 192.168.39.243
The fog client is configured with this ip addresse
I can ping it from the client with adresse ip, short dns name, long dns name.
I can get the file http://192.168.39.243/fog/management/other/ssl/srvpublic.crt from the client and Firefox, edge and curl.But i see these errors in fog.log
24/09/2020 10:20:52 Client-Info Version: 0.11.19 24/09/2020 10:20:52 Client-Info OS: Windows 24/09/2020 10:20:52 Middleware::Authentication Waiting for authentication timeout to pass 24/09/2020 10:21:49 Middleware::Communication Download: http://192.168.39.243/fog/management/other/ssl/srvpublic.crt 24/09/2020 10:22:52 Middleware::Communication ERROR: Could not download file 24/09/2020 10:22:52 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle.
24/09/2020 10:24:52 Client-Info Version: 0.11.19 24/09/2020 10:24:52 Client-Info OS: Windows 24/09/2020 10:24:52 Middleware::Authentication Waiting for authentication timeout to pass 24/09/2020 10:25:49 Middleware::Communication Download: http://192.168.39.243/fog/management/other/ssl/srvpublic.crt 24/09/2020 10:26:52 Middleware::Communication ERROR: Could not download file 24/09/2020 10:26:52 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle. 24/09/2020 10:26:52 Middleware::Communication URL: http://192.168.39.243/fog/management/index.php?sub=requestClientInfo&configure&newService&json 24/09/2020 10:27:55 Middleware::Communication ERROR: Could not contact FOG server 24/09/2020 10:27:55 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle. 24/09/2020 10:27:55 Middleware::Response Success 24/09/2020 10:27:55 Service ERROR: Invalid promptTime, using default 24/09/2020 10:27:55 Middleware::Communication URL: http://192.168.39.243/fog/management/index.php?sub=requestClientInfo&mac=60:F2:62:1A:2B:84|62:F2:62:1A:2B:83|60:F2:62:1A:2B:83|34:48:ED:02:2F:CF|60:F2:62:1A:2B:87&newService&json 24/09/2020 10:28:58 Middleware::Communication ERROR: Could not contact FOG server 24/09/2020 10:28:58 Middleware::Communication ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle. 24/09/2020 10:28:58 Middleware::Response Success 24/09/2020 10:28:58 Middleware::Communication URL: http://192.168.39.243/fog/service/getversion.php?clientver&newService&json 24/09/2020 10:30:01 Service ERROR: Unable to get cycle data 24/09/2020 10:30:01 Service ERROR: Le serveur distant a retourné une erreur : (504) Dépassement du délai de la passerelle. 24/09/2020 10:30:01 Middleware::Response Success 24/09/2020 10:30:01 Service Initializing modules
The time/date are corrects on client and server
I’m lost !!
-
@Sebastian-Roth
I saw that the client load the following url :
http://192.168.39.243/fog/status/getservertime.php
It get the following time : Sep 24, 2020 14:37 pm
In fact the time is 16:37 pm
But on the server :
[root@fog] ~ # date
jeudi 24 septembre 2020, 16:38:44 (UTC+0200)Is it the problem ?
-
@plegrand I don’t think the time difference is causing the issue for you. While I don’t speek French I suppose the message returned by the FOG server is a 504 HTTP error. Please take a look at the Apache serverlogs to find out what it complains about. See my signature in where to find those logs.
-
@Sebastian-Roth There is nothing in error.log
-
@plegrand The log you posted doesn’t seem to come from a fresh fog-client install but from existing clients. Possibly many or all your clients are unable to communicate with the FOG server and that puts such a load onto it that it returns with HTTP 504 (gateway timeout).
Have you looked at the logs of a couple of your clients. Do others work fine? How many hosts with fog-client installed do you have?
-
@Sebastian-Roth
I made the test with a fresh install of the latest client with same problems. -
@plegrand Do other clients work properly or do they all show those messages in the client logs?