Core Management

Re:HomeProxy is multi-core: the LuCI app is the interface, and a separate core binary does the actual proxying. You install, update, and switch cores from Services → Re:HomeProxy → Core & Tools → Core management — no SSH required.

Choosing a core

	hiddify-core (default)	sing-box-extended
Engine	Fork of sing-box by the Hiddify team	Fork of sing-box with extra build tags
Footprint	Lighter; a compact build exists for small devices	Larger (~26 MB installed)
Protocols	Hiddify-app protocols, TLS fragment, XHTTP, Mieru, etc.	The widest protocol set…
AmneziaWG / WARP	❌ Not supported	✅ Supported

Rule of thumb: if you need AmneziaWG/WARP, or want the broadest protocol coverage and have ~40 MB free, choose sing-box-extended. Otherwise hiddify-core is the lighter default and is the only one with a compact build for tight-storage routers.

Which protocols appear in the node editor depends on the core you install — see Supported Protocols.

Installing — one smart button

Core Management has a single Install button per core. It does not ask you to choose between "standard" and "compressed" builds — instead it inspects your device and picks a build that actually fits:

It reads the free space on /overlay (persistent flash) and your free RAM.
For hiddify-core: if the full build fits → it installs the standard build. If storage is tight but there's enough RAM → it installs the compact build and tells you so.
If neither can fit → it stops with a clear message instead of installing something broken.

Why the guardrail matters

A core binary that is larger than the free overlay gets truncated as it's written, and then crashes with a "bus error" (SIGBUS) the moment it's launched — a confusing failure that looks like a corrupt download. The installer's size check exists specifically to prevent this: it never offers a build the device can't hold.

The compact build

The compact (UPX-compressed) build of hiddify-core is much smaller on flash, but it decompresses into RAM each time it launches — trading flash space for memory. The installer only picks it when there's enough free RAM, and shows a note like "Limited storage — installing the compact build (decompresses into RAM at launch)." On most routers this is invisible in day-to-day use.

Storage at a glance

Free on `/overlay`	What installs
~40 MB+	hiddify-core or sing-box-extended (full build)
~25–40 MB	hiddify-core (compact build, if RAM allows)
< ~25 MB	Not enough — free space, or bake the core into a custom firmware image

On a compressing overlay (jffs2/ubifs) the full build needs less free space than the raw figure, because the filesystem compresses it. The installer accounts for this automatically — trust its check over the table above.

Tight on flash but building your own image? Large cores fit comfortably when baked into the SquashFS root at image-build time (the SquashFS root is compressed and read-only), rather than installed into the writable overlay.

Switching cores and updating

Update: press Install again — it fetches the latest release and reinstalls.
Switch cores: install the other core; if both are present, Re:HomeProxy uses your Preferred core setting (on Client → Routing Settings). The config generator and the service honour the same preference, so the generated config always matches the core that will run it.
Custom / external core: instead of the managed install you can point Re:HomeProxy at a self-provided core binary (a build you compiled, or a version not in Releases) — it detects and uses it. Advanced setups only.
Version / status: the Core management section shows the installed core and version. If it shows all ?, the backend (rpcd) is stale — restart it (/etc/init.d/rpcd restart) and reload the page.

Resources & updates

The Core & Tools tab also has a Resources management section for the data files routing depends on — the GeoIP / Geosite databases and the RU rule-sets:

Check update fetches the latest rule-set and geo data on demand.
The RU routing lists also self-refresh on a schedule, so in normal use you don't need to touch this.
Subscriptions update separately — on demand from the Subscriptions tab, or automatically on a cron; see Subscriptions & Node Import.

Kernel modules

The proxy needs kmod-nft-tproxy and kmod-tun for transparent routing. The installer pulls these in; if routing doesn't work after a fresh install, confirm they're present.

See also: ByeDPI · Zapret · Supported Protocols · Troubleshooting

5.0 KiB Raw Blame History Unescape Escape