github-starred/gitea-mirror
2
0
Fork 0
mirror of https://github.com/RayLabsHQ/gitea-mirror.git synced 2026-05-07 12:37:43 -05:00
Code Issues 103 Packages Projects Releases 93 Wiki Activity

[GH-ISSUE #172] Inalid email or password #457

New Issue
Closed
opened 2026-04-13 14:10:53 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 14:10:53 -05:00
Owner
Copy Link

Originally created by @groke76 on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/172

Hi, after using gitea-mirror for a couple of months, I can no longer log in, I get "invalid email or password". I have checked the logs, checked the Gtea token is correct, recreated gitea token, but I still get "invalid email or password, please contact administrator", but I am the administrator. And I cannot see any places to create a new gitea-mirror user or reset the user anywhere.
Is this a bug on new version or something?

Originally created by @groke76 on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/172 Hi, after using gitea-mirror for a couple of months, I can no longer log in, I get "invalid email or password". I have checked the logs, checked the Gtea token is correct, recreated gitea token, but I still get "invalid email or password, please contact administrator", but I am the administrator. And I cannot see any places to create a new gitea-mirror user or reset the user anywhere. Is this a bug on new version or something?
GiteaMirror commented 2026-04-13 14:10:57 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Feb 24, 2026):

Added a proper admin recovery flow in PR #178.

What it adds:

  • bun run reset-password -- --email=user@example.com --new-password='new-secure-password'
  • Uses Better Auth-compatible password hashing
  • Upserts credential account if missing
  • Invalidates existing sessions for that user after reset

This gives a non-destructive recovery path when an admin gets locked out and email reset is not configured.

<!-- gh-comment-id:3948876548 --> @arunavo4 commented on GitHub (Feb 24, 2026): Added a proper admin recovery flow in PR #178. What it adds: - `bun run reset-password -- --email=user@example.com --new-password='new-secure-password'` - Uses Better Auth-compatible password hashing - Upserts credential account if missing - Invalidates existing sessions for that user after reset This gives a non-destructive recovery path when an admin gets locked out and email reset is not configured.
GiteaMirror commented 2026-04-13 14:10:58 -05:00
Author
Owner
Copy Link

@arunavo4 commented on GitHub (Feb 24, 2026):

Resolved by #178 (admin CLI password reset flow + README docs).

<!-- gh-comment-id:3948887831 --> @arunavo4 commented on GitHub (Feb 24, 2026): Resolved by #178 (admin CLI password reset flow + README docs).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#457
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?