Pritunl Zero Crash auth: Google request failed

Hello @zach our zero trust pritunl is going down because of this
[2025-07-16 09:20:32][ERRO] :play_button: 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”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
ORIGINAL STACK TRACE:
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
/go/src/github.com/pritunl/pritunl-zero/auth/sync.go:39 +0x13c7338
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
/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] :play_button: 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”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)
ORIGINAL STACK TRACE:
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
/go/src/github.com/pritunl/pritunl-zero/auth/sync.go:39 +0x13c7338
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
/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?

I also has the same problem with pritunl

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.

Screenshot 2568-07-16 at 16.52.39
My subscription button’s also gone and revery back to free version

Failed to sync Subscription @zach
the license is gone

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.

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

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.

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

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

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

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

Where is the server located?

AP-SOUTH-1

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 server remained available the entire time despite also being hosted on Oracle Cloud.

129.80.151.180 app.pritunl.com
129.80.151.180 auth.pritunl.com

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

ap-southeast-1

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

In logs i can see

[WARNING] Message queue flood
  size = 144

Server is in ap-south-1a

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

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.

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

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