Skip to main content

Credential Troubleshooting

Credential Troubleshooting

Support Guide

Identify the active runtime, remote protocol, provider, and source before retrying a push.

Commandcusty configure credentials

Category

Configuration

Quick Command

custy configure credentials status

The configured file is missing​

Run status. A missing file is not malformed: Custy tries the next configured source and can then use an approved interactive prompt. Mount the intended directory at /run/secrets/custy or set CUSTY_CREDENTIALS_DIR.

The provider is enabled but its file is missing​

Enabled: yes comes from the mounted project configuration. Token file: missing means the current container cannot see the external file. Re-run status with the same credential bind mount used during setup. An environment source may still show missing when a valid file source is already available.

File setup warns that input may be echoed​

The container was started without a controllable terminal. Use both -i and -t, normally written as docker run --rm -it. Current Custy versions reject the unsafe hidden-input fallback and explain the required invocation.

The username and password prompt disappears​

Older images could capture terminal streams while Git was waiting for input, making an active prompt look frozen. Rebuild or pull a current image. Custy now releases the progress display and gives manual Git authentication direct terminal ownership. For HTTPS, type the username and a PAT—not an account password. Pressing Enter twice submits empty credentials and causes an authentication failure.

The token file is invalid​

Custy stops on symbolic links, directories, oversized data, invalid encoding, multiple lines, NUL bytes, or surrounding whitespace. Recreate it through the wizard or set --replace; never weaken validation to accept ambiguous data.

Local execution ignores the configured token​

This is expected when container_only = true. Local execution keeps the host's normal Git helper or SSH session. Set container_only = false only when the external fallback is intentionally required locally.

The remote uses SSH​

Custy's token fallback applies only to supported HTTPS hosts. Configure SSH keys, agent forwarding, known_hosts, and file permissions through Git/SSH.

A non-interactive push fails immediately​

With fail_non_interactive = true, Custy sets GIT_TERMINAL_PROMPT=0 when a prompt cannot be used. Supply the configured file or environment source rather than disabling the safeguard in CI.

Authentication is still rejected​

Terminal
bash
custy configure credentials status
custy configure credentials test --remote origin
git remote get-url origin

Check the exact host, HTTPS protocol, account username, PAT scopes, expiration, repository membership, and branch permissions. Custy preserves Git's failure details without printing the token.