# Extension sign-in (/docs/troubleshooting/sign-in)



Extension sign-in uses a short-lived authorization request tied to the browser that started it. The
extension exchanges that approval without exposing an account token in the popup.

## Approval completed but the extension still says Sign in [#approval-completed-but-the-extension-still-says-sign-in]

1. Reopen the extension after the approval window closes.
2. Wait a moment for the pending authorization to resume.
3. Confirm you approved access in the same browser profile where the extension is installed.
4. Confirm the extension and website are for the same environment.
5. Retry sign-in once from a newly opened popup.

## The browser could not complete sign-in [#the-browser-could-not-complete-sign-in]

Check that popups are allowed for the eReader Relay site and that privacy software did not block the
authorization window or callback. Do not switch browser profiles or private browsing modes halfway
through approval.

## Access was denied [#access-was-denied]

Start again and choose **Allow extension** only if you want this browser profile connected. A denied
request does not sign the extension in.

## The approval expired or state did not match [#the-approval-expired-or-state-did-not-match]

Close old approval tabs and start a new sign-in from the extension. This protects against reusing or
mixing authorization attempts.

## Storage is unavailable [#storage-is-unavailable]

The browser must allow extension-local storage so the authorization can survive popup closure. Check
browser policies, privacy settings, and whether the extension is permitted in the current profile.

## What to report [#what-to-report]

Include the browser and version, extension version/build environment, approximate time with time zone,
and exact visible message. Do not include the authorization code, access token, cookies, or full
callback URL.