Where the error sits
| What you see | Stage | First action |
|---|---|---|
| Timeout, TLS error or HTTP 401/403, before any content | Fetch failure | Use the general update path: address, authorisation, network |
Content received, then [SingboxParser] unmarshal error, outbounds[n] and unknown field "tunnel-per-resolver" | Content arrived; the current parser rejects a field | Keep a masked error, the version and the subscription type; ask the provider to check the output format |
| No parse error, profile imported, list empty | Display or selection stage | Use the updated-but-no-nodes path |
| Nodes appear, connection fails | Core start, node or network | Keep the earliest connection error; stop re-importing |
The index in outbounds[33] or outbounds[25] locates an entry in the configuration array. unknown field states only that the current parsing path does not accept that field. Neither message distinguishes a generator that emitted an inapplicable field, a client version that predates the field, or content altered in transit.
Two public reports
Hiddify issue #2295 documents Android 16 on Hiddify 4.1.1 importing a Hiddify Manager subscription and reporting outbounds[33].tunnel-per-resolver. Issue #2203 documents Windows 11 on 4.1.1 reporting a similar field error for a different subscription. Both are user reports, both are closed, and a closed state does not mean a general fix was published. This site does not have those private subscriptions and has not reproduced their configurations.
What the reports do establish is the shape of the failure: the subscription parsed far enough to reach a specific outbound object, and stopped there. That is why the useful next step is a format question to the provider, not a node question.
Handle it in order
- Protect the working configuration. Pause automatic updates and repeated retries. Note the OS, Hiddify version, subscription source type, the full error text and the time. Do not clear application data, and do not publish the subscription URL.
- Confirm this is a post-fetch parse error. If the log shows an HTTP, certificate, connection or permission error first, handle that instead. HTTP 200 can still return a login page, so check the content type as well.
- Check which entry the provider offers. See whether it distinguishes Hiddify, sing-box, Clash and generic links. Use the entry explicitly intended for this client rather than a web page, a QR redirect page, or another client's format.
- Inspect the structure locally if you are entitled to. With a local JSON/YAML parser, confirm that the field really appears near the reported
outbounds[n]. Keep the original file untouched — a field may interact with other settings, and an edited file is no longer the provider's output. - Ask the provider, with masked details. Field name, array position, client version, OS, entry type and time are enough for them to check whether their generator output suits this build. If they provide a corrected subscription, import it in parallel: confirm it parses, nodes appear, and a real HTTPS request succeeds, before replacing the old profile.
Why the field is a version question
tunnel-per-resolver is an outbound-level option in the sing-box configuration schema. A client that bundles an older parser will reject it; a generator that always emits the newest schema will produce it regardless of what the client can read. That combination is the ordinary cause of “the provider's config is valid but this client refuses it”, and it is resolved by aligning the format, not by editing nodes.
The sing-box outbound documentation is a reasonable reference for field types and structure. Hiddify's actual importer still follows its own version's implementation, so the documentation alone does not tell you which build accepts what.
After the parse succeeds
An import that no longer errors is step one. Continue by confirming the profile is saved and selected, the expected nodes appear, the core starts, and one HTTPS request to a site you can reach actually completes. If the profile exists but no nodes appear, move to the empty-list path. If nodes exist but traffic fails, move to the connection path — capture mode and real network state.
Scope and limits
- This applies only when the error explicitly contains
SingboxParserandunknown field "tunnel-per-resolver". - A misspelled
adress, a different unknown field, a fetch failure and post-connect breakage each need different handling. - This site has neither of the private configurations nor the server-side generators, so it cannot assert which side is defective, and it cannot promise that a version, a field edit or a specific provider entry resolves it.
- When asking publicly, mask the subscription URL, token, UUID, node servers and account identifiers.