Canary: some requests bypass the system proxy (Stable works fine), causing long "connection problem" on startup and broken media

(#3617) Bug Needs triage desktop media self-hosting

Observed behaviour

On the Canary build, some network traffic does not go through the system proxy, while the Stable build respects it correctly on the same machine and network. I'm in a region behind the GFW, where a proxy is required to reach Fluxer's servers and media/CDN hosts. As a result, when launching Canary, the app shows the "Having trouble connecting?" banner for a long time and stays in the loading state. Once the connection finally succeeds, many media items (images, avatars, emoji, attachments, etc.) still fail to display. Stable works normally under the exact same proxy setup. I'm not sure whether this is a bug or an intentional change (e.g. for security reasons). If it's intentional, sorry about that. In that case, I'd appreciate knowing whether there's a setting or workaround for users who rely on a system proxy.

Reproduction steps

1.Configure a system-wide proxy (Windows system proxy settings; no TUN/transparent proxy mode). 2.Launch Fluxer Stable: it connects normally, and messages and media load. 3.Launch Fluxer Canary under the same conditions.

Platform

Windows, Self-hosting

  • Canary.png

    Canary.png

    1403×920 | 140 kB

  • Stable.png

    Stable.png

    1512×922 | 202 kB

Comments

Sign in with Fluxer to comment and vote.

No comments yet.