# Error "Unable to verify authorization token due to server clock differences"
**URL:** https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685
**Category:** Support
**Created:** [April 12, 2020, 7:22am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685 "2020-04-12T07:22:20Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [April 12, 2020, 7:22am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/1 "2020-04-12T07:22:20Z")
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](http://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
```plaintext
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?
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [April 12, 2020, 9:21am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/2 "2020-04-12T09:21:59Z")
> [@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.
---
### Author:  [@trusktr](https://meta.discourse.org/u/trusktr)
#### Post date: [April 12, 2020, 9:41am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/3 "2020-04-12T09:41:40Z")
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!
---
### Author:  [@Faizan\_Zahid](https://meta.discourse.org/u/Faizan_Zahid)
#### Post date: [April 28, 2020, 10:38am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/4 "2020-04-28T10:38:42Z")
im facing the same issue,
please see output of `grep ntp /etc/services`
Does anyone else know what else can i do to fix this?
@RGJ
---
### Author:  [@Faizan\_Zahid](https://meta.discourse.org/u/Faizan_Zahid)
#### Post date: [April 28, 2020, 11:22am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/5 "2020-04-28T11:22:59Z")
fixed it by following, [Google Login Stopped Working after manual update](https://meta.discourse.org/t/google-login-stopped-working-after-manual-update/111029)
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [May 28, 2020, 11:23am UTC](https://meta.discourse.org/t/error-unable-to-verify-authorization-token-due-to-server-clock-differences/147685/6 "2020-05-28T11:23:00Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.