Overriding `FLUXER_CLIENT_IP_HEADER_NAME` causing frontend to break due to 403 to RPC

(#697) Bug Closed: Fixed self-hosting

Summary

When you override the FLUXER_CLIENT_IP_HEADER_NAME to anything other than x-forwarded-for the frontend stops working because all /rpc/internal returns a 403.

Steps to reproduce

  1. Go to docker-compose.yml
  2. Override FLUXER_CLIENT_IP_HEADER_NAME to something other than x-forwarded-for
  3. Run docker compose up -d --force-recreate api
  4. Run docker compose logs -f and try to access the app and observe the 403s appearing.

Environment

Dunno about version, whatever latest build was as of 1st July 2026, on Arch Linux.

Logs or screenshots

api-1               | {"level":"info","time":"2026-07-02T14:38:38.697Z","service":"fluxer-api","env":"production","method":"POST","path":"/internal/rpc","status":403,"durationMs":0,"msg":"Request completed"}
api-1               | {"level":"warn","time":"2026-07-02T14:38:39.614Z","service":"fluxer-api","env":"production","path":"/.well-known/fluxer","msg":"Rejected request without required proxy headers"}
  1. Tarek changed the status from Awaiting confirmation to Fixed

2 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Awaiting confirmation
Overriding FLUXER_CLIENT_IP_HEADER_NAME no longer breaks the web app.
Deleted comment
Removed by moderator Rex: Removed a general status note that was posted on many GitHub threads. It no longer applies here.