Setting Up a Local HTTP Proxy on Android with Termux & Privoxy (No Root)

Before you start

Running a local HTTP proxy on Android lets you filter, cache, or modify web traffic without installing a system‑wide VPN or rooting the device. This guide assumes you have a fairly recent Android version (7.0+), a stable Wi‑Fi connection, and at least 200 MB of free storage for Termux and its packages.

What you’ll need:

• Google Play Store or F‑Droid access to install Termux.
• A Wi‑Fi network (cellular data can be used, but the proxy setup differs slightly).
• Basic comfort with a Linux‑style command line.

Safety note: The proxy runs entirely in user space, so it cannot alter system files. However, routing all traffic through a local proxy may expose you to privacy risks if the proxy configuration is left open to other apps. Keep the proxy port blocked by a firewall when not in use.

Step 1 – Install Termux and update its package repository

If you see a warning about storage permissions, grant Termux access via Settings > Apps > Termux > Permissions > Storage. Without this, Privoxy will not be able to write its log file.

Step 2 – Install Privoxy

Privoxy runs as a user‑space HTTP proxy on a configurable port (default 8118). It does not require root privileges, which makes it ideal for our purpose.

Step 3 – Configure Privoxy for local use

At this point Privoxy is ready to run, but we’ll add a small wrapper script to keep it alive when the screen turns off.

Step 4 – Create a start‑up script

Note: The termux-wake-lock command keeps the CPU awake, preventing Android from killing the process when the screen turns off. If you prefer the proxy to stop when you’re not actively using the device, omit that line.

Step 5 – Point Android’s Wi‑Fi proxy to the local server

Android will now send all HTTP (not HTTPS) traffic from apps that respect the system proxy through Privoxy. Most browsers, the Google Play Store, and many third‑party apps follow this setting.

Step 6 – Verify that traffic is flowing through Privoxy

Because Privoxy only handles plain HTTP, HTTPS sites will still connect directly unless you also install a TLS‑intercepting tool, which is beyond the scope of this no‑root guide.

Step 7 – Using the proxy with apps that ignore the system setting

Some apps (e.g., certain VPN clients or browsers that bundle their own networking stack) bypass Android’s proxy configuration. For those, you can use ProxyDroid‑style wrappers, but they typically require root. A practical workaround is to use adb reverse to forward traffic from the app’s local port to Privoxy, but this also needs a PC. In most everyday scenarios, the system proxy covers the majority of traffic you care about, such as web browsing and app updates.

Troubleshooting

Privoxy won’t start

• Port conflict: If another app already uses port 8118, Privoxy will abort. Change the listen-address line to an unused port (e.g., 127.0.0.1:8888) and update the Android proxy settings accordingly.
• Missing libraries: Run pkg install libandroid-glob if you encounter “cannot open shared object file” errors.
• Termux session killed: Ensure you started Privoxy with the wrapper script that includes termux-wake-lock. You can also enable Termux:Boot (install the add‑on) and add ~/start-privoxy.sh to its ~/.termux/boot folder so the proxy restarts after a reboot.

No traffic appears in the log

• Confirm the Android proxy is set to 127.0.0.1 and the correct port.
• Check that the Wi‑Fi network you are on is the one you edited. Android stores proxy settings per‑network.
• Some apps use HTTPS exclusively; they will not be logged unless you enable TLS‑interception (requires certificates and is not covered here).

Websites load slowly or fail

• Privoxy’s default filtering can block certain scripts or ads that a site relies on. Open http://config.privoxy.org and disable aggressive filters under the Actions tab.
• High latency may be caused by the device’s CPU throttling when the screen is off. Keep the wake lock active or manually start the proxy after you unlock the device.

Advanced tweaks (optional)

• Content filtering: Add custom rules in $PREFIX/etc/privoxy/user.action to block trackers, strip cookies, or rewrite URLs.
• Caching: Enable the built‑in cache by uncommenting enable-cache 0 (set to 1) in the config file. This can speed up repeated requests on low‑bandwidth connections.
• Running as a background service: Install the Termux:Boot add‑on, then place the start script in ~/.termux/boot/start-privoxy.sh. The proxy will start automatically after each reboot.

When to stop the proxy

If you no longer need the proxy, simply kill the Privoxy process and remove the wake lock:

pkill privoxy
termux-wake-unlock

Remember to revert the Wi‑Fi proxy settings to None** to avoid apps trying to connect to a non‑existent local server.