I see a lot of those errors in the forgejo log, do you have any idea why?
Failed to update mirror repository '/var/lib/forgejo/data/forgejo-repositories/crazywolf13-mirror/chezmoi.git': remote: Invalid username or token. Password authentication is not supported for Git operations.
fatal: Authentication failed for'https://github.com/CrazyWolf13/chezmoi.git/'
Migrate repository from failed: Clone: exit status 128 - fatal: could not read Username for'https://github.com': terminal prompts disabled
Thanks a lot!
Originally created by @CrazyWolf13 on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/254
Hi,
I see a lot of those errors in the forgejo log, do you have any idea why?
```bash
Failed to update mirror repository '/var/lib/forgejo/data/forgejo-repositories/crazywolf13-mirror/chezmoi.git': remote: Invalid username or token. Password authentication is not supported for Git operations.
fatal: Authentication failed for 'https://github.com/CrazyWolf13/chezmoi.git/'
```
```bash
Migrate repository from failed: Clone: exit status 128 - fatal: could not read Username for 'https://github.com': terminal prompts disabled
```
Thanks a lot!
I've upgraded to v3.14.2, cleared all errors, but they seem to re-appear.
Do I need to manually fix those repos?
<!-- gh-comment-id:4141543789 -->
@CrazyWolf13 commented on GitHub (Mar 27, 2026):
@arunavo4 this does not seem resolved.
I've upgraded to v3.14.2, cleared all errors, but they seem to re-appear.
Do I need to manually fix those repos?
@CrazyWolf13 can you try on a fresh setup? I think those mirrors need to re authenticated
<!-- gh-comment-id:4141564153 -->
@arunavo4 commented on GitHub (Mar 27, 2026):
@CrazyWolf13 can you try on a fresh setup? I think those mirrors need to re authenticated
I just did that to those possible, sadly 1 is currently unavailable due to DMCA takedown and one is gone, so ideally I want to just keep it gitea for now.
Then I have a private repo from my org which does not show up at all in gitea-mirror? Though it seems like initially it was added just fine, so I currently wonder why it is not being displayed.
Also this is how the new repo synced from gitea-mirror looks like:
<!-- gh-comment-id:4141605448 -->
@CrazyWolf13 commented on GitHub (Mar 27, 2026):
@arunavo4
Can this be reopened?
I just did that to those possible, sadly 1 is currently unavailable due to DMCA takedown and one is gone, so ideally I want to just keep it gitea for now.
Then I have a private repo from my org which does not show up at all in gitea-mirror? Though it seems like initially it was added just fine, so I currently wonder why it is not being displayed.
Also this is how the new repo synced from gitea-mirror looks like:
<img width="1367" height="827" alt="Image" src="https://github.com/user-attachments/assets/ab879663-4226-4a47-b501-f7e8b21d2d84" />
@CrazyWolf13 looks like it will take more time to investigate how can I address this cause I don't have a similar situation. Will check it out this weekend.
<!-- gh-comment-id:4141617521 -->
@arunavo4 commented on GitHub (Mar 27, 2026):
@CrazyWolf13 looks like it will take more time to investigate how can I address this cause I don't have a similar situation. Will check it out this weekend.
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 @CrazyWolf13 on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/254
Hi,
I see a lot of those errors in the forgejo log, do you have any idea why?
Thanks a lot!
@arunavo4 commented on GitHub (Mar 27, 2026):
The forgejo v12+ has new auth requirements
@CrazyWolf13 commented on GitHub (Mar 27, 2026):
@arunavo4 this does not seem resolved.
I've upgraded to v3.14.2, cleared all errors, but they seem to re-appear.
Do I need to manually fix those repos?
@arunavo4 commented on GitHub (Mar 27, 2026):
@CrazyWolf13 can you try on a fresh setup? I think those mirrors need to re authenticated
@CrazyWolf13 commented on GitHub (Mar 27, 2026):
@arunavo4
Can this be reopened?
I just did that to those possible, sadly 1 is currently unavailable due to DMCA takedown and one is gone, so ideally I want to just keep it gitea for now.
Then I have a private repo from my org which does not show up at all in gitea-mirror? Though it seems like initially it was added just fine, so I currently wonder why it is not being displayed.
Also this is how the new repo synced from gitea-mirror looks like:
@arunavo4 commented on GitHub (Mar 27, 2026):
@CrazyWolf13 looks like it will take more time to investigate how can I address this cause I don't have a similar situation. Will check it out this weekend.
@CrazyWolf13 commented on GitHub (Mar 27, 2026):
@arunavo4 thanks.
Let me know if more details is needed!