The Media Expiry setting only affects media at the time it is uploaded. If an instance admin changes this setting, previously uploaded media is not affected and only newly uploaded media uses the updated expiry setting.
I would expect changes to this setting to also apply retroactively, such that existing media would also observe the updated expiry setting for such an event when an instance’s data storage capacity conditions change. For example, if an instance owner is running out of space, they would probably want pre-existing media to have an expiry date applied to make room; inversely if an instance owner upgraded their storage capacity, they may no longer see the need to have expiry applied for pre-existing media.
Steps to reproduce
If media expiry is already enabled:
Upload an attachment in a text chat/channel.
Go to Configuration > Instance Config > Media & retention and uncheck "Enable attachment expiry" in the admin panel.
Fully restart docker compose stack.
Go back to the attachment that was uploaded in step 1; it will still have an expiry date applied.
If media expiry is already disabled:
Upload an attachment in a text chat/channel
Go to Configuration > Instance Config > Media & retention and check "Enable attachment expiry" in the admin panel.
Fully restart docker compose stack.
Go back to the attachment that was uploaded in step 1; it will have no expiry date applied.
Environment
Version: Latest Self-Hosted as of the time of documenting this bug.
Server OS: Debian 13.5
Client Browser: Fluxer PWA in Flatpak Brave Browser
Device: Computer
Falco changed the status from Awaiting confirmation to Fixed
The pull request fluxer#1182 mentions this post Closed
The pull request fluxer#1182 was closed without merging Closed
Status changed from Needs triage to Awaiting confirmationStatusNeeds triage→Awaiting confirmation
Fixed in the self-hosted api 2026.1011.113345: changing attachment expiry now also applies to files uploaded earlier. This applies to self-hosted instances only.
I've submitted a PR (https://github.com/fluxerapp/fluxer/pull/1182) to fix this It adds a background task that runs whenever the media config is updated in the admin panel, recalculating and applying the expiry settings retroactively to all existing attachments
This is confirmed to be fixed on Fluxer API 2026.1011.125745
Enabling media expiry applies an expiration date for all media based upon the date of upload. Disabling media expiry removes expiration dates for all uploaded media on the server.
3 comments
Comment by Rex
Comment by @SudhanshuMatrix
Deleted comment
Comment by Falco