Which layer the error belongs to
| Observation | What it establishes | Next step |
|---|---|---|
| The message appears immediately on import, with no HTTP status or download log | The input value, the entry type or the pasted content is the first suspect; the server has not been reached | Check scheme prefix, spaces, line breaks and content type |
A client error(Connect) or a timeout appears | The client attempted a network connection; this is a different failure from instant URL validation | Check network, source and certificates against the update-failure path |
| The address returns 401, 403, 404, or downloads a login page | The remote endpoint responded, but authorisation, path or body may not be usable | Confirm the address and permissions with the provider; never publish the token |
| The file imported but the proxy list is empty | You are now in parsing, activation or provider state | Use the “update succeeded, no nodes” path; stop blaming the URL prefix |
Step 1: inspect the input locally
Paste the address into a local plain-text editor and look only at the beginning and the end. Do not post it in a group or an online checker. A remote subscription URL should begin with http:// or https:// and be a complete address on a single line.
- A leading quote, space or sentence of explanation.
- A trailing line break, full stop or Markdown bracket picked up with the copy.
- A “copy subscription” button that actually copied a label or a help page URL.
- A wrapped line in a chat app that split the address into two.
A string that looks like a link is not automatically a valid subscription. Passing URL syntax is only the first gate; the server still has to return something the client can parse, which is the next stage. Treat the URL as a credential: keep the scheme, the domain and a masked path in your notes.
Step 2: choose the entry that matches the content
| What you have | Entry to use | Common mistake |
|---|---|---|
A full https://… subscription address | The remote subscription entry | Pasting it into a local-file entry, or pasting a file path into the URL field |
A .yaml file | Local configuration import | Assuming the file is a profile when it is actually an HTML error page saved with a .yaml name |
A single vless://, trojan:// or vmess:// URI | Not a remote subscription | Believing the client should accept a node URI as a subscription URL |
| A QR code or a chat message containing a config | Depends on what it decodes to | Treating the whole message as a URL |
The documentation lists remote subscription import, remote subscription configuration and URL scheme as separate remote methods, plus local configuration import. Interface names shift between versions, so match on behaviour rather than on a label you remember.
Step 3: one minimal contrast that leaks nothing
- Record the client version, the OS, the entry used and the exact error text.
- Confirm the first and last characters in a text editor, then re-copy the complete single-line address into the remote subscription entry.
- If the same address saves through one official entry while another rejects it instantly, keep that comparison and the client log. It shows the entries behave differently; it does not locate a code-level cause.
- If the import starts and then fails with a network or certificate error, move to the update-failure path. Do not disable certificate verification to get past an input message.
- After a successful save, confirm the profile card exists, is active, and lists nodes — then verify with an ordinary HTTPS page.
If the nodes themselves do not work
A failed node is not evidence that the URL input was wrong. Test one real HTTPS request; if it fails on every node, the profile may be valid while the nodes are expired or unreachable. Free nodes in particular can stop working within hours, and a healthy latency value does not prove an HTTPS request completes.
Evidence boundaries
Clash Verge Rev issue #8683 is a user report on 2.5.10 covering Windows and macOS, whose body states only that creating a new entry and placing the link in the subscription field works. It contains no masked original input, no complete reproduction and no log. Issue #8684 was closed as a duplicate or invalid with no fix version recorded. Nothing here should be read as “a particular button is definitely broken”, and none of it justifies changing the system proxy, reinstalling the client or clearing every subscription as a first step.
If you report it upstream
- Client and OS versions, and which entry you used.
- The exact instant error text.
- The masked structure of the URL: scheme, domain, path shape, whether it was a single line.
- What a different official entry did with the same address.
- Whether any HTTP status or download log appeared at all.
Remove the token, account identifiers and any query parameter that could authenticate before posting.