DEV Community

qnca zzlx
qnca zzlx

Posted on

I got tired of debugging the same proxy issues — so I wrote a production guide

The problem

Every week, friends and strangers ask the same questions in DMs and forums:

  • "TUN mode works in the browser but not in the terminal, help?"
  • "Why does this DNS leak test show my real IP?"
  • "How do I get ChatGPT to go through the proxy automatically?"

I'd answer, and a month later someone else would ask the same thing. It was a huge time sink.

What I did

I started writing down every fix I'd verified in production. Not another client, just a structured configuration guide for Mihomo (Clash Verge Rev).

That became Clash Verge Rev Omni Guide.

What's inside

  • TUN mode that actually works — covers UDP, Docker, and games
  • DNS leak-proof setup — Fake-IP + DoH/DoT with a clear fallback for domestic sites
  • AI site auto-proxy — rules for ChatGPT, Claude, Gemini, etc., out of the box
  • GitHub Actions auto-update — fresh subscriptions and rule sets every day, zero manual work
  • Performance tuning — Mihomo optimizations that make a difference

Everything is a wiki page, so you can jump straight to the part you need.

How it works

The guide is pure documentation and config templates — no binary, no API keys, no dashboard. You drop the templates into your profile folder, adjust your subscription info, and start the core.

The full wiki covers each topic with step-by-step instructions and troubleshooting FAQs.

Try it

If you're maintaining a proxy setup and spending too much time debugging, have a look.

I'd love to know: what's one proxy issue you keep running into that never seems to have a clear answer? Drop a comment — I might add it to the wiki next.


Repo: github.com/clash-verge2026/clash-verge-rev-omni-guide

Top comments (0)