If one proxy group opens empty, people often jump to "subscription dead" or "reinstall." More often the subscription still has nodes, and filters, group refs, or group type emptied that one group. Don’t wipe the whole profile first.
Check the subscription card’s total node count. If it’s already 0, follow no nodes and update failed. If the pool has nodes but one group is blank, keep reading.
Five checks that usually locate it
- Manually refresh the subscription and wait.
- Confirm the overall proxy list shows nodes (the pool, not one group).
- Turn off region/keyword filters and reopen the blank group.
- Note whether it’s a select group or url-test/fallback.
- Any core communication errors? See core communication.
If disabling filters fills the group, the subscription is fine—tighten filters later. Latency testing hits the same trap: node latency.
Filters vs wrong names
Filters are obvious: off = full again. Wrong names are quieter—Merge or local edits pointing proxies / use / provider names at something that doesn’t exist. Reload after one change. See Merge rules.
With proxy-providers, groups must reference the provider name, not an imagined node label. Mix that up and you get "icon present, list missing."
Why url-test / fallback can look empty
Auto groups may stay blank briefly while health checks run. If they stay empty, check member lists, test URL reachability, and odd intervals. Don’t treat "testing" as permanent failure.
Broken chain or load-balance setups can also look unselectable. See chain proxy. Fall back to a simple select group to prove the subscription is healthy.
Scripts, profiles, fresh updates
Scripts that rewrite proxy-groups can delete groups—disable and compare (scripts). On multi-profile setups, blank may belong only to the current profile. After a refresh, switch tabs or reload before assuming failure; then check logs.
Latency numbers exist but the group looks empty
Try another list view, maximize, or restart. Watch for a second old process holding ports (ports). If only one subscription’s groups are empty, refresh that card alone.
When routing looks broken too
With no selectable nodes, perfect rules still go nowhere. Restore the group first, then revisit routing rules. Before reset, back up URLs and Merge (config location, backup).
Done when
Pool > 0; the group expands and selects; connection page reacts to switches; filters no longer empty the group. Reinstall is rarely required.
Symptom-to-check table
| Symptom | First check |
|---|---|
| One group blank, pool has nodes | Turn off filters, reopen |
| Group icon present, list missing | Provider name reference wrong |
| Auto group empty briefly | Wait for health check to finish |
| Only after a script edit | Disable script, compare |