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ص 5

تم الإصلاح باتباع الخطوات الواردة في: Google Login Stopped Working after manual update

الموضوع		الردود	مرات العرض
Not able to log in with Google token Support	7	616	26 نوفمبر 2020
Google sign up discorse time settings Support	3	528	7 ديسمبر 2020
Google login not working due to incorrect server time Support	8	1629	29 يوليو 2019
Google Login Stopped Working after manual update Support	5	1027	8 مارس 2019
Google auth error Support	6	1256	7 أكتوبر 2020

خطأ "تعذر التحقق من رمز التفويض بسبب اختلافات ساعة الخادم"

الموضوعات ذات الصلة