Login Issues — Avora CLI

Restore access when login fails, a saved token expires, or commands are reaching the wrong Avora backend.

Task

Verify the API URL, clear an unusable session, and create a fresh authenticated session.

Prerequisites

• Valid Avora credentials.
• Network access to the intended API.
• Access to the configured CLI state directory.

Find This in Your Terminal

Start by checking environment overrides:

echo "$AVORA_API_URL"
echo "$AVORA_CLI_HOME"

Steps

1. Confirm that AVORA_API_URL points to the intended server, or unset it when the saved login URL should be used.

2. Run avora logout to clear the saved authentication object.

3. Sign in again with an explicit API URL when necessary.

   avora login --api https://api.example.com
   

4. Test the session with avora projects.

5. If commands use different state, make sure every shell has the same AVORA_CLI_HOME value.

Expected Result

Project listing succeeds and the refreshed session is stored with the correct API base URL.

Next Step

Return to Pull Code.

Troubleshooting

• A 401 after automatic refresh usually means the refresh token is no longer accepted; log in again.
• A connection error usually indicates an unreachable hostname, incorrect port, or server that is not running.
• Repeatedly seeing Not logged in can mean the state directory is unwritable or changes between shells.