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) 2020 年 4 月 28 日午前 11:22 5

以下の手順で解決しました: Google Login Stopped Working after manual update

トピック		返信	表示
Not able to log in with Google token Support	7	615	2020 年 11 月 26 日
Google sign up discorse time settings Support	3	523	2020 年 12 月 7 日
Google login not working due to incorrect server time Support	8	1624	2019 年 7 月 29 日
Google Login Stopped Working after manual update Support	5	1019	2019 年 3 月 8 日
Google auth error Support	6	1248	2020 年 10 月 7 日

エラー「サーバーの時刻の違いにより認証トークンの検証ができませんでした」

関連トピック