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…

[image] 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.

Error "Unable to verify authorization token due to server clock differences"

Support

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

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

3 Likes

Topic		Replies	Views
Not able to log in with Google token Support	8	579	December 26, 2020
Google sign up discorse time settings Support	3	494	December 7, 2020
Server Error with Google OAuth2 login, again Support	2	901	May 24, 2016
Google Authentication Bug On Discourse Bug	5	1461	January 11, 2016
Twitter & Google login not working any more Support	7	1108	March 29, 2022

Error "Unable to verify authorization token due to server clock differences"

Related Topics