Skip to main content

Troubleshooting Sign-In

When social sign-in hangs, returns to the welcome screen, or the core logs an unauthorized /auth request, use this checklist.

Check Backend Reachability​

From the same network as the desktop app, verify the public OpenHuman endpoints:

curl -I https://tinyhumans.ai/
curl -I https://api.tinyhumans.ai/health

If the website loads but the API endpoint fails, the desktop app may not be able to exchange OAuth callbacks for a session.

Check the Selected Core​

If using Advanced remote core mode, confirm both the RPC URL and bearer token before starting OAuth:

curl -sS https://your-core.example/rpc \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer CORE_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"core.ping","params":{}}'

A 401 response means the desktop token and remote core token do not match. Fix this first before retrying Google or GitHub sign-in.

Successful desktop OAuth ends with an openhuman://auth?... callback. If the browser shows that URL but the app stays on the welcome screen:

  1. Ensure only one OpenHuman desktop instance is running
  2. Restart the app, keep the same remote core settings, and retry sign-in
  3. If using a remote core, check whether the core receives openhuman.auth_store_session

For remote cores, temporarily manual-injecting can confirm whether the core is functioning:

curl -sS https://your-core.example/rpc \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer CORE_TOKEN" \
  -d '{"jsonrpc":"2.0","id":1,"method":"openhuman.auth_store_session","params":{"token":"JWT_FROM_CALLBACK"} }'

What to Include in a Bug Report​

In your bug report, include:

  • App version and OS
  • Whether the core mode is local or remote
  • RPC URL host, redacted token status, and core.ping result
  • OAuth provider used
  • Whether an openhuman://auth URL appeared in the browser
  • The first unauthorized log line (if any)

Next Steps​