Error messages & fixes

The most common error messages and how to fix them. Lumbung's server messages are in Indonesian; each heading shows the original text.

Clone / push keeps asking for a password, then fails

Authentication failed or 401:

• Use a token, not your Jianren account password. Any username works.
• Token expired or revoked? Create a new one in Access tokens, then clear the old credential (see Tokens).
• Too many failed attempts block your IP for a while (Terlalu banyak percobaan masuk yang gagal) — wait 10 minutes.

Repo tidak ditemukan (not found) / 404

Private repos look "missing" to non-members. Check the URL spelling and ask the owner to invite you (Settings → Members).

Token ini tidak punya cakupan tulis_repo

Your token is read-only. Create a token with the tulis_repo scope.

Kamu tidak punya izin push ke repo ini (no push permission)

Your role is Guest or Reporter. Ask a maintainer to raise it to Developer.

Branch main terlindungi — push langsung tidak diizinkan (protected)

Create a new branch and open a merge request:

git switch -c fix/name
git push -u origin fix/name

Force push ke … tidak diizinkan

That branch is protected. Don't rewrite history; merge the latest changes first:

git pull --no-rebase
git push

rejected … (fetch first) / non-fast-forward

Lumbung has commits you don't have yet:

git pull
git push

Kuota penyimpanan pemilik repo penuh (quota full)

Delete unused repos, remove large files from history, or ask an admin for more quota. Large files (videos, datasets, build output) shouldn't live in git.

Akses … dicabut / Repo diarsipkan / Repo ini cermin (read-only)

The repo is read-only for now. Contact its owner; for mirrors, change the source repo instead.

SSH: Permission denied (publickey)

The key isn't registered or SSH offers another key — see SSH keys.

Merge request: Merge button disabled

Read the requirement list in the merge box: conflicts (how to resolve), missing approvals, open threads, or still a draft.