Description
After reinstalling 9remote (npm install -g 9remote, version 2.0.22, freshly reinstalled, no cache leftovers), the app consistently fails at the "Preparing" stage with the following error when downloading the cloudflared tunnel binary:
❌ Failed to download cloudflared: Integrity check failed: HTTP 404
Error: Integrity check failed: HTTP 404
at ia (C:\Users\myuser\AppData\Roaming\npm\node_modules\9remote\dist\cli.cjs:44:366)
at async Jt (C:\Users\myuser\AppData\Roaming\npm\node_modules\9remote\dist\cli.cjs:43:7350)
at async qi (C:\Users\myuser\AppData\Roaming\npm\node_modules\9remote\dist\cli.cjs:62:701)
at async zi (C:\Users\myuser\AppData\Roaming\npm\node_modules\9remote\dist\cli.cjs:74:55)
at async Ya (C:\Users\myuser\AppData\Roaming\npm\node_modules\9remote\dist\cli.cjs:74:387)
The progress bar shows "Downloading tunnel binary 100%" right before the error, suggesting the download URL itself returns a 404 (the request completes, but the resource doesn't exist), rather than a network/connectivity timeout.
Steps to Reproduce
npm install -g 9remote (v2.0.22)- Run
9remote (also tested via the desktop GUI app — same failure, but silently: GUI just loops back to the welcome screen with no visible error)
- Observe failure at "Preparing → Downloading tunnel binary"
Additional Notes
- Confirmed this isn't a stale-cache issue:
~/.9remote/bin/ is empty (0 files) before and after the failed attempt, so the binary never downloads at all.
- Fully uninstalled and reinstalled the npm package (
npm uninstall -g 9remote → npm install -g 9remote) — error is 100% identical, byte-for-byte same stack trace, confirming the issue is not local environment/cache related but with the cloudflared download URL/version reference hardcoded in cli.cjs.
- OS: Windows (via both CMD and Git Bash / MINGW64)
- npm registry version checked: 2.0.22 (latest, no newer version available)
Environment
- OS: Windows
- 9remote version: 2.0.22
- Install method: npm global install
- Node.js: v24.14.1
Expected Behavior
cloudflared binary downloads successfully and the app proceeds through Connecting → Tunneling → Verifying → Ready.
Actual Behavior
Download fails with HTTP 404. In the GUI app, this failure is swallowed silently — the connection wizard resets back to the welcome screen with no error message shown to the user, making this very hard to diagnose without running the CLI directly.
Description
After reinstalling 9remote (
npm install -g 9remote, version 2.0.22, freshly reinstalled, no cache leftovers), the app consistently fails at the "Preparing" stage with the following error when downloading the cloudflared tunnel binary:The progress bar shows "Downloading tunnel binary 100%" right before the error, suggesting the download URL itself returns a 404 (the request completes, but the resource doesn't exist), rather than a network/connectivity timeout.
Steps to Reproduce
npm install -g 9remote(v2.0.22)9remote(also tested via the desktop GUI app — same failure, but silently: GUI just loops back to the welcome screen with no visible error)Additional Notes
~/.9remote/bin/is empty (0 files) before and after the failed attempt, so the binary never downloads at all.npm uninstall -g 9remote→npm install -g 9remote) — error is 100% identical, byte-for-byte same stack trace, confirming the issue is not local environment/cache related but with the cloudflared download URL/version reference hardcoded incli.cjs.Environment
Expected Behavior
cloudflared binary downloads successfully and the app proceeds through Connecting → Tunneling → Verifying → Ready.
Actual Behavior
Download fails with HTTP 404. In the GUI app, this failure is swallowed silently — the connection wizard resets back to the welcome screen with no error message shown to the user, making this very hard to diagnose without running the CLI directly.