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

support
1

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.

whenever I try to log in with Google (I haven’t tried the other login methods except username/password).

I’m not sure what causes this error, and there’s no search results with answers on Google.

I did look at my server’s NTP logs, and I see errors like

ntpd[23986]: giving up resolving host 1.arch.pool.ntp.org: Servname not supported for ai_socktype (-8)

which seems like it would be related (causing a clock difference). Is this in fact what the problem may be?

1 Like
2

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.

4 Likes
3

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!

2 Likes
4

im facing the same issue,
please see output of grep ntp /etc/services

image
image1262×248 44.6 KB

Does anyone else know what else can i do to fix this?

@RGJ

5

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

3 Likes
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.