Three kinds of update, three different jobs
Manual update is the button on the card: it pulls once, right now. Automatic update runs in the background on the interval you set. Forced update ignores the local cache and pulls a complete fresh copy. Use it when the provider clearly changed something and you still see the old nodes.
The remaining traffic and the expiry date on the card are not calculated by the client. The provider sends them in a response header along with the file. When they are missing or disagree with the panel, the provider either did not send them or used a nonstandard format.
Do not delete the card over a failed update
Deleting means hunting down the link again, while the old copy on disk still works. Find the cause first; re-importing is the last step.
Set the interval, then pick the route
- 1
The interval counts in minutes
Open the edit dialog on the card. The update interval field counts minutes, so 1440 means once a day. Single digit values are pointless and a reliable way to get rate limited. Once a day to once every few hours covers how often providers actually change nodes.
- 2
Direct, or through the proxy
Clash Verge can fetch the file directly or send the request through the active proxy. If the subscription domain does not open on your network, the update has to go through the proxy or it will sit there until it times out.
- 3
Switch back to direct when every node is down
Updating through the proxy only works while the proxy works. With all nodes dead that route becomes a loop: put the update back on direct, pull the new file, then set it back.
Check whether your chosen node survived
A node you picked by hand normally survives an update, as long as the group name and the node name are unchanged. Rename the group or retire that node and the selection has nothing to point at, so the group falls back to its first entry. That is what people mean when the speed changes after an update.
- The update timestamp reads a moment ago, so a new file did arrive
- The node count matches what the provider panel shows
- Your main exit group still holds your node, not the first one in the list
Common questions
The expiry date is missing or wrong. What can I do?
First check that the provider sends it at all; plenty of cheap plans never return that header. Some return it only for a specific User Agent, so change the User Agent in the edit dialog and update again. If nothing brings it back, trust the number in the provider panel.
Half the nodes disappeared after an update. Did the client lose them?
The client does not drop nodes selectively. Either the provider changed the plan or retired some lines, or this pull returned a truncated file. Run a forced update, compare the count against the panel, and if it is still short the answer is on the provider side.