Supported Methods
Setting Up 2FA
Setting up 2FA requires three steps: authorize the addition of a new method, configure the method, then activate it with a verification code.Step 1: Authorize a new method
Before adding any 2FA method, authorize your account. For your first method, authorization uses email by default. For subsequent methods, use an existing 2FA method.Step 2: Configure the method
For Authenticator App (TOTP):vastai tfa resend-sms --secret <SECRET>.
Email is not a 2FA method you add in this step — it is the verification channel used by
tfa auth-new (Step 1) to authorize adding your first method (TOTP or SMS).Step 3: Activate the method
Logging In with 2FA
If your account has 2FA enabled and your session key has expired, usetfa login to re-authenticate:
~/.config/vastai/vast_tfa_key. The CLI uses this session key for subsequent authenticated requests. If this file is deleted or the session expires (returns a 404), run tfa login again.
Managing Methods
View current status
Update a method
vastai tfa status.
Delete a method
Backup Codes
Backup codes let you log in if you lose access to your 2FA device. Each code is one-time use.Regenerate backup codes
Session Key Lifecycle
After a successfultfa login, a session key is saved to ~/.config/vastai/vast_tfa_key (or $XDG_CONFIG_HOME/vastai/vast_tfa_key if XDG_CONFIG_HOME is set). The CLI automatically uses this key for authenticated requests. The session key expires after inactivity. When it expires, affected CLI commands return a 404 error. Run vastai tfa login to get a new session key.
Error Reference
See Also
- API Reference: Two-Factor Authentication endpoints — REST API 2FA documentation
- Authentication — API key setup and management