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) 4월 28, 2020, 11:22오전 5

다음 링크를 따라 문제를 해결했습니다: Google Login Stopped Working after manual update

글		댓글	조회수
Not able to log in with Google token Product Support	7	690	11월 26, 2020
Google sign up discorse time settings Product Support	3	579	12월 7, 2020
Google login not working due to incorrect server time Product Support	8	1715	7월 29, 2019
Google Login Stopped Working after manual update Product Support	5	1086	3월 8, 2019
Google auth error Product Support	6	1332	10월 7, 2020

오류: 서버 시간 차이로 인해 인증 토큰을 확인하지 못함

Related topics