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…

[изображение] 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

Ошибка «Не удалось проверить токен авторизации из-за расхождений во времени на сервере»

Поддержка

Faizan_Zahid (Faizan Zahid) 28.Апрель.2020 11:22:59 5

исправил, следуя инструкции: Google Login Stopped Working after manual update

Тема		Ответов	Просм.
Not able to log in with Google token Support	7	634	26.11.2020
Google sign up discorse time settings Support	3	531	07.12.2020
Google login not working due to incorrect server time Support	8	1637	29.07.2019
Google Login Stopped Working after manual update Support	5	1040	08.03.2019
Google auth error Support	6	1268	07.10.2020

Ошибка «Не удалось проверить токен авторизации из-за расхождений во времени на сервере»

Связанные темы