More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    VPS Recovery and Data Rescue

    1

    When a VPS stops booting or its services become unavailable, acting too quickly can overwrite the data needed for recovery.

    $19.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    VPS Recovery and Data Rescue

    VPS Recovery and Data Rescue

    Example session with this skill installed

    My Hostinger VPS running Ubuntu 24.04 stopped accepting SSH after an automatic update. I can access the provider's recovery environment, and the original disk appears to be attached, but I have not identified it yet. The server runs Docker services, including n8n and MariaDB. The provider snapshot was created after the failure, so I do not know whether it is useful.

    Guide me through the safest recovery path. Start with read-only checks. Do not assume disk names, mount points, volume names, or data paths. Do not recommend reinstalling, repairing the filesystem, or writing to the original disk until we have identified the source disk and made an independent, verified copy of the required data. Ask me for sanitized command output one step at a time.

    • Read your context and instructions
    • Compiled the vps recovery

    Recovery approach

    The priority is to identify the original disk and protect its data before attempting repairs or reinstalling Ubuntu. Because the provider snapshot was created after the failure, do not restore it over the VPS until its contents and overwrite behavior are confirmed.

    I will guide you one checkpoint at a time. I cannot yet identify the original disk from the information provided, so do not mount, repair, format, or reinstall anything.

    Step 1: Inspect the recovery environment

    Run these read-only checks from the recovery environment:

    whoami
    cat /etc/os-release | head -n 5
    lsblk -o NAME,TYPE,SIZE,FSTYPE,LABEL,UUID,MOUNTPOINTS,RO
    findmnt -o SOURCE,TARGET,FSTYPE,OPTIONS
    df -h
    

    Do not copy a device name or mount point from an example. The output should let us distinguish the temporary recovery system from the original VPS disk. If you are unsure which disk is which, stop and share the sanitized output before taking another action.

    What to share

    Paste the command output here after removing public IP addresses, hostnames, usernames, tokens, passwords, and any customer data. These commands should not display application secrets, but review the output before sharing it.

    Safety checks

    Do not run fsck, mkfs, partitioning tools, or commands that mount the original disk read-write. Do not use the provider's restore or reinstall controls yet. If the disk reports I/O errors, the device mapping is ambiguous, or the filesystem type is unexpected, stop and contact the provider before proceeding.
    Once the disk is identified, the next step is to confirm whether it is mounted read-only. Then we can locate the Docker volumes and application data, create a separate recovery archive, and verify its contents and hash before considering a rebuild.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When a VPS stops booting or its services become unavailable, acting too quickly can overwrite the data needed for recovery. This skill guides you through a cautious recovery process, starting with the provider's recovery options and a read-only assessment of the original system.

    It helps you identify the disks, service data, configuration, databases, and encryption keys that matter to your recovery plan. It then guides you through creating and verifying an independent copy before you consider rebuilding the operating system. If a rebuild is appropriate, the skill helps plan administrative access, firewall rules, container or service setup, data restoration, and post-recovery checks.

    The workflow adapts to the provider, operating system, storage layout, and deployment method you confirm. A tested Hostinger and Ubuntu 24.04 Docker recovery provides a concrete reference for the sequencing and validation approach. Examples involving Docker, MariaDB, n8n, Mautic, server-side Google Tag Manager, Portainer, Nginx, age, and rclone are used only when they match your environment.

    The skill emphasizes checkpoints, verified backups, service compatibility, and explicit approval before destructive operations. It will ask you to stop when disk identity, backup integrity, credentials, or restore behavior is uncertain. It does not promise that every failed VPS can be recovered, and it does not substitute for provider support or a tested disaster-recovery plan.

    What the skill helps you do

    • Assess the failure and choose between data rescue, repair, and a controlled rebuild.
    • Use a provider-supported rescue environment to identify the original disk and protect it from writes.
    • Locate service data, databases, deployment configuration, and application-specific encryption keys.
    • Create an archive of selected recovery data and verify its contents and hash before relying on it.
    • Adapt the recovery plan to different providers, Linux distributions, storage layouts, and deployment methods.
    • Plan a rebuild with safe administrative access, SSH and firewall checkpoints, and controlled service exposure.
    • Restore services in dependency order using compatible application and database versions.
    • Validate data, credentials, application health, TLS, network bindings, and restart behavior.
    • Review backup encryption, off-host copies, retention, monitoring, and isolated restore testing.

    Intended users

    Operators, developers, and technically capable VPS owners who need structured guidance during a server outage or want to improve recovery readiness. The skill assumes the user can access a provider console or follow command-line instructions with care. It is not a replacement for a qualified administrator when data is critical or the storage system is damaged.

    Requirements

    • Access to the VPS provider account or a provider-supported recovery environment.
    • A separate destination with enough space for the recovery data.
    • The ability to run and review commands in a Linux shell, or a system administrator who can do so.
    • Any encryption keys and application secrets required for recovery, stored securely and never pasted into chat.
    • A verified address or provider console for the target VPS.
    • Permission to make changes to the server and approval from the person responsible for the service.

    Some steps depend on provider tooling, distribution-specific commands, application documentation, or access to a separate computer. The connected agent may not be able to operate the provider dashboard or local machine directly.

    Important limitations

    This skill provides interactive guidance. It does not independently access your provider account, guarantee recovery, repair a damaged filesystem, recover missing encryption keys, or restore a backup it cannot access. You or your administrator must run and verify commands in the target environment.

    Provider recovery modes, disk layouts, filesystems, firewall behavior, and panel workflows vary. Commands from the Hostinger and Ubuntu 24.04 example must not be copied to another VPS without confirming the target system. The skill may stop and recommend provider or specialist support when a disk cannot be identified safely, a filesystem reports errors, a backup is incomplete, or a restore path is untested.

    Reinstalling an operating system, formatting storage, replacing application volumes, changing firewall or SSH access, and modifying databases can cause downtime or irreversible data loss. The skill requires the user to verify prerequisites and explicitly approve high-impact actions before proceeding. It cannot guarantee the accuracy of third-party provider instructions or the compatibility of undocumented application data formats.

    Suggested tags

    VPS, Linux, server recovery, data rescue, Docker, backup, disaster recovery, SSH, system administration

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Requires provider console or rescue mode access. Cannot recover data from physically failed disks or lost encryption keys. Guidance only; does not execute commands directly.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 12 days ago

    Software
    OpenSSH clienttargzipsha256sum
    Optional
    ageDocker EngineDocker Compose

    age is only for backups encrypted with age. Docker is only for Docker deployments.

    Permissions

    Read Files
    Write Files
    Terminal / Shell

    File Scopes

    **/docker-compose.y*ml
    **/compose.y*ml
    **/nginx/**
    **/etc/letsencrypt/**
    **/var/lib/docker/volumes/**

    File access is used only to inspect recovery-relevant configuration and data paths when the connected agent has authorized local access. These files may contain credentials, private keys, customer data, or application secrets. Do not display or transmit secret values. Ask the user to redact sensitive output. Read original disks in read-only mode where supported. Do not modify, overwrite, or delete files without explaining the impact and obtaining explicit user approval. The skill guides the user and does not automatically access the VPS provider account.

    Listed12 days ago

    What's inside

    Frequently Asked Questions

    It guides you through assessing a VPS failure, identifying and protecting important data, verifying recovery copies, planning a rebuild when appropriate, restoring services, and checking the result. It provides step-by-step instructions and safety checkpoints based on the environment you confirm.

    No. The skill provides guidance and asks you or your administrator to run and verify commands. It does not access your VPS or provider account by default. Reinstallations, database changes, file replacement, firewall changes, and other high-impact actions require clear warnings and your explicit approval before proceeding.

    The workflow is designed to adapt to different VPS providers and Linux environments, but provider recovery procedures and system commands vary. The detailed reference scenario uses Hostinger, Ubuntu 24.04, and Docker. That example is not a guarantee of compatibility with every provider, distribution, storage layout, or service.

    Yes. It can guide you through identifying Docker volumes, bind mounts, Compose configuration, database dependencies, and application versions, then planning a staged restore. The exact steps depend on your deployment. Docker data should not be overwritten or services started against empty volumes until the recovery plan is confirmed.

    You need authorized access to the VPS or its provider-supported recovery environment, plus a way to store a separate copy of recovered data. Depending on the situation, you may also need an administrator who can run Linux commands, the backup decryption key, and application-specific credentials. Never paste passwords, private keys, or tokens into chat.

    The skill follows a structured recovery workflow with environment checks, data-protection steps, verification checkpoints, and clear stop conditions. It prioritizes making and checking an independent data copy before recommending a rebuild. It does not guarantee recovery or replace provider support or a qualified administrator when the disk, filesystem, or backup is at risk.

    New in DevOps & Cloud