Manage SSH Key Pairs in UAPP
Review stored SSH key metadata, view or download key files, manage login authorization and understand deletion scope in UAPP.
Open SSH → SSH Key Pairs. Access requires shell access or permitted backup user-pool key management.
Review keys
The page reports key names, available public/private files, algorithm, bit count, fingerprint, comment and creation metadata where available. Search and filtering help locate a key. Summary counts include algorithm families and, with shell access, authorization state.
Authorization is matched by the public-key data rather than its comment. The status reports whether that public key is found in the account's authorization list; it is not a successful SSH connection test.
View or download
Use the public or private file actions to open the content dialog, copy content or download a key. Verify the key name and type before copying. Views and downloads are blocked in demo mode.
A missing metadata field or an empty listing can reflect an inspection error; ask the provider to investigate before replacing keys.
Authorize or deauthorize
With shell access, select the authorization action for a public key and confirm the intended change. This adds or removes its public-key entry in this account's authorized-key list. Backup-only key access does not permit this action.
Deauthorization revokes this entry; it does not delete the stored pair or remote authorizations. Keep another working access method before revoking the key you use.
Connection details
When shell access is enabled, connection help uses the panel hostname, account username and server SSH port. The port helper falls back to 22 when it cannot retrieve a valid port. Verify the actual connection address and port with the provider if these details do not work.
Do not assume downloading a private key alone establishes login permission or bypasses server policy.
Delete a key pair
Select the delete action, verify the key name and confirm. Deletion removes the stored private file and its corresponding .pub file. It does not edit the authorized-key list.
Deletion is not revocation
Removing local key files can break outbound backups or other consumers while copies of the key may remain authorized. Revoke authorization separately where required, and check dependent storage pools before deleting.
Refresh after changes and test the intended connection separately. Creation, deletion and authorization changes are blocked in demo mode.