[Self-hosted] Users with paid or gifted Premium are still asked to get Premium

(#894) Bug Closed: Fixed billing self-hosting

Reproduction steps

Get paid/gifted Premium > User Settings > Profile > Change Username > Get premium (already has it)

Observed behaviour

Thinks user doesn't have premium when they do

Build information

Stable Web 2026.1002.172440, Linux (x64), Firefox 156.0, Locale en-US

Platform

Self-hosting

Evidence

  1. Alek B | TekkNodes changed the status from Awaiting confirmation to Confirmed
  2. Alek B | TekkNodes changed the status from Awaiting confirmation to Confirmed
  3. Hampus changed the status from Confirmed to Fixed

11 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Awaiting confirmation
Fixed in self-hosted 2026.1008.190217. Users with paid or gifted premium on a self-hosted instance can change their tag without being asked to get Premium.
Comment by Rex
RexSystem 1 vote
Status changed from Confirmed to Awaiting confirmation
Fixed in the self-hosted api 2026.1011.113345: limits now follow the instance premium model, so users with paid or gifted premium are no longer asked to get it.
Comment by Alek B | TekkNodes
Settings > Profile Click on Discrimination > get told to get premium So premium still isn't being triggered to accounts properly. Canary Web 2026.1008.190217, Linux (x64), Firefox 157.0, Locale en-US
Comment by Alek B | TekkNodes
Alek B | TekkNodes OP1 vote edited Still happening 4 replies
Canary Web 2026.1011.174115, Linux (x64), Firefox 157.0, Locale en-US Tried it on 2 accounts, my alt and my main, still pointing to the premium. Just turned off the billing, and everyone has premium, that does work. BUT when billing is active (on) it doesn't let us change the numbers.
Comment by Hampus
HampusStaff 1 vote 3 replies
What fluxer-api image tag are you using?
Comment by Alek B | TekkNodes
Alek B | TekkNodes OP1 vote 2 replies
v1
Comment by Hampus
HampusStaff 1 vote 1 reply
"v1" is a moving tag, so it depends on when you last pulled. Can you run this in your self-hosting folder and send what it prints? docker inspect --format '{{ index .Config.Labels "app.fluxer.build-version" }}' $(docker compose ps -q api) If it's older than 2026.1011.113345, run docker compose pull && docker compose up -d and try again.