Skip to content
View overnice2025's full-sized avatar

Block or report overnice2025

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
overnice2025/README.md

Proxy client troubleshooting references

Structured, version-checked references for the proxy clients people actually run into trouble with: Clash Verge Rev, Clash Meta / Mihomo, v2rayN, v2rayNG, Hiddify, sing-box, FlClash.

The point is not to collect error messages. It is to say which stage failed and what the shortest verifiable fix is — and to be explicit when a claim cannot be verified.


Repositories

20 exact error strings mapped to cause and fix, grouped by failure stage:

Stage Example error
Config parsing the remote profile data is invalid yaml
Service / IPC cannot select profile: socket error, service core IPC timeout
DNS set system dns failed: exit code 1
TUN / routing nftables operation not supported, exit status 127
Subscription import ArgumentOutOfRangeException, gzip import failure
TLS / transport allowInsecure has been removed

Each entry records the client, the platform, the version range where the error was observed, the upstream issue where one exists, and the evidence boundary — what was reproduced and what was not.

Ten clients compared on the fields that actually determine whether a fix applies to you: platform support, routing core, TUN implementation, rule system, configuration format, open or closed source, and pricing model.

Clash Verge Rev · FlClash · v2rayN · v2rayNG · Shadowrocket · Surge · Stash · sing-box · Hiddify · Karing

Why the same subscription URL imports cleanly in one client and silently loses half its nodes in another: base64 node lists vs Clash YAML vs sing-box JSON, the subscription-userinfo header, and the field mismatches that conversion tools drop without warning.


How these are maintained

  • Errors are quoted verbatim, not paraphrased, so they stay searchable and diffable.
  • Every entry states the client version it was observed on. Behaviour changes between releases; an entry without a version is treated as unverified.
  • Upstream issue numbers are linked when they exist, so the reader can check the maintainer's own explanation rather than trusting a blog post.
  • Corrections are welcome as issues or pull requests. If an entry is wrong for your version, say which version and what you saw.

Related

These repositories do not host subscriptions, node addresses, tokens or configuration files that can be connected directly.

Popular repositories Loading

  1. python-amazon python-amazon Public

    Python

  2. clash-error-codes clash-error-codes Public

    Clash Verge Rev, v2rayN, v2rayNG, Hiddify, sing-box, FlClash error codes and troubleshooting: set system dns failed, allowInsecure, invalid yaml, config.yaml empty, tun not working, core ipc pipe t…

  3. proxy-client-matrix proxy-client-matrix Public

    Proxy client comparison table: side-by-side comparison of 10 clients — Clash Verge Rev, FlClash, v2rayN, v2rayNG, Shadowrocket, Surge, Stash, sing-box, Hiddify, Karing. Platform, core, TUN rule sys…

  4. subscription-format-notes subscription-format-notes Public

    Clash subscription format notes: base64 node lists vs Clash YAML vs sing-box JSON, the subscription-userinfo header, and why conversion silently breaks nodes.

  5. overnice2025 overnice2025 Public

    Clash troubleshooting index: Clash Verge Rev, v2rayN, v2rayNG, Hiddify, sing-box, FlClash error codes with causes and fixes, plus client comparison and subscription format notes.

  6. clash-config-examples clash-config-examples Public

    Clash config examples for Clash Verge Rev, mihomo and sing-box: annotated config.yaml, sing-box config.json and Clash YAML profile files with every field explained — DNS, TUN, rule providers, proxy…