I have Google auth enabled, and it was working. But then something happened (I think I accepted an automatic update to my machine specs on linode.com ) and now Google auth doesn’t work, and Discourse says Unable to verify authorization token due to server clock differences. Please try again. when…

[imagen] trusktr: Servname not supported for ai_socktype What does grep ntp /etc/services tell you? There should be two lines: ntp 123/tcp ntp 123/udp If they’re not there, add them and restart your ntp service.

Thanks for the tip! Turns out I was confused: the Discourse is running on another server (my subdomain points to another PI) On this other machine NTP was not installed, so I installed it (apt install ntp in Ubuntu), and now there’s no problem!

im facing the same issue, please see output of grep ntp /etc/services [image] Does anyone else know what else can i do to fix this? @RGJ

fixed it by following, Google Login Stopped Working after manual update

Error "No se pudo verificar el token de autorización debido a diferencias en la hora del servidor"

Soporte

Faizan_Zahid (Faizan Zahid) 28 Abril, 2020 11:22 5

Se solucionó siguiendo: Google Login Stopped Working after manual update

Tema		Respuestas	Vistas
Not able to log in with Google token Support	8	614	26 Diciembre 2020
Google sign up discorse time settings Support	3	516	7 Diciembre 2020
Google login not working due to incorrect server time Support	9	1612	28 Agosto 2019
Google Login Stopped Working after manual update Support	6	1016	7 Abril 2019
Google auth error Support	7	1221	6 Noviembre 2020

Error "No se pudo verificar el token de autorización debido a diferencias en la hora del servidor"

Temas relacionados