Theme My Login Action

When the backup/restore command is executed for the first time, if the device is not already bound locally, the CLI pauses and prompts to complete the authorization in the browser. You can also take the initiative to execute the login command.

View Version

peppykeep --version

Example output:

peppykeep 26.7.836+20260716152959

Login (using cached credentials)

peppykeep login --config-home ~/.peppykeep/conf

When logged in and the credentials are valid:

Action = auth login
Status = SUCCESS
AuthState = CACHED

Refresh Login/Device Bindings

When you need to rebind or refresh the authorization:

peppykeep login --refresh --config-home ~/.peppykeep/conf

Example output:

Action = auth login
Status = REQUIRED
OpenUrl = https://www.peppykeep.com/console/device/binding?auth_session_id=...
ManualCodeUrl = https://www.peppykeep.com/console/device/code/
DeviceCode = XXXX-XXXX-XXXX-XXXX

Follow these steps to bind this device:

1. Open this link in your desktop browser
   https://www.peppykeep.com/console/device/code/

   Or open official site:
   Login -> Console -> Devices -> Bind a new device

2. Enter this device code
   XXXX-XXXX-XXXX-XXXX

Waiting for device authorization...
Status = AUTHORIZED

Action = auth login
Status = SUCCESS
AuthState = LOGGED_IN
CachePath = /path/to/user/.peppykeep/auth/license_bundle.enc

Once the binding is complete, the interrupted backup/restore command will continue to execute automatically. Do not share DeviceCode with others.