How to set up ErrorX on Linux
Install ErrorX from a .deb, .rpm or AppImage on any GTK desktop. Two libraries to install first, one sudo prompt, and you are connected.
What you need
- A GTK-based desktop environment
- libayatana-appindicator3 and libkeybinder-3.0
- amd64, or arm64 with the .deb package
- sudo access on the machine
- An active ErrorX subscription
- A Google, Facebook or Discord account to sign in with
Install the two required libraries first
ErrorX needs libayatana-appindicator3 for its tray icon and libkeybinder-3.0 for global hotkeys. The .deb package pulls them in automatically, but AppImage and RPM users must install them by hand — the app will not start without both.
# Debian / Ubuntu / Mint
sudo apt-get install libayatana-appindicator3-dev libkeybinder-3.0-dev
# Fedora
sudo dnf install libayatana-appindicator-gtk3-devel keybinder3-develPick the package for your distribution
Download from the ErrorX download page. Use the .deb on Debian, Ubuntu and derivatives; the .rpm on Fedora, RHEL and openSUSE; and the AppImage anywhere else. All three are built for amd64, and .deb is also available for arm64.
# Debian / Ubuntu
sudo dpkg -i ErrorX-*-linux-amd64.deb
# Fedora / RHEL / openSUSE
sudo rpm -i ErrorX-*-linux-amd64.rpm
# Anything else
chmod +x ErrorX-*-linux-amd64.AppImage
./ErrorX-*-linux-amd64.AppImageLaunch ErrorX
Start it from your application menu, or run `errorx` in a terminal if you installed the .deb or .rpm. The AppImage runs directly from wherever you saved it — no installation step and nothing written outside your home directory.
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 it hands you back to the app. If clicking the return link does nothing, quit ErrorX completely and click the link again — see the troubleshooting note below.
Authorise the tunnel with sudo
The first time you press Start, ErrorX asks for your sudo password in a dialog. That grants its core the one permission it needs to create a network interface. Nothing is installed as a system service and no daemon is left running when you quit.
Connect and leave it on Rule
Press Start. The app fetches your encrypted config, claims one of your device slots and brings the tunnel up. Rule mode routes international traffic through ErrorX and leaves Bangladeshi and locally cached destinations on the direct path, which is faster than tunnelling them.
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
- The app does not start at all, with no window and no error
- One of the two required libraries is missing. Install both packages from step 1 and try again — this accounts for most Linux launch failures.
- Clicking the sign-in link in the browser does nothing
- A known limitation: the link cannot reach an ErrorX window that is already open. Quit ErrorX completely, then click the link — it will start the app and complete the sign-in.
- The AppImage will not run
- Make sure it is executable with `chmod +x`, and that FUSE is available — on Ubuntu that means the libfuse2 package. Failing that, use the .deb instead.
- No tray icon on GNOME
- GNOME removed built-in tray support. Install the AppIndicator extension, or use the app window directly — the tray is a convenience, not a requirement.
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.