The 32 bit windows version isn't supported (asking for i686 Windows build)

[amiralishoja]

Hi, thank you for helping us to connect to the internet with this amazing tool.
I had a problem that I'll describe it here down

I have an unused old system, so I wanna run the program on it and just install the CA on my other devices and use it without installing tool on other devices.
my problem is that my old system have a 32 bit windows and it'll take a lot of time to I install a 64 bit windows and updata it to 10 and right now I'll be happy if you made a 32 bit version if it's possible, if is not I'll update my windows and th@ anks for the time you gived to me.

I did open an issue already about it on issue #155
but it closed because there we changed the subject, so here I wanna ask for the i686 Windows build

[therealaleph]

Hi @amiralishoja — thanks for the context. The i686-pc-windows-msvc build is real work but isolated; tracking as a follow-up to #155 (which closed today after you got google_only bootstrap working).

For now, two paths that don't require the build:

1. Run mhrv-rs on a different device, use that device's proxy from your 32-bit Windows. You can install mhrv-rs on:

• Any 64-bit Windows machine (laptop, family computer)
• Any Mac
• Any Linux box
• An Android phone running mhrv-rs in Proxy-only mode

Then on the 32-bit Windows, set the system proxy to point at that device's IP + port 8085 (HTTP) or 8086 (SOCKS5). The 32-bit Windows just consumes the proxy; mhrv-rs runs elsewhere. Install the CA on the 32-bit Windows so HTTPS interception works.

2. Wait for the i686 build. I'll add i686-pc-windows-msvc to the release matrix in a future release. The Rust target itself works (it's tier-1), it's just adding the matrix entry + ensuring eframe / wgpu compile on 32-bit. Realistic timeline: a week or two for a low-priority maintainer like me; sooner if you (or anyone reading this) wants to send a PR adding it to .github/workflows/release.yml. The change is ~5 lines.

The "install CA on multiple devices, run mhrv-rs on one" pattern (path 1) is actually exactly what mhrv-rs is designed for — listen_host = 0.0.0.0 lets you share the proxy across LAN. That's covered in #225 reply end-to-end.

Cross-linking #155 ↔ #272 as the i686-pc-windows-msvc tracker.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[amiralishoja]

Thank you, actually I don't know how I have to make it, so I'll be waiting until you do it. Is there any short video or document that teaches me how to do it ?
Because I'm a beginner and I'm not familiar with GitHub release and action builds

If it is there I'll be thank you if you mention it down here, after learning how it's working absolutely I'll send a PR to solve this, but if I could do it 😂

[therealaleph]

@amiralishoja — no worries, here's a beginner-friendly walkthrough. The change for adding i686-pc-windows-msvc is small (~5 lines in one YAML file).

Step 1: Set up your local environment

# Install Rust (one-time)
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

# Add the i686 Windows target
rustup target add i686-pc-windows-msvc

Step 2: Fork the repo

Go to https://github.com/therealaleph/MasterHttpRelayVPN-RUST → click "Fork" in the top right → "Create fork".

This creates https://github.com/<your-username>/MasterHttpRelayVPN-RUST — your own copy.

Step 3: Clone your fork + create a branch

git clone https://github.com/<your-username>/MasterHttpRelayVPN-RUST
cd MasterHttpRelayVPN-RUST
git checkout -b add-i686-windows

Step 4: Edit .github/workflows/release.yml

Find the build matrix (search for target: x86_64-pc-windows-gnu) and add a new entry below:

          - target: i686-pc-windows-msvc
            os: windows-latest
            name: mhrv-rs-windows-i686

Should look like:

          - target: x86_64-pc-windows-gnu
            os: windows-latest
            name: mhrv-rs-windows-amd64
          - target: i686-pc-windows-msvc        # ← new
            os: windows-latest                   # ← new
            name: mhrv-rs-windows-i686           # ← new

Step 5: Commit + push

git add .github/workflows/release.yml
git commit -m "ci: add i686-pc-windows-msvc to release matrix (#272)"
git push origin add-i686-windows

Step 6: Open the PR

GitHub will show "add-i686-windows had recent pushes" — click the "Compare & pull request" button. Set:

• Title: ci: add i686-pc-windows-msvc to release matrix
• Description: "Closes The 32 bit windows version isn't supported (asking for i686 Windows build) #272. Adds 32-bit Windows binary to the release matrix per user request."

Click "Create pull request".

I'll review and merge — the change is mechanical so it'll go fast. The i686 binary will build on next release.

Caveats (FYI, don't need to do anything):

• The UI binary may not build on i686 (some eframe/wgpu deps may not target 32-bit). If the matrix entry's UI build fails, we can mark it --features "" (CLI-only). I'll handle that in review if needed.
• The windows-latest runner is a 64-bit Windows VM but it cross-compiles to i686 fine (Rust's cross-compilation handles it).

GitHub PR Documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

If you get stuck at any step, just reply here and I'll help. Or if it's easier, I can just do it myself when I get a quiet hour — it's a 5-minute change. But you taking it through PR is more valuable because you go through the whole flow once and the next time will be 2 minutes for you.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[therealaleph]

@amiralishoja — fantastic, you went through the whole flow. PR #288 is merged. The i686-pc-windows-msvc build will run on the next release tag and you should see mhrv-rs-windows-i686.zip in the release artifacts.

The release matrix has fail-fast: false so even if i686 hits a UI build issue (some 32-bit eframe deps may be tricky), the rest of the release ships normally and we just don't have an i686 binary that round. If it does fail, we can iterate from the actual error.

Thanks for taking this through GitHub PR end-to-end on what sounded like a first-time flow. That was the harder bit — the next PR you do will be 2 minutes for you. Closing #272 as resolved.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}