Troubleshooting Guide for Auto-Identification

This page helps troubleshoot issues encountered when clicking Auto-Identify in the plugin's "Add/Edit Account" section, such as: excessively long identification time, infinite waiting, identification failure (401/403/format errors, etc.), and inability to submit.

Excessively Long Identification Time (Stuck on "Identifying...")

Auto-identification requires opening a temporary page and reading site information. It will noticeably slow down in the following situations:

Site has Cloudflare / Firewall verification enabled: Please check if a temporary window pops up; if manual verification is required, please complete it before timeout.
Slow network/site response: It is recommended to wait a moment, or switch networks/proxies and retry.
Permissions/Browser anomaly: If you just granted optional permissions and started experiencing "infinite waiting", see "Infinite Waiting After Granting Optional Permissions" below.

Infinite Waiting After Granting Optional Permissions

After initially granting optional permissions, identifying some sites might get stuck in auto-identification, appearing as a continuously loading interface:

Solution: First, click Reload extension and retry in the slow identification prompt. After confirmation, allow the plugin to reload its runtime, then perform identification again. If the prompt does not appear or the issue persists after reloading, open the browser extension management page, disable then re-enable this extension, or restart the browser and retry identification/authorization.
For the purpose and explanation of optional permissions, see: /permissions (Permission Management).

Identification Failed: First, Confirm You Are Indeed Logged In

Auto-identification relies on you being logged into the target site in the same browser:

First, open the target site's backend (console) page in your browser.
Confirm that you are not redirected back to the login page (refresh the page to verify).
Then return to the plugin and perform auto-identification.

Identification Failed: Try Switching Authentication Methods

Different sites/modified versions handle interfaces and login states differently. When identification fails, prioritize trying to switch authentication methods:

Access Token authentication failed: Switch to Cookie authentication and auto-identify again.
AnyRouter: Must use Cookie authentication, and the Cookie must come from the currently logged-in account; Cookie authentication does not support multiple accounts on the same site simultaneously.

Unable to Submit / Unable to Save: Check Required Fields Item by Item

When required fields are missing, the submit button is disabled or saving fails. Requirements vary by site, so confirm the site type first and check the corresponding fields:

New API and compatible sites: Check the Site Name, Username, User ID, Access Token, and a Recharge Amount Ratio greater than 0. When using Cookie authentication, import or enter the Session Cookie (Header Value).
Sub2API: Check the Site Name, User ID, JWT Access Token, and Recharge Amount Ratio. Cookie authentication is not supported. When "Extension-managed session (multiple accounts)" is enabled, you must also import or enter a Refresh Token.
OpenRouter: Check the Site Name, OpenRouter Management Key, and Recharge Amount Ratio. A User ID is not required, and Cookie authentication is not supported.
Other sites: Follow the required markers currently shown in the form and the corresponding site instructions in the Manual Account Addition Guide.

Last Resort: Manually Add Account

If auto-identification consistently fails, you can switch to Manual Addition, complete the information, and then save the account.

See the Manual Account Addition Guide for details.