When logging in and forgotten the password i see Don't have an account? Contact your administrator. but i am the admin. i dont have access the docker internal fs tho.
Uptime: About an hour (healthy)Created: 1 hour ago
I accidentally used bogus login while installing because it was complaining about wrong origin (the server has 3 exposed ips .10,.11,.12 and i tried to use .12 but it only allowed from .10)
Originally created by @Bluscream on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/164
When logging in and forgotten the password i see `Don't have an account? Contact your administrator.` but i am the admin. i dont have access the docker internal fs tho.
Application | Version | Network | Container IP | Container Port | LAN IP:Port | Volume Mappings (App to Host) | Autostart | Uptime
-- | -- | -- | -- | -- | -- | -- | -- | --
giteastarted | up-to-date | bridge Tailscale | 172.17.0.16 | 22:TCP3000:TCP | 192.168.2.12:2222192.168.2.12:3001 | /data/git/repositories/mnt/user/projects//data/mnt/user/appdata/gitea//opt/unraid/tailscale/usr/local/share/docker/tailscale_container_hook | Off | Uptime: 2 hoursCreated: 1 hour ago
gitea-mirrorstartedCompose Stack: gitea_mirror | Compose | gitea_mirror_default | 172.23.0.2 | 4321:TCP | 192.168.2.12:3002 | /app/datagitea_mirror_gitea-mirror-data | Compose | Uptime: About an hour (healthy)Created: 1 hour ago
I accidentally used bogus login while installing because it was complaining about wrong origin (the server has 3 exposed ips .10,.11,.12 and i tried to use .12 but it only allowed from .10)
Hi @Bluscream I realised I never added a proper reset password rather I just used to delete the user and recreate it again. casue its a backup anyway. But I will add a reset script. The one you dropped here has a few concerns.
Also, for that wrong origin you will need to add the ip where the container is running. Once I have some time in a week or so I will address this issue properly tho I have documented it the issue stems from the way better auth is configured.
<!-- gh-comment-id:3742288936 -->
@arunavo4 commented on GitHub (Jan 13, 2026):
Hi @Bluscream I realised I never added a proper reset password rather I just used to delete the user and recreate it again. casue its a backup anyway. But I will add a reset script. The one you dropped here has a few concerns.
Also, for that wrong origin you will need to add the ip where the container is running. Once I have some time in a week or so I will address this issue properly tho I have documented it the issue stems from the way better auth is configured.
Follow-up implemented in PR #178: added a built-in CLI admin password reset flow.
Command:
bun run reset-password -- --email=user@example.com --new-password='new-secure-password'
Behavior:
updates password hash in Better Auth credential account
creates credential account if missing
clears active sessions for that user (forces re-login)
Also documented in README under Admin Password Recovery (CLI).
<!-- gh-comment-id:3948876672 -->
@arunavo4 commented on GitHub (Feb 24, 2026):
Follow-up implemented in PR #178: added a built-in CLI admin password reset flow.
Command:
- `bun run reset-password -- --email=user@example.com --new-password='new-secure-password'`
Behavior:
- updates password hash in Better Auth credential account
- creates credential account if missing
- clears active sessions for that user (forces re-login)
Also documented in README under **Admin Password Recovery (CLI)**.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Bluscream on GitHub (Jan 12, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/164
When logging in and forgotten the password i see
Don't have an account? Contact your administrator.but i am the admin. i dont have access the docker internal fs tho.I accidentally used bogus login while installing because it was complaining about wrong origin (the server has 3 exposed ips .10,.11,.12 and i tried to use .12 but it only allowed from .10)
@Bluscream commented on GitHub (Jan 13, 2026):
@arunavo4 commented on GitHub (Jan 13, 2026):
Hi @Bluscream I realised I never added a proper reset password rather I just used to delete the user and recreate it again. casue its a backup anyway. But I will add a reset script. The one you dropped here has a few concerns.
Also, for that wrong origin you will need to add the ip where the container is running. Once I have some time in a week or so I will address this issue properly tho I have documented it the issue stems from the way better auth is configured.
@arunavo4 commented on GitHub (Feb 24, 2026):
Follow-up implemented in PR #178: added a built-in CLI admin password reset flow.
Command:
bun run reset-password -- --email=user@example.com --new-password='new-secure-password'Behavior:
Also documented in README under Admin Password Recovery (CLI).
@arunavo4 commented on GitHub (Feb 24, 2026):
Resolved by #178 (built-in CLI password reset command and documentation).