# Pritunl Zero Crash auth: Google request failed

**URL:** <https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424>\
**Category:** Pritunl Zero\
**Tags:** pritunl-zero\
**Created:** [July 16, 2025, 9:48am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424 "2025-07-16T09:48:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ariretiarno](https://forum.pritunl.com/user_avatar/forum.pritunl.com/ariretiarno/32/517_2.png) [@ariretiarno](https://forum.pritunl.com/u/ariretiarno)\
**Post date:** [July 16, 2025, 9:48am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/1 "2025-07-16T09:48:35Z")

</div>

Hello @zach our zero trust pritunl is going down because of this  
[2025-07-16 09:20:32][ERRO] ▶ proxy: Serve error ◆ client=“52.220.0.189”  
auth: Google request failed  
Get “[https://auth.pritunl.com/update/google?license=46ffe408fbbb840790e60608c9fd42ad49810aad4452fb51291fd00e83120ca13567059ac90cb3716ab516b9ad2d80d5fe7d0877d596a37dc9faba898ff2bc20&user=aang.kurniawan%40evermos.com](https://auth.pritunl.com/update/google?license=46ffe408fbbb840790e60608c9fd42ad49810aad4452fb51291fd00e83120ca13567059ac90cb3716ab516b9ad2d80d5fe7d0877d596a37dc9faba898ff2bc20&user=aang.kurniawan%40evermos.com)”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)  
ORIGINAL STACK TRACE:  
[github.com/pritunl/pritunl-zero/auth.GoogleSync](http://github.com/pritunl/pritunl-zero/auth.GoogleSync)  
/go/src/github.com/pritunl/pritunl-zero/auth/google.go:193 +0x13c1ac5  
[github.com/pritunl/pritunl-zero/auth.SyncUser](http://github.com/pritunl/pritunl-zero/auth.SyncUser)  
/go/src/github.com/pritunl/pritunl-zero/auth/sync.go:39 +0x13c7338  
[github.com/pritunl/pritunl-zero/proxy.(\*Proxy).ServeHTTP](http://github.com/pritunl/pritunl-zero/proxy.(*Proxy).ServeHTTP)  
/go/src/github.com/pritunl/pritunl-zero/proxy/proxy.go:206 +0x15aef69  
[github.com/pritunl/pritunl-zero/router.(\*Router).ServeHTTP](http://github.com/pritunl/pritunl-zero/router.(*Router).ServeHTTP)  
/go/src/github.com/pritunl/pritunl-zero/router/router.go:99 +0x15d5cd8  
net/http.serverHandler.ServeHTTP  
/usr/local/go/src/net/http/server.go:3210 +0x778bed  
net/http.initALPNRequest.ServeHTTP  
/usr/local/go/src/net/http/server.go:3819 +0x75ecb0  
net/http.(\*http2serverConn).runHandler  
/usr/local/go/src/net/http/h2\_bundle.go:6249 +0x72bdf4  
runtime.goexit  
/usr/local/go/src/runtime/asm\_amd64.s:1700 +0x4799e0  
[2025-07-16 09:20:32][ERRO] ▶ proxy: Serve error ◆ client=“120.29.157.227”  
auth: Google request failed  
Get “[https://auth.pritunl.com/update/google?license=46ffe408fbbb840790e60608c9fd42ad49810aad4452fb51291fd00e83120ca13567059ac90cb3716ab516b9ad2d80d5fe7d0877d596a37dc9faba898ff2bc20&user=tezza.lantika%40evermos.com](https://auth.pritunl.com/update/google?license=46ffe408fbbb840790e60608c9fd42ad49810aad4452fb51291fd00e83120ca13567059ac90cb3716ab516b9ad2d80d5fe7d0877d596a37dc9faba898ff2bc20&user=tezza.lantika%40evermos.com)”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)  
ORIGINAL STACK TRACE:  
[github.com/pritunl/pritunl-zero/auth.GoogleSync](http://github.com/pritunl/pritunl-zero/auth.GoogleSync)  
/go/src/github.com/pritunl/pritunl-zero/auth/google.go:193 +0x13c1ac5  
[github.com/pritunl/pritunl-zero/auth.SyncUser](http://github.com/pritunl/pritunl-zero/auth.SyncUser)  
/go/src/github.com/pritunl/pritunl-zero/auth/sync.go:39 +0x13c7338  
[github.com/pritunl/pritunl-zero/proxy.(\*Proxy).ServeHTTP](http://github.com/pritunl/pritunl-zero/proxy.(*Proxy).ServeHTTP)  
/go/src/github.com/pritunl/pritunl-zero/proxy/proxy.go:206 +0x15aef69  
[github.com/pritunl/pritunl-zero/router.(\*Router).ServeHTTP](http://github.com/pritunl/pritunl-zero/router.(*Router).ServeHTTP)  
/go/src/github.com/pritunl/pritunl-zero/router/router.go:99 +0x15d5cd8  
net/http.serverHandler.ServeHTTP  
/usr/local/go/src/net/http/server.go:3210 +0x778bed  
net/http.(\*conn).serve  
/usr/local/go/src/net/http/server.go:2092 +0x75810f  
runtime.goexit  
/usr/local/go/src/runtime/asm\_amd64.s:1700 +0x4799e0

Can you explain?

---

<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:** [July 16, 2025, 9:49am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/2 "2025-07-16T09:49:47Z")

</div>

I also has the same problem with pritunl

---

<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:** [July 16, 2025, 9:51am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/3 "2025-07-16T09:51:22Z")

</div>

There is currently an outage with access to Pritunl services and Google single sign-on isolated to the South Asia region.

Click subscription in the top right of the web console to trigger a refresh, there are reports it is working again.

---

<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:** [July 16, 2025, 9:53am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/4 "2025-07-16T09:53:14Z")

</div>

![Screenshot 2568-07-16 at 16.52.39](https://forum-static.pritunl.com/optimized/2X/4/4e19e4a2475fa0c3a53cd592f23348ca2d8f1b9e_2_690x33.png)  
My subscription button’s also gone and revery back to free version

---

<div class="post-metadata">

**Author:** ![ariretiarno](https://forum.pritunl.com/user_avatar/forum.pritunl.com/ariretiarno/32/517_2.png) [@ariretiarno](https://forum.pritunl.com/u/ariretiarno)\
**Post date:** [July 16, 2025, 10:00am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/5 "2025-07-16T10:00:08Z")

</div>

Failed to sync Subscription @zach  
the license is gone

---

<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:** [July 16, 2025, 10:00am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/6 "2025-07-16T10:00:33Z")

</div>

There has been no increase in errors on the Pritunl service systems. The issue is entirely related to a connection between South Asia and the US East datacenter that the Pritunl services are running in. It appears to be isolated specifically to AWS. I haven’t seen any reports outside of the South Asia AWS region and the status checking system has checking in the South Asia region which has reported no issues.

---

<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:** [July 16, 2025, 10:10am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/7 "2025-07-16T10:10:27Z")

</div>

Are there any workaround for this?  
I’ve create local user without sso, It can’t connect either

---

<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:** [July 16, 2025, 10:32am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/8 "2025-07-16T10:32:33Z")

</div>

It’s now stable on the ap-south-1 instance that I’m testing with and I’ve seen several reports it is working now. Click subscription in the top right to refresh the license.

---

<div class="post-metadata">

**Author:** ![mohijeet-changejar](https://forum.pritunl.com/user_avatar/forum.pritunl.com/mohijeet-changejar/32/1133_2.png) [@mohijeet-changejar](https://forum.pritunl.com/u/mohijeet-changejar)\
**Post date:** [July 16, 2025, 10:34am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/9 "2025-07-16T10:34:27Z")

</div>

> [@zach](#):
>

We also face same issue in both pritunl-zero and pritunl-vpn even subscription button was not working network tab showing pending…though now it seems working as expected

---

<div class="post-metadata">

**Author:** ![shreyank](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/s/7feea3/32.png) [@shreyank](https://forum.pritunl.com/u/shreyank)\
**Post date:** [July 16, 2025, 10:37am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/10 "2025-07-16T10:37:25Z")

</div>

We are facing the same issue in both pritunl and pritunl zero. Still it’s not fixed  
region: ap-south-1

```auto
retries exceeded with url: /subscription (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9ce04f9ee0>, 'Connection to app.pritunl.com timed out. (connect timeout=20)'))

```

---

<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:** [July 16, 2025, 10:39am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/11 "2025-07-16T10:39:20Z")

</div>

What I did as work around is I’ve to create new set of user/server since current user in system already has group and sso enabled.  
That’d at least allow user who really need to connect to vpn to be able to connect while waiting for sso to be recover

---

<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:** [July 16, 2025, 10:39am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/12 "2025-07-16T10:39:26Z")

</div>

Where is the server located?

---

<div class="post-metadata">

**Author:** ![mohijeet-changejar](https://forum.pritunl.com/user_avatar/forum.pritunl.com/mohijeet-changejar/32/1133_2.png) [@mohijeet-changejar](https://forum.pritunl.com/u/mohijeet-changejar)\
**Post date:** [July 16, 2025, 10:40am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/13 "2025-07-16T10:40:39Z")

</div>

> [@witoon](#):
>
> That’d at least allow user who really need to connect to vpn to be able to connect while waiting for sso to be recover

AP-SOUTH-1

---

<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:** [July 16, 2025, 10:41am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/14 "2025-07-16T10:41:00Z")

</div>

You can also try adding the IPs below to `/etc/hosts` I created a second load balancer as it appeared to be isolated to a specific set of IPs on Oracle Cloud. The [app4.pritunl.com](http://app4.pritunl.com) server remained available the entire time despite also being hosted on Oracle Cloud.

```auto
129.80.151.180 app.pritunl.com
129.80.151.180 auth.pritunl.com

```

---

<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:** [July 16, 2025, 10:42am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/15 "2025-07-16T10:42:24Z")

</div>

Which availability zone in ap-south-1? I have a test instance in ap-south-1a with no issues connecting.

---

<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:** [July 16, 2025, 10:43am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/16 "2025-07-16T10:43:25Z")

</div>

ap-southeast-1

---

<div class="post-metadata">

**Author:** ![abhinav-kumar3](https://forum.pritunl.com/user_avatar/forum.pritunl.com/abhinav-kumar3/32/1305_2.png) [@abhinav-kumar3](https://forum.pritunl.com/u/abhinav-kumar3)\
**Post date:** [July 16, 2025, 10:43am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/17 "2025-07-16T10:43:29Z")

</div>

Subscription is working for me now, but the users are still not able to connect to pritunl via client

In logs i can see

```auto
[WARNING] Message queue flood
  size = 144

```

Server is in ap-south-1a

---

<div class="post-metadata">

**Author:** ![mohijeet-changejar](https://forum.pritunl.com/user_avatar/forum.pritunl.com/mohijeet-changejar/32/1133_2.png) [@mohijeet-changejar](https://forum.pritunl.com/u/mohijeet-changejar)\
**Post date:** [July 16, 2025, 10:44am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/18 "2025-07-16T10:44:54Z")

</div>

Sharing new profile link might solve this issue there are few users who facing this issue in our org simply sharing profile link seems working

---

<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:** [July 16, 2025, 10:46am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/19 "2025-07-16T10:46:42Z")

</div>

You should not attempt to reimport VPN profiles or make any configuration changes unless it is continuing to have issues. It may cause other issues and won’t fix this issue. Most users are now reporting it is online.

---

<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:** [July 16, 2025, 10:51am UTC](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424/20 "2025-07-16T10:51:05Z")

</div>

> [@zach](#):
>
> eimport VPN profiles or make any configuration changes. It may cause other issues and won’t fix this issue. Most users are now reporting it is online.

Some of our server is working, however few server still having issue with below log

[2025-07-16 17:48:37][WARN] ▶ profile: Request ovpn connection error  
profile: Request put error  
Post “[https://None/key/ovpn/](https://None/key/ovpn/)[redacted somelong number]”: dial tcp: lookup None: no such host

[Next page](https://forum.pritunl.com/t/pritunl-zero-crash-auth-google-request-failed/3424.md?page=2)
