Clash Verge Rev: ambiguous nodes are grey

On the Clash Verge Rev nodes page, record the ambiguous message, grayed-out entries that cannot be selected, or tests that correspond to a node from another source. Then check whether these nodes come from multiple proxy providers and share the same name.

The official v2.5.8 release, published on 10/9/2026, explicitly fixes both problems. Older-version users in issue #8021 reported nodes they could not select while existing connections still worked. That report does not explain every greyed-out node or establish that every older version and platform is affected.

Look for multiple proxy-providers in the runtime configuration, duplicate node names across sources and differences in the interface or tests. If a collection is not loaded, a node is unavailable or configuration parsing fails, address that error first instead of calling every issue ambiguous.

Record the full client version, operating system, current Profile, affected group, and duplicate names. Compare the subscription with the running configuration: collection names under proxy-providers, node names in each collection, and the affected group's use list. Duplicate collection keys are a different configuration error that an upgrade cannot fix.

Also check include-all-providers, include-all, and exclude-type. In the fixed-version implementation, the first two include all collections, so use alone cannot be assumed to restrict sources. Type exclusions also change the candidate nodes. Without those conditions, compare against the group's own collection scope.

Confirm that the collections have loaded and really contain duplicate node names. Test the node and group separately against the same trusted address and record the results. Start a new HTTPS request with the original selection and inspect the connection log for the expected group and exit. A browser request that bypasses the proxy is not a valid comparison.

In Settings, open Backup Settings under Verge Advanced Settings. Create a local record under Manual Backup, then use View Records to export that pre-upgrade backup outside the application data directory. Labels may differ by interface language. Creating a local record alone does not give you a separate offline copy.

The official backup implementation includes regular files in profiles and application configuration; it is not an image of the entire data directory. Save external Provider files and other resources you manage separately. Keep subscription tokens, passwords, and original backups on your own device, rather than attaching them to public reports.

Do not delete a working subscription just because the interface looks wrong.

v2.5.8 looks up nodes in the Provider used by each proxy group, avoiding confusion with identically named nodes from other providers. This changes how the client associates group members with their sources. Use real connections to check whether two identically named outbounds within the same group can be selected separately; restored display alone is not proof.

Obtain v2.5.8 for your operating system and architecture from the official Release linked below and follow the project's normal upgrade procedure. Retain your configuration and exported backup. This site's archived client version and the latest upstream version are separate records; an older site backup cannot establish that this fix is installed.

If a group still contains identically named nodes from multiple collections, clickable entries do not establish independent selection of the second exit. In v2.5.8, the selection call still passes a group name and node name. Mark the result unconfirmed if evidence is insufficient; repeated latency tests or existing long-lived connections do not prove a switch.

If collections remain empty or show download or parse errors after upgrading, retain the first error and investigate their sources. If membership and selection are correct but a new request fails, check node connectivity, rules, and the test destination instead of attributing every failure to client mapping.

If upgrading restores the selection you need, no renaming is necessary. When two duplicate exits must be distinguished in the same group, use a locally managed configuration copy and set a different override.additional-prefix for each collection, such as A- and B-. This source prefix is officially supported by Mihomo; it does not modify the remote subscription service.

Merge additional-prefix into the collection's existing override, preserving its other fields. Explicit proxies references, name filters, scripts, and saved selections may still refer to old names and need checking together. Do not replace the whole override or treat A- and B- as universal values for every subscription.

Import the local copy normally under a distinct name and retain the original Profile. Check syntax, nodes, rules, and required customizations before briefly switching to verify the new names and actual exits. If you cannot determine how the running configuration or scripts are affected, stop renaming and retain redacted evidence for the maintainers.

If the copy fails, return to the original working Profile and restore application settings you actually changed. Prefixes in the copy do not automatically migrate to other subscriptions. Recheck the running configuration after subscription updates; one successful test is not a permanent guarantee.

If damaged configuration requires recovery, preserve the current data first. Import the exported pre-upgrade file into backup history, then select its record and run Restore Backup. Importing only adds a record; it does not apply it automatically. Recheck subscriptions, rules, proxy mode, and real requests after restoring.

Before rolling back the application, check backup compatibility and the official security advisory. Do not copy the issue user's suggestion to return to v2.5.2, especially for the Windows service: the advisory specifies affected versions and the patched build. Do not assume an older application can read a backup created by a newer one. Prefer restoring a verified working configuration.

If no configuration works, stop proxy interception normally and check ordinary network access. Pause tasks that require proxy access. Do not clear all data or disable security software as trial fixes, or bypass the official upgrade with an installer from another source.

If the problem persists, report the full version, operating system, redacted collection and group scope, duplicate-name relationships, individual and group tests, new-connection chain, and quit/restart results. Use consistent placeholders to preserve the structure; hide subscription credentials, personal addresses, and secret. Describe observed differences, without claiming an unverified exit selection is fixed.