What to check first
Verify your server's version and its signature policy using a test repository and an authorized recovery administrator.
Choose a KeySigner setup
| Setup guide | What it does and what to keep available |
|---|---|
| Test a Gitea browser sign-in code → | Enroll a fresh code and verify a browser sign-in to the test instance. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available Keep Gitea’s single-use recovery key where you can reach it outside KeySigner. |
| Replace a Gitea browser sign-in code → | Check whether a browser stays signed in, then verify the replacement and rejection of the old code. You need KeySigner on iPhone or Mac with Sign-in codes. Keep available Keep independent recovery and the original settings session until the fresh sign-in works. |
What it covers
The Git service administrator has powers that repository collaborators do not.
Troubleshooting
Does Gitea still reject your code after replacement?
Check the server address and which entry in KeySigner came from the new QR code. Try a fresh code in a clean session and keep independent recovery available.
Replace Gitea and Forgejo sign-in codes →
Check Gitea status for reports on cloud.gitea.com and Gitea’s other hosted services. For a self-hosted instance, give your operator the hostname and time of the failure.
Documentation and support
Gitea documentation
Configure and verify signed commits
Set up multi-factor authentication