Quick Start

System requirements

All platforms require a 64-bit operating system and network access.

Platform Minimum version Requirements
macOS 10.15 Catalina or later Apple Silicon (ARM64), Xcode Command Line Tools
Windows Windows 10 version 1803 or later x64, WebView2, Microsoft Visual C++ Redistributable
Linux Ubuntu 22.04+ (AMD/ARM) WebKitGTK 4.1, GTK 3, OpenSSL, libfuse2 (AppImage only)

On Linux, the app also needs a way to obtain administrator privileges: pkexec, graphical sudo (zenity, kdialog, or yad), or terminal sudo.

VPN clients, antivirus software, and corporate proxies that intercept the same traffic may conflict with the app.

Installation

macOS

Open the .dmg and drag the app into Applications.

Windows

Run the -setup.exe installer.

Linux

The app ships as an AppImage. A browser saves it without the execute bit, so set that bit yourself before launching:

chmod +x Solpuga_<version>_aarch64.AppImage
./Solpuga_<version>_aarch64.AppImage

Without chmod +x the launch fails with Permission denied.

  • chmod +x did not help? The file is on a noexec mount — a shared VM folder, or /tmp on some systems. Move it to your home directory and try again.
  • Ubuntu 24.04 or newer needs FUSE 2: sudo apt install libfuse2t64. Without it the AppImage reports dlopen(): error loading libfuse.so.2.
  • Do not run it with sudo. As root, the app writes its CA and its configuration into /root, so the certificate wizard and the captured traffic will not match what you see on a normal launch.

First launch

1. Install the certificate

HTTPS can only be decrypted once the app's own root CA is installed and trusted on your computer. Each installation generates its own certificate.

The wizard lives under the SSL Certificate menu and does the work for you; your operating system may ask for an administrator password.

See Certificate Installation for details.

2. Start capturing

Start capture from the main window.

The system proxy is configured automatically, so you do not need to change the proxy settings yourself. If that fails, the proxy is still listening — point a browser or an app at it manually, using the address and port it reports.

Capture can also be started and stopped from the app's system tray icon.

3. Open a browser or app

Open the website or application whose traffic you want to inspect. Its requests appear as they happen, and selecting one shows its headers, body, status, timing, and the rest of the detail.

See Capture & Inspect Traffic for what is recorded.

Address and port

By default the proxy listens on all network interfaces (0.0.0.0), port 7070.

Both can be changed under Settings → Proxy.

Linux: terminal and Flatpak apps

Command-line tools and Flatpak apps ignore the GNOME proxy setting, so with the system proxy their traffic goes past Solpuga. There are two ways to capture it.

Transparent mode. Under Settings → Proxy → Capture mode, pick Transparent mode — all apps. HTTP/HTTPS traffic from every app is then redirected to the proxy. The first time, the system asks for the administrator password once, to install the Solpuga network helper service.

Manual setup. Keep System proxy and route terminal and Flatpak apps through Solpuga yourself. The commands use the default port 7070; if you changed it under Settings → Proxy, put yours in its place. no_proxy lists, separated by commas, the hosts that requests go to directly.

The current shell and the apps started from it:

export http_proxy=http://127.0.0.1:7070
export https_proxy=http://127.0.0.1:7070
export no_proxy='localhost,127.0.0.1'

Apps you start later in this session:

systemctl --user set-environment http_proxy=http://127.0.0.1:7070 https_proxy=http://127.0.0.1:7070 no_proxy='localhost,127.0.0.1'

A single run of a Flatpak app — replace <app-id> with its ID:

flatpak run --env=http_proxy=http://127.0.0.1:7070 --env=https_proxy=http://127.0.0.1:7070 --env=no_proxy='localhost,127.0.0.1' <app-id>

When you stop capturing, undo the session setup:

systemctl --user unset-environment http_proxy https_proxy no_proxy

In the shell where you set the variables, run unset http_proxy https_proxy no_proxy, or close it.

Solpuga 1.0.1 and earlier suggested a permanent flatpak override for Flatpak apps instead of a single run. If you set it, Flatpak apps send their requests to Solpuga's port even when capture is off. Check:

flatpak override --user --show

If it lists only http_proxy and https_proxy, remove the override:

flatpak override --user --reset

If it lists other settings too, delete just those two lines from ~/.local/share/flatpak/overrides/global.

What to do next

  • Map Local — replace a response with your own content.
  • Breakpoints — pause a request or a response and edit it.
  • Mobile Devices — capture traffic from iOS and Android devices and emulators.
  • Settings — proxy address, startup behaviour, bypass list.
  • License and activation — how to activate a licence and manage devices.