Skip to content

Installation Linux

WePROXA 3.11.0 is the first release for Linux. It ships as a .deb package for Debian and Ubuntu and an .rpm package for Fedora, for both x86_64 and ARM64 computers. Linux support is a preview, so a few features are still missing. See Known Limitations.

  • A 64-bit x86_64 or ARM64 computer
  • glibc 2.35 or newer, such as Ubuntu 22.04 or later, Debian 12, or a current Fedora release
  • A graphical desktop. GNOME and KDE Plasma let WePROXA set the system proxy for you

Each release is tested on Ubuntu 22.04, Ubuntu 24.04, Debian 12, and Fedora.

Run this command in a terminal:

Terminal window
curl -fsSL https://weproxa.com/i | bash

The script picks the .deb or .rpm package for your computer and installs it with apt or dnf. It asks for your password, because it installs a system package. When it is done, it opens WePROXA.

If your system has no curl, install it first with sudo apt install curl.

Then trust the certificate before you inspect HTTPS, as step 3 of Install explains.

To download and install the package yourself, follow the steps below instead.

Run uname -m if you are not sure which one you need. x86_64 means x86_64, and aarch64 means ARM64.

  1. Install the package from the folder you downloaded it to. The package manager also installs the libraries WePROXA needs.

    Terminal window
    sudo apt install ./weproxa_*.deb
  2. Launch WePROXA from your desktop’s app menu, or run weproxa in a terminal.

  3. Trust the certificate before you inspect HTTPS. WePROXA creates its own root CA certificate on first launch, but it does not install it for you. Open Settings → CA Certificate and click Install & Trust. See Linux HTTPS Certificate Setup for details, including the browser step.

Both packages recommend certutil, and apt and dnf install recommended packages by default. WePROXA uses certutil to add its certificate to Chrome, Chromium, and Firefox.

WePROXA checks for a new version each time it starts. When you choose Install & Restart, your desktop asks for your password, because the update installs a system package. See Updates.

  • Start the proxy from the toolbar. On GNOME and KDE Plasma, WePROXA sets the desktop’s proxy settings, and restores them when the proxy stops or the app quits.
  • Other desktops have no proxy settings WePROXA can change. Set the proxy in each app you want to capture instead.
  • Command-line tools ignore the desktop’s proxy settings. Copy the export commands from Settings → Proxy Config into your shell. See Terminal Proxy Setup.
  • Firefox follows the desktop’s proxy settings when it is set to Use system proxy settings.
  • The weproxa-mcp command for AI clients is installed at /usr/bin/weproxa-mcp, so it is on your PATH with no extra step. See MCP Integration.

To run the proxy without a window, for example on a CI runner or a server with no desktop, install weproxa-cli instead:

Terminal window
curl -fsSL https://weproxa.com/cli | bash

It needs no graphical desktop and no system package. See Headless CLI.

These features are not available on Linux yet:

  • Global shortcut under Wayland. The marker shortcut works in an X11 session only. Under Wayland, use Add Marker in the tray menu instead.
  • Opening a configured terminal. Linux has no standard way to name your terminal app, so Settings → Proxy Config offers the commands to copy instead of a button.
  • Network change alerts. Network Health cannot detect a change of network yet.

To uninstall WePROXA on Linux:

  1. If you have a Pro license, open Settings → License and click Deactivate first. This frees the activation so you can use the license on another computer.

  2. Quit WePROXA if it is running. Quitting restores your previous proxy settings.

  3. Remove the package:

    Terminal window
    sudo apt remove weproxa

    This also removes the weproxa-mcp command.

  4. If you trusted the WePROXA Root CA, remove it from the system store and your browsers. See Removing the Certificate.

  5. Optionally, delete WePROXA’s data. Removing the package keeps your settings, rules, Workspaces, saved requests, and the CA certificate files. Export any Scenario you want to keep first, then run:

    Terminal window
    rm -rf ~/.local/share/com.ennbou.weproxa ~/.cache/com.ennbou.weproxa

    See Where WePROXA stores its data.