Windows Desktop sign-in ignores the HTTPS proxy and times out

[yx637718]

What happened

Environment

• Windows desktop app, installed on 2026-09-18.
• Exact packaged version is not exposed in the Windows executable metadata; the installer was the current desktop build available at installation time.
• Local HTTP proxy: http://127.0.0.1:7897. The proxy works for other applications and for a Bun request launched with the proxy environment.

Expected behavior

Freebuff Desktop should honor the standard proxy environment variables or the Windows proxy configuration when it is launched from Explorer, so the sign-in request can reach https://freebuff.com.

Actual behavior

The app shows:

Sign-in failed — retry

Could not reach freebuff.com: The operation timed out

The local Freebuff orchestrator is healthy at http://127.0.0.1:7371, and its auth status reports reason: request_timeout. The installed desktop bundle sends the sign-in request to POST https://freebuff.com/api/auth/cli/code with a 15-second timeout.

When Freebuff is launched normally from Explorer, it does not inherit the proxy environment available to the terminal, so the sign-in request goes direct and times out. A proxy-injected launcher is the current workaround.

Steps to reproduce

1. On Windows, configure a working local HTTP proxy at http://127.0.0.1:7897.
2. Install and launch Freebuff Desktop normally from Explorer, without proxy environment variables in the process environment.
3. Click Sign in to Freebuff.
4. Observe the timeout error.
5. For comparison, run a Bun HTTPS request with HTTP_PROXY and HTTPS_PROXY set to http://127.0.0.1:7897; the request reaches freebuff.com successfully.

Where does this happen?

Desktop app

Operating system

Windows

Version

Unknown packaged Windows desktop build (installed 2026-09-18)

Model

No response

Logs or screenshots

Observed UI error: “Could not reach freebuff.com: The operation timed out”. 

[rcc12301999-hue]

I had similar problem, i used the program " 1.1.1.1 (warp) " from cloudflare, and now i can access, maybe a DNS question?

[a649774420]

You can work around this by injecting the proxy environment variables via a batch script before launching the application:

Open a text editor (e.g., Notepad) and paste the following snippet.

(Make sure to replace 7897 with your actual local proxy port, such as 7890, 10809, etc.)
(If you use Clash you can check it at General page and find your port number):
@echo off
set HTTP_PROXY=http://127.0.0.1:7897
set HTTPS_PROXY=http://127.0.0.1:7897
set ALL_PROXY=http://127.0.0.1:7897
start "" "%LOCALAPPDATA%\Programs\freebuff\Freebuff.exe" --proxy-server="http://127.0.0.1:7897"
(Note: If Freebuff is installed in a different location on your machine, update the path after start "" to point to your actual Freebuff.exe path.)

Save the file as start_freebuff.bat. Launch Freebuff using this script whenever you need to sign in.