AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Fluxer Services Incompatible with Cloudflare WARP Proxy

(#234) Bug Awaiting confirmation infra
by RexSystem edited originally by @MisutaaAsriel on GitHub

Summary

When using Cloudflare's WARP proxy service, whether via VPN or Proxy, Fluxer fails to properly load or function without adding *.fluxer.workers.dev and *.fluxer.app to WARP's Split-Tunnel address exemption list.
  • In Safari, registration attempts time out.
    • Viewing the Network tab, in developer tools, ip.fluxer.workers.dev shows in red with a timeout.
  • The electron app displays a grey screen and does not load.

Steps to reproduce

Failure

  1. Install WARP
  2. Attempt to open Fluxer

Success

  1. Open WARP settings
  2. Navigate to "Advanced" tab
  3. Open "Split-tunnel" settings
  4. Add *.fluxer.workers.dev and *.fluxer.app to the list of exempted addresses
  5. Close Fluxer
  6. Reopen Fluxer

Environment (optional)

  • macOS Tahoe 26.2
  • Safari 26.2
  • MacBook Air M2
  • 24GB RAM
  • Browser Client (Latest)
  • macOS Client 0.0.8 (0.0.8)

6 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Fixed to Awaiting confirmation
This was closed in a bulk cleanup before Fluxer V2 without being checked or fixed. It may work now, so it is waiting for someone to confirm whether the bug still happens.
Permalink
Comment by @MisutaaAsriel
RexSystem 1 vote originally by @MisutaaAsriel on GitHub OP
Note: this also impacts security requests to web.fluxer.app — I was unable to add a Passkey until I exempted both *.fluxer.workers.dev and *.fluxer.app.
Permalink
Comment by @aarondemolder
RexSystem 1 vote originally by @aarondemolder on GitHub
If it's useful to debug, I wanted to add that when WARP split tunnels is configured to "Include IPs and domains" only, this issue does not occur - e.g. when using WARP to access listed IP ranges or named private services on remote machines, rather than VPN/proxying the entire connection. This is our setup and we can access fluxer with no issue.
Permalink
Comment by @MisutaaAsriel
RexSystem 1 vote originally by @MisutaaAsriel on GitHub OP
If it's useful to debug, I wanted to add that when WARP split tunnels is configured to "Include IPs and domains" only, this issue does not occur - e.g. when using WARP to access listed IP ranges or named private services on remote machines, rather than VPN/proxying the entire connection.
This is because that setting "inverts" the split tunnel list so only the specified IPs and domains are accessed through WARP. So naturally, fluxer not being on it, it would work. In my case my ISP has unstable service and I find WARP improves connection reliability, stability. So I use it in place of Private Relay (as Private Relay only impacts Safari, Mail) to mask my IP and receive more reliable service.
Permalink
Comment by @pranavganesh6
RexSystem 1 vote originally by @pranavganesh6 on GitHub
hey! i'm on a windows and I followed your process, and this allows fluxer to load, but I cannot send any messages nor can I join any servers. I put in the EXACT things you inputted and it doesn't work. I'm on the most recent version, by the way :)
Permalink
Comment by @MisutaaAsriel
RexSystem 1 vote originally by @MisutaaAsriel on GitHub OP
hey! i'm on a windows and I followed your process, and this allows fluxer to load, but I cannot send any messages nor can I join any servers. I put in the EXACT things you inputted and it doesn't work. I'm on the most recent version, by the way :)
Ive noticed even with the changes sometime Fluxer will time out or fail to load. There may be issues with how Fluxer operates that may not play well with all ISPs.
Permalink