[Self-hosted] Unexpected deleted users

(#831) Bug Fixed self-hosting

Observed behaviour

I noticed an unexpected user entry in the Fluxer Admin panel under the admin panel The entry appears as: DeletedUser#0000 ID: 1 Status: User I did not delete this user, and I did not perform any action that should have created or produced a DeletedUser#0000 account. When I click the result, the Admin panel open the page reports but it show: User Not Found No user found with ID 1 I have also checked inside the PostgreSQL users data but I did not found any deleted users.

Reproduction steps

  1. Start a self-hosted Fluxer instance using the v1 release with PostgreSQL as the database backend.
  2. Log in to the Fluxer Admin panel.
  3. Navigate to Lookup → Users.
  4. Perform a user lookup.
  5. An unexpected user entry named DeletedUser#0000 appears with ID 1.
  6. Click the DeletedUser#0000 entry.
  7. Fluxer navigates to /admin/users/1.
  8. The page displays “User Not Found – No user found with ID 1.”
  9. Check the PostgreSQL users data; the DeletedUser#0000 entry is not present as an existing user.
  10. No user was manually deleted during this process, and no database records were manually modified.

Build information

Stable Web 2026.908.233045, Windows NT 10.0 (x64), Firefox 147.0, Locale en-US

Platform

Self-hosting

Evidence

  • 650522958-1531f8dc-fbe4-42c3-b7bc-765e8dcf2129.png

    650522958-1531f8dc-fbe4-42c3-b7bc-765e8dcf2129.png

    1920×956 | 81 kB

  • 650526514-15a7aab1-0dc7-4474-84b3-17e47f694bf0.png

    650526514-15a7aab1-0dc7-4474-84b3-17e47f694bf0.png

    1920×961 | 47 kB

3 comments

Sign in with Fluxer to comment and vote.
Comment by Hampus
HampusStaff 1 vote originally by @hampus-fluxer on GitHub
This is a built-in dummy user! I'll take a look if we still use it, and whether it can be removed. It is not actually something that exists in the database, but it is returned by the user repository method.
Comment by @erredi
RexSystem 1 vote originally by @erredi on GitHub OP
now I understand in fact I couldn't find it in the database, if it's just a placeholder there are no problems, I opened this issue thinking it was a bug!