Loon · WLOC setup tutorial

Set up WLOC on Loon — plugin, certificate path, and MitM, step by step

Loon is straightforward until you hit the certificate path step. Every other client assumes you use the default CA. Loon makes you explicitly point the plugin at the certificate. It is a security feature — Loon does not want plugins silently borrowing a CA they should not have. Once you know where that setting lives, the rest is smooth.

Before you start

WLOC installed.
Loon installed (separate purchase).
A test device.
Stable Wi-Fi.

Step 1: Install the WLOC plugin

Copy the Loon plugin URL: https://wloc.app/modules/wloc.lpx. In Loon, Plugin tab, tap +, paste URL, Subscribe. Make sure toggle is ON.

.lpx plugin contains scripts, argument block, and MitM hostname list.
Loon supports auto-update for subscribed plugins.

Step 2: Generate CA and configure the plugin certificate path

Loon Settings → MitM → Generate CA. Install profile. iOS trust: Settings → General → About → Certificate Trust Settings → toggle ON. Now the Loon-specific step: Plugin tab → WLOC plugin details → set certificate path to Loon CA. Nine times out of ten, MitM is dead because this path was never set.

CA: Loon Settings → MitM → Generate CA.
iOS trust: Settings → General → About → Certificate Trust Settings.
Plugin certificate path: Plugin tab → WLOC plugin details → certificate path → Loon CA.

Step 3: Verify with WLOC diagnostics

Save a test target. Run diagnostics. Loon uses $loon persistent store — no manual config. Look for patch count > 0.

Loon uses $loon persistent store.
Patch count > 0 confirms the response script.

Step 4: Restore: clear, disable plugin, revoke CA

WLOC: clear target. Loon: toggle plugin OFF, disable MitM. iOS: remove CA profile. Plugin can stay subscribed.

Toggle plugin OFF, then disable MitM.
Remove CA profile from iOS Settings.

Common gotchas

Plugin active but MitM not working

You skipped the certificate path. Plugin tab → WLOC plugin details → certificate path → Loon CA. That is it. Nine out of ten support requests.

FAQ

Why does Loon need a certificate path setting?

Loon requires each plugin to explicitly declare which CA to use. This prevents plugins from silently using an unintended CA.