[GH-ISSUE #263] Repos got created first time but then are not syncing #1479

Closed
opened 2026-04-24 18:16:33 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @thisisjaymehta on GitHub (Apr 11, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/263

I installed forgejo and gitea-mirror
The I configured sync and repos got synced the first time.
But then they are not being updated with latest commits from github.

I can see following error in logs:

Stderr: fatal: could not read Password for 'https://sanitized-credential@github.com': terminal prompts disabled

However I can see my github connection is working fine when I do "Test Connection" in gitea-mirror

Image
Originally created by @thisisjaymehta on GitHub (Apr 11, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/263 I installed forgejo and gitea-mirror The I configured sync and repos got synced the first time. But then they are not being updated with latest commits from github. I can see following error in logs: Stderr: fatal: could not read Password for 'https://sanitized-credential@github.com': terminal prompts disabled However I can see my github connection is working fine when I do "Test Connection" in gitea-mirror <img width="2806" height="1648" alt="Image" src="https://github.com/user-attachments/assets/a2987c29-bbb7-401e-a777-670b004b8a93" />
Author
Owner

@arunavo4 commented on GitHub (Apr 13, 2026):

@thisisjaymehta This should be partially addressed in #266. The fix ensures auth credentials are always sent during migration (not just for private repos), which prevents the "terminal prompts disabled" error for newly mirrored repos.

One caveat — repos that were already migrated without credentials can't be fixed via the API (Gitea/Forgejo doesn't support updating mirror credentials through PATCH). For those, you'll need to delete and re-mirror them so the credentials get stored properly.

You can test with the PR image: ghcr.io/raylabshq/gitea-mirror:pr-266

<!-- gh-comment-id:4233881167 --> @arunavo4 commented on GitHub (Apr 13, 2026): @thisisjaymehta This should be partially addressed in #266. The fix ensures auth credentials are always sent during migration (not just for private repos), which prevents the "terminal prompts disabled" error for newly mirrored repos. One caveat — repos that were already migrated without credentials can't be fixed via the API (Gitea/Forgejo doesn't support updating mirror credentials through PATCH). For those, you'll need to delete and re-mirror them so the credentials get stored properly. You can test with the PR image: `ghcr.io/raylabshq/gitea-mirror:pr-266`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea-mirror#1479