Failed to obtain access token-local

Support
1

image
image793×370 8.41 KB

Issue Summary

I am unable to log in to my Local account on the desktop app. Every time I click “Log in to Local”, it opens the browser, but then redirects back with the attached error

This means I cannot use the Live Link feature at all.

What I Have Already Tried:

  • Cleared Local’s app data folders (blob_storage, Local Storage, Session Storage, DIPS, Local State, lockfile) from C:\Users\[username]\AppData\Roaming\Local
  • Fully uninstalled and reinstalled Local (clean install, deleting all leftover folders)
  • Ran Local as Administrator
  • No VPN or ad blockers in use
  • Tried multiple browsers as default browser

By changing my wifi connection. I was briefly able to log in, but received a new error:
“Could not start Live Link — ApolloError: request to https://hub.localwp.com/api/ failed, reason: unable to verify the first certificate”

After trusting the SSL certificate, the login session was lost again and I’m back to the original “Failed to obtain access token” error.

System Details:

  • OS: Windows

  • Local Version: Latest (freshly installed)

  • Browser used for OAuth: Chrome

  • No VPN or firewall blocking confirmed

    image
    image263×312 7.5 KB

Expected Behaviour:
Clicking “Log in to Local” should complete the OAuth flow and keep me logged in so I can use Live Link.

Actual Behaviour:
Login either fails immediately with “Failed to obtain access token”, or logs in briefly and then loses the session after SSL trust step.

Please advise on a permanent fix. Please find the error log.

local-lightning.log (27.5 KB)

2

Is there anything else unique about your network connection @User006? Are you on a home network or at an office?

The errors in your log look like this:

{“eventId”:“4807af4e62be48c2aeabded1fab10555”,“level”:“warn”,“message”:“Unhandled Rejection.”,“p”:{},“reason”:{“message”:“Failed to obtain access token”,“name”:“InternalOAuthError”,“oauthError”:{“code”:“UNABLE_TO_VERIFY_LEAF_SIGNATURE”}},“thread”:“main”,“timestamp”:“2026-03-10T12:26:24.794Z”}

This means that the issue is likely still with the network connection preventing requests. So you might have to try another network. If you’re working in an office environment or using any kind of employer network/proxy they might have additional security in place. If you’re trying with something like a phone hotspot then the connection might not be strong/stable enough.

3

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