Troubleshooting#

The fixes people actually need, gathered in one place. Each one links to the full story on its page.

Git over HTTPS: authentication loops#

git push keeps asking for credentials, or answers 401 forever:

• The password is a personal access token, not your account password — every rickub_pat_… token works for git.
• A Read-only token can clone and fetch but can never push — mint a Full-access one for pushing.
• Tokens are shown once. If yours is lost or stale, delete it under Settings → Access tokens and create a new one.

Git over SSH: host key warnings#

The first connection asks you to verify rickub's host key. Its live ed25519 fingerprint is published on the Quickstart and Authentication pages — compare before accepting. On networks that block port 22, clone over 443: ssh://git@ssh.rickub.com:443/owner/repo.git.

Container registry errors#

The registry has its own troubleshooting section. The short version:

• 401 loops at docker login or push — expired/revoked PAT, or a read-only token where a read/write one is needed (t-401).
• Push refused with 429 — the namespace storage pool (git + LFS + registry) is full; delete images and tags or upgrade — pulls never stop (t-429).
• DENIED on push — the image name is bound to another repository; a namespace owner-admin can rebind it (t-denied).
• 405 on blob delete — shared layers are protected until nothing references them; let the 24-hour GC sweep (t-405).

LFS push warnings#

locksverify warnings on push are safe to silence — rickub does not implement the LFS file-locking API; the exact git config line is on the Git LFS page.

A workflow didn't run#

• Check the workflow actually appears under the Actions tab after the first push. Triggers outside push, pull_request, workflow_dispatch, schedule, release and workflow_call do not fire yet — a workflow triggered only by pull_request_target or friends is quietly inert (details).
• If the repository has a .rickub/workflows/ directory, it replaces .github/workflows/ entirely — a file in the GitHub directory will not run (details).

A workflow failed in a way the docs warned about#

• reports: is a parse error — it is a rickub extension and belongs in .rickub/workflows/ only (why).
• A secret name was rejected — names may not start with GITHUB_ or RICKUB_; rename it on the settings page and in the YAML (details).
• GHCR push fails with an auth error — rickub's GITHUB_TOKEN is not a github.com credential; use your own PAT stored as a secret (details).
• A job asking for windows-latest or macos-latest fails immediately — runners are Linux x86-64 only, by design (runner classes).

An import came over incomplete#

Re-run the import: it matches each item to its source and fills in what is missing instead of duplicating. A large GitHub import without a token can hit GitHub's 60-request-per-hour anonymous limit — supply a source token and retry (details).

Commits show Unverified#

Work through the checklist on Verified commits — the common ones are the GPG_TTY terminal issue and a committer email that does not match your account email.

Locked out of two-factor#

Sign in with a recovery code from the same challenge screen. Recovery codes are shown once when 2FA is enabled; if you have exhausted them and lost your authenticator, support can help verify you another way.