# Google sso read operation timed out

**URL:** <https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476>\
**Category:** Pritunl VPN\
**Created:** [August 8, 2025, 9:03am UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476 "2025-08-08T09:03:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![witoon](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/w/e79b87/32.png) [@witoon](https://forum.pritunl.com/u/witoon)\
**Post date:** [August 8, 2025, 9:03am UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/1 "2025-08-08T09:03:23Z")

</div>

We’ve got below error regularly for a couple of days when user tried to login using google sso

Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: #033[1;93m[sentry-gate-main-1]#033[0m#033[1m[2025-08-08 08:59:42,727]#033[0m#033[1;91m[ERROR]#033[0m Google auth check error  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: #033[1;91mTraceback (most recent call last):#033[0m  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/user/user.py”, line 405, in sso\_auth\_check  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: valid, google\_groups = sso.verify\_google(self.email)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/sso/google.py”, line 43, in verify\_google  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: results = service.groups().list(userKey=user\_email,  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/googleapiclient/\_helpers.py”, line 130, in positional\_wrapper  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: return wrapped(\*args, \*\*kwargs)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/googleapiclient/http.py”, line 923, in execute  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: resp, content = \_retry\_request(  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/googleapiclient/http.py”, line 222, in \_retry\_request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: raise exception  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/googleapiclient/http.py”, line 191, in \_retry\_request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: resp, content = http.request(uri, method, \*args, \*\*kwargs)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/google\_auth\_httplib2.py”, line 218, in request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: response, content = self.http.request(  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/httplib2/ **init**.py”, line 1720, in request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: (response, content) = self.\_request(  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/httplib2/ **init**.py”, line 1440, in \_request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: (response, content) = self.\_conn\_request(conn, request\_uri, method, body, headers)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/site-packages/httplib2/ **init**.py”, line 1392, in \_conn\_request  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: response = conn.getresponse()  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/http/client.py”, line 1377, in getresponse  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: response.begin()  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/http/client.py”, line 320, in begin  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: version, status, reason = self.\_read\_status()  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/http/client.py”, line 281, in \_read\_status  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: line = str(self.fp.readline(\_MAXLINE + 1), “iso-8859-1”)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/socket.py”, line 716, in readinto  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: return self.\_sock.recv\_into(b)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/ssl.py”, line 1275, in recv\_into  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: return self.read(nbytes, buffer)  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: File “/usr/lib/pritunl/usr/lib/python3.9/ssl.py”, line 1133, in read  
Aug 8 09:00:07 sentry-gate-main-1 pritunl[4500]: return self.\_sslobj.read(len, buffer)

I’m not sure if it’s pritunl issue or google issue but anyone have an idea on how do I troubleshoot

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [August 8, 2025, 10:07am UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/2 "2025-08-08T10:07:08Z")

</div>

This is likely an incorrect API key. Verify the Google JSON Private Key is configured correctly in the top right settings and the permissions are correct in the Google Workspace settings.

---

<div class="post-metadata">

**Author:** ![witoon](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/w/e79b87/32.png) [@witoon](https://forum.pritunl.com/u/witoon)\
**Post date:** [August 8, 2025, 10:36am UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/3 "2025-08-08T10:36:01Z")

</div>

I’ve verify that key is correct and we can login if we retry multiple times, I don’t think key is the issue.

---

<div class="post-metadata">

**Author:** ![andrey-tuzhilin](https://forum.pritunl.com/user_avatar/forum.pritunl.com/andrey-tuzhilin/32/1317_2.png) [@andrey-tuzhilin](https://forum.pritunl.com/u/andrey-tuzhilin)\
**Post date:** [August 8, 2025, 6:05pm UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/4 "2025-08-08T18:05:11Z")

</div>

Same issue here. We have a `valid, google_groups = sso.verify_google(self.email)` call timing out. This has been happening periodically since approximately `Aug 08 at 11:51:37 UTC`.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [August 8, 2025, 10:04pm UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/5 "2025-08-08T22:04:36Z")

</div>

If the issue is intermittent run the command below. This will disable the hourly single sign-on check for connected users.

`sudo pritunl set app.sso_connection_check false`

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [August 9, 2025, 11:21pm UTC](https://forum.pritunl.com/t/google-sso-read-operation-timed-out/3476/6 "2025-08-09T23:21:39Z")

</div>

An update has been released Pritunl v1.32.4349.59 that will implement rate limiting and remove redundant usage of the Google Workspace API. This should fix issues with active connections dropping but new connection requests need the API validation. If the API issues continue it may take multiple connection attempts for a user to connect. If set commands were used to disable single sign-on checks temporarily, run the commands below after updating to revert the single sign-on skip options to the default values. These commands can be run even if no changes were made to verify the values have the correct default configuration.

```shell
sudo pritunl unset app.sso_connection_check
sudo pritunl unset user.skip_remote_sso_check

```
