GUIDE
Vinipuch will not connect: checklist — profile, client, OS permission
Published: 2026-09-20 · Updated: 2026-09-20
If access does not come up, separate three causes: no active access, the client did not pull the remote profile, or the system did not grant the network-configuration permission. Refresh the Connect link, confirm official SFI, SFA, SFW, SFM or SFL, and toggle the profile. The checklist does not promise a fix and does not teach how to evade network limits. If the steps fail, write to the support bot without tokens or cookies.
Separate it first: no access, no profile, no OS permission
“It does not work” is several symptoms. No active trial, promo or plan — the client is not the cause. A stale profile — the client still has old contents. No system permission — the tunnel never starts.
This page expands the short checklist in Getting started. We do not invent OS error codes: read what the client shows.
Five-minute checklist — order matters
Go top to bottom. Do not skip access just to reinstall the app.
Access is on: trial, plan, traffic
In the bot or cabinet, check that access is on. Trial and promo length is shown before activation — we do not freeze a duration here. Device limit and quota are on the plan card: Economy, Standard, Comfort or Premium. If the period traffic ran out, buy extra in the bot or cabinet; that is not an import bug.
Refresh the remote profile via Connect
Open Connect again and re-add the link as Remote. When the server changes the URL often stays, the contents update. A file you saved by hand goes stale fast.
Official client SFI / SFA / SFW / SFM / SFL
iPhone — SFI from the App Store, listing “sing-box MT”. Android — SFA from Google Play or the APK on the download page. Windows — SFW, macOS — SFM (Universal pkg or Homebrew; it is no longer on the Mac App Store), Linux — SFL. Third-party shells are not recommended and not supported.
OS permission for network configuration
The system asks once. Without it the profile exists and the tunnel does not. Go back to the client and accept the prompt if it is still there.
Toggle the profile
Turn it off, wait a few seconds, turn it on. Do not edit JSON by hand.
Common mistakes by platform
Typical user-side causes. Not an OS error catalog and not a rebuild of the core.
iPhone and iPad — SFI
Confirm the app is SFI from the App Store, not a random shell. If permission never appeared, delete the profile in the client, add the link again and wait for the system dialog.
Android — SFA
Install SFA from Google Play or the APK on the Vinipuch download page. A random APK from chat is unsupported. After refreshing the profile, restart the client.
Windows, macOS, Linux — SFW, SFM, SFL
macOS: SFM is the pkg or Homebrew, not the Mac App Store. If the client hangs after a server change, refresh the Remote link instead of grabbing another installer. A last user-side step is reinstalling the official package for that platform, not a third-party shell.
What not to do
A short stop-list so the ticket does not get worse.
Do not install random shells
The official path is the Vinipuch download page. A shell from chat adds foreign code and drops official support.
Do not send secrets to support
Do not send tokens, login cookies or wallet secrets. Device, client, time, expected versus actual is enough.
Do not edit the config from a chat “guide”
Hand-edited JSON and “evasion recipes” are out of scope here. The managed path is the Remote profile from Connect.
When to write to support and what to attach
If the checklist is done and access still does not come up, message the support bot. Include device and client (SFI, SFA, SFW, SFM or SFL), approximate time, expected versus actual, a screenshot if needed.
If the question is “you charged me and it does not work”: auto-renew is opt-in from balance only, never from the card. Cash refunds are not available; see the refund policy.
Related guides
Start and import live in Getting started. Why official client only lives in the sing-box explainer. If a bank or local app breaks while the tunnel is up, see profile routing. Payments and plans live in the payment explainer and on the pricing page.
Short answers
Must the checklist always fix it?
No. It is a user-side order of checks, not a guarantee. If it fails, write to support without secrets.
Can a third-party shell fix this?
Not as a supported path. Install the official client from the download page.
Do I need a new link every time the server changes?
Often it is enough to open Connect and refresh the same Remote profile: the URL may stay, the contents update.
Is this just exhausted traffic?
Sometimes. Check the quota in the bot or cabinet and the plan card. Buying extra traffic is a separate action, not an import repair.