Codeberg + KeySigner

Use KeySigner to generate one-time codes for your Codeberg browser sign-in.

What to check first

Start with a test account you control and keep its current browser session open. Have somewhere secure to save the scratch token Codeberg shows after enrollment.

KeySigner setups

KeySigner setup requirements →

What it covers

The test covers browser sign-in. Git access and commit signatures use separate credentials.

Make an offline recovery plan →

Troubleshooting

Does Codeberg reject a code from KeySigner?

Check the saved entry is for the same account, turn on automatic time on your device, and try a fresh code. Keep the working session and scratch token available.

Set up sign-in codes for Gitea, Forgejo and Codeberg →

Check Codeberg status for reports on Codeberg.org and related hosted services.

Find documentation and support →

Documentation and support

Codeberg documentation

Set up an authenticator code and save a scratch token
Add a key for signing changes

KeySigner setup help

Ask about this setup →