How to set up ErrorX on macOS
Install ErrorX on Apple Silicon or Intel — with Homebrew or the DMG — sign in with your account, and get a system-wide encrypted tunnel running in about five minutes.
What you need
- A Mac with Apple Silicon or an Intel processor
- An administrator account on the machine
- An active ErrorX subscription
- About 200 MB of free disk space
- Homebrew, if you prefer installing from the terminal
- A Google, Facebook or Discord account to sign in with
Install with Homebrew, or take the DMG
If you use Homebrew, two commands install ErrorX and keep it updatable from the terminal — the tap is refreshed automatically on every stable release. Otherwise download the DMG from our download page: take the Apple Silicon build for any M-series Mac, or the Intel build for anything older.
brew tap FakeErrorX/tap
brew install --cask errorxMove it to Applications
If you used the DMG, open it and drag ErrorX into your Applications folder, then eject the disk image. Homebrew does this for you. Launching from inside the mounted DMG appears to work but breaks on the next update, so do not skip the drag.
Open it and get past Gatekeeper
Launch ErrorX from Applications. If macOS says it cannot verify the developer, close the dialog, then right-click the app icon and choose Open — the second dialog has an Open button that the first one does not. You only have to do this once per installed version.
Sign in through your browser
Press Continue with ErrorX. Your default browser opens the ErrorX login page; sign in with Google, Facebook or Discord and the browser hands you straight back to the app. There is no password form inside the app.
Approve the tunnel with your Mac password
The first time you press Start, macOS asks for your administrator password through its own dialog. That grants the ErrorX core the one permission it needs to create a network interface — nothing is installed system-wide and no kernel extension is loaded.
Connect and leave it on Rule
Press Start. The app pulls your encrypted config, claims a device slot and brings the tunnel up. Rule mode is the default and the right choice: international traffic goes through ErrorX while local and cached destinations stay on the direct path, where they were already fast.
Check that it actually helped
Test against something genuinely international — a BDIX speed test was already fast and will tell you nothing.
- Note your download speed from a cloud or GitHub target before connecting
- Connect, then run exactly the same test again
- Compare the two numbers — that difference is what you are paying for
- Your dashboard shows the device as online while the tunnel is up
If something goes wrong
- "ErrorX cannot be opened because the developer cannot be verified"
- Close the dialog, right-click the app in Applications and choose Open. The dialog you get that way has an Open button. Alternatively, allow it under System Settings → Privacy & Security.
- It asks for my password again after an update
- Expected. The permission that lets ErrorX create a network interface belongs to the specific binary, and an update replaces that binary. One prompt per update.
- The tunnel connects but nothing loads
- Switch to Direct mode to confirm your underlying connection works, then back to Rule. If it only fails in Rule mode, send us a message with your ISP name — it is usually a DNS setting we can fix from our side.
- The app says the device limit is reached
- Every slot on your plan is held by a device that is online right now. Stop ErrorX elsewhere, or disconnect that device from Dashboard → Subscription, then press Start again.
Stuck on a step?
Send us a message with the step number and what you saw — that is usually enough for us to tell you exactly what happened.