Browser extension
Fix missing destinations, inaccessible pages, stale state, and extension errors.
The popup closes during sign-in
This is normal browser behavior in some environments. Complete Allow extension, let the approval window close, then reopen the extension. The pending authorization should resume. If it still appears signed out, use Extension sign-in troubleshooting.
The extension cannot use the current page
Open a normal public http:// or https:// article tab and try again. Browsers do not give the
extension access to settings pages, extension pages, new-tab pages, local files, or other protected
surfaces.
If the extension cannot identify an active tab, focus the article tab before opening the popup.
A reading list is missing
Refresh or reopen the popup. Confirm the list still exists and belongs to the signed-in account. A stale locally remembered list is cleared when it no longer appears in the account's destinations.
A device is missing
Confirm it exists under Devices in the web app, then reopen the popup. The extension only offers devices belonging to the current account.
Every device is turned off
That can be intentional. The extension remembers an explicitly empty selection. Turn on one or more devices before Send EPUB. On first use only, a sole available device is selected automatically.
The page was added to the wrong list
The action button includes the selected list name, and the success view repeats it. Before submitting, confirm the selector and button refer to the intended list. Open the list from the success view to verify it. If necessary, select the correct list and add the page there.
Something went wrong or eReader Relay could not be reached
- Confirm the website is reachable in another tab.
- Confirm the extension build targets the same environment as the site: development with
dev.ereaderrelay.com, production with the production service. - Reopen the popup and retry once.
- If the session expired, sign in again.
- Record the time and visible error before reporting it.
Repeated retries do not help a policy refusal or unsupported page. Use Article capture troubleshooting when a reason code is shown.