ByeByeDPI support: help yourself first, then ask well
This site is a guide, not a helpdesk — but support works best in a particular order, and this page is that order. Most problems die at step one or two.
Step 1 — Match your symptom to a guide
Nothing works / still blocked
The troubleshooting guide diagnoses by failure shape: plumbing errors, a filter beating your settings, or a block that is not DPI.
It runs, but a site stays blocked
The settings ladder: position first, method second, fake third, auto mode last.
Browser ignores ByeDPI
SOCKS5, 127.0.0.1, 1080 — the proxy setup guide for Firefox, Chrome and system settings.
A quick question, not a problem
VPN or not, root or not, free or not, macOS or not — the FAQ answers in one paragraph each.
Step 2 — Check you have the real, current thing
Update from the official download page before asking anyone anything. A large share of support threads, in our reading of the project's discussions, involve old builds or unofficial repacks; both are fixed by the same reinstall from GitHub, and no volunteer can help debug a file whose origin is unknown.
Step 3 — Ask the project, with a report that can be answered
The developers and experienced users are on GitHub. For the Android app, use the ByeDPIAndroid repository — its README points to its discussions for configuration help. For the desktop core, use the byedpi repository and its issue tracker. Include: your platform and version of the tool, your provider, the exact command or app settings used, the site category that fails (not necessarily the site), and which failure shape from the troubleshooting guide you see. Reports written that way are the ones that receive working answers.
Contacting this site
For corrections to anything published here — a wrong setting, a stale claim, a broken link — the route is the contact page. We correct factual errors openly and note significant changes; our approach is described on the about page. Please do not send us your provider passwords, your traffic, or requests to unblock a specific service for you: we cannot, and we would not keep them if we could.