Mr.PlanB Logo

    Proxmox Helper Scripts

    Search, copy, and run current Community Scripts for Proxmox VE. LXC containers, virtual machines, PVE host tools, media servers, networking utilities, monitoring software, databases, and popular self-hosted applications.

    Browse the official directoryBack to Proxmox guides

    Last reviewed: August 15, 2026. Every command and official-page link on this page was re-checked against the upstream repository on that date.

    Compatibility: the Community Scripts project currently lists Proxmox VE 8.4, 9.0, 9.1, and 9.2 in its repository requirements. Individual scripts can still have separate requirements, active bugs, or temporary compatibility issues. Always check the official script page before running a command on a host you care about.

    Most popular Proxmox Helper Scripts

    Good starting points if you are setting up a new Proxmox host or building a self-hosted stack.

    ScriptTypeBest for
    PVE Post InstallPVERepositories, updates, and initial host setup
    DockerLXCContainers and Compose workloads
    Home Assistant OSVMHome automation
    Plex Media ServerLXCMedia streaming
    JellyfinLXCOpen-source media streaming
    ImmichLXCPhoto and video backup
    Pi-holeLXCDNS ad blocking
    TailscaleAddonSecure remote access
    VaultwardenLXCPassword management
    Uptime KumaLXCService monitoring

    What are Proxmox Helper Scripts?

    Proxmox Helper Scripts are community-maintained shell scripts that automate common deployment and management tasks on Proxmox VE. A script can create an LXC container or VM, assign resources, install an application, configure networking, and apply sensible defaults from one command launched in the Proxmox VE host shell.

    The original collection became widely known through tteck. The project is now maintained by the Community Scripts organization, which continues to add and update scripts. If an older tutorial points to a legacy tteck URL or an old GitHub path, check the current script page before running it — repository paths change as the project evolves.

    How the workflow usually works

    1. Open the Proxmox VE host shell.
    2. Copy the current command from the official Community Scripts page.
    3. Review the script source if the system matters to you.
    4. Run the command as root.
    5. Choose Default or Advanced settings when the script offers them.
    6. Let the script create the LXC, VM, or host configuration.
    7. Open the new service and finish any application-specific setup.

    Showing 31 of 31 scripts

    PVE Post Install

    PVE
    System

    Run this after installing Proxmox VE to review repositories, optionally configure the no-subscription repository, update the host, and apply common post-install settings.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/post-pve-install.sh)"
    Official script pageView source

    PVE Kernel Clean

    PVE
    System

    Remove older unused kernel images to tidy the boot menu and recover space on the boot partition.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/kernel-clean.sh)"
    Official script pageView source

    PVE LXC Updater

    PVE
    System

    Update the operating systems inside multiple LXC containers from the Proxmox host in one pass.

    Run in: Proxmox VE host shell

    This updates the container OS. It does not necessarily update the application installed inside each LXC.
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/update-lxcs.sh)"
    Official script pageView source

    Docker

    LXC
    System

    Create a lightweight Linux container with Docker and Docker Compose ready for self-hosted workloads.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docker.sh)"
    Official script pageView source

    Portainer

    Addon
    System

    Add Portainer's browser-based Docker management UI to a container that already runs Docker.

    Run in: existing LXC console

    This is an addon, not a container-creation script. Run it inside an existing Docker LXC console (Debian, Ubuntu, or Alpine), not on the Proxmox host.
    bash <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/portainer.sh)
    Official script pageView source

    Plex Media Server

    LXC
    Media

    Deploy Plex Media Server in an LXC container. Hardware transcoding can need extra host and container configuration depending on your GPU.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/plex.sh)"
    Official script pageView source

    Jellyfin

    LXC
    Media

    Deploy the open-source Jellyfin media server for movies, TV, music, and other local media.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyfin.sh)"
    Official script pageView source

    Immich

    LXC
    Media

    Deploy Immich for self-hosted photo and video backup with mobile app support.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/immich.sh)"
    Official script pageView source

    Sonarr

    LXC
    Media

    Deploy Sonarr for automated TV library management and download client integration.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/sonarr.sh)"
    Official script pageView source

    Radarr

    LXC
    Media

    Deploy Radarr for automated movie library management.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/radarr.sh)"
    Official script pageView source

    Prowlarr

    LXC
    Media

    Deploy Prowlarr to manage the indexers used by Sonarr, Radarr, and related applications.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/prowlarr.sh)"
    Official script pageView source

    Seerr

    LXC
    Media

    Deploy Seerr for media discovery and request management alongside Plex, Jellyfin, and the ARR stack.

    Run in: Proxmox VE host shell

    Seerr is the currently listed request-management script. Older guides point to Overseerr or Jellyseerr, which no longer have official Community Scripts pages.
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/seerr.sh)"
    Official script pageView source

    qBittorrent

    LXC
    Media

    Deploy qBittorrent with its web interface in a dedicated container.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/qbittorrent.sh)"
    Official script pageView source

    Pi-hole

    LXC
    Networking

    Run network-wide DNS-based ad and tracker blocking in a lightweight LXC.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pihole.sh)"
    Official script pageView source

    AdGuard Home

    LXC
    Networking

    Deploy AdGuard Home for DNS filtering, blocking, and network-level privacy controls.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/adguard.sh)"
    Official script pageView source

    Nginx Proxy Manager

    LXC
    Networking

    Deploy a web-managed reverse proxy for routing services and handling HTTPS certificates.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"
    Official script pageView source

    WireGuard

    LXC
    Networking

    Create a WireGuard LXC for a lightweight encrypted VPN. The official page also offers WGDashboard as an optional component.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/wireguard.sh)"
    Official script pageView source

    NetBird

    LXC
    Networking

    Deploy the NetBird client in an LXC to connect a Proxmox-hosted workload to an existing NetBird network.

    Run in: Proxmox VE host shell

    After installation, enter the container and authenticate it to your NetBird network using the setup method NetBird documents.
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/netbird.sh)"
    Official script pageView source

    Tailscale

    Addon
    Networking

    Install Tailscale into an existing supported LXC. This is an addon, so it differs from scripts that create a brand-new application container.

    Run in: Proxmox VE host shell

    Run this from the Proxmox host shell and pick the target container. Afterwards, reboot that LXC and run tailscale up inside its console.
    bash <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/add-tailscale-lxc.sh)
    Official script pageView source

    RustDesk Server

    LXC
    Networking

    Deploy a self-hosted RustDesk Server for remote desktop discovery and relay services.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/rustdeskserver.sh)"
    Official script pageView source

    Uptime Kuma

    LXC
    Monitoring

    Deploy Uptime Kuma for uptime checks, status monitoring, and notifications.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/uptimekuma.sh)"
    Official script pageView source

    Grafana

    LXC
    Monitoring

    Deploy Grafana for dashboards and infrastructure visualization.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/grafana.sh)"
    Official script pageView source

    Prometheus

    LXC
    Monitoring

    Deploy Prometheus for metrics collection, time-series storage, and alerting workflows.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/prometheus.sh)"
    Official script pageView source

    InfluxDB

    LXC
    Databases

    Deploy InfluxDB for time-series data, commonly paired with Grafana for infrastructure telemetry.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/influxdb.sh)"
    Official script pageView source

    Vaultwarden

    LXC
    Security

    Deploy a lightweight Bitwarden-compatible password manager server.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)"
    Official script pageView source

    NextcloudPi

    LXC
    Utilities

    Deploy NextcloudPi, the container route to Nextcloud file sync, sharing, calendars, and collaboration.

    Run in: Proxmox VE host shell

    The official page warns that this installer sources scripts from outside the Community Scripts repository, so review the source first. If you want plain Nextcloud rather than NextcloudPi, use the Nextcloud VM script instead.
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nextcloudpi.sh)"
    Official script pageView source

    Nextcloud VM

    VM
    Utilities

    Create a full Nextcloud virtual machine when you would rather run it with its own kernel than inside a container.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/nextcloud-vm.sh)"
    Official script pageView source

    PostgreSQL

    LXC
    Databases

    Deploy PostgreSQL in a dedicated Linux container.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/postgresql.sh)"
    Official script pageView source

    Homepage

    LXC
    Utilities

    Deploy Homepage as a customizable dashboard for organizing self-hosted applications and infrastructure links.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homepage.sh)"
    Official script pageView source

    Node-RED

    LXC
    Home Automation

    Deploy Node-RED for visual automation flows, API integration, IoT workflows, and event processing.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/node-red.sh)"
    Official script pageView source

    Home Assistant OS

    VM
    Home Automation

    Create a Home Assistant OS virtual machine from the official KVM image.

    Run in: Proxmox VE host shell

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/haos-vm.sh)"
    Official script pageView source

    LXC or VM: which should you use?

    LXC containers share the host Linux kernel, so they are usually lighter than full virtual machines and work well for always-on Linux services, dashboards, media tools, DNS services, databases, and monitoring. A VM includes its own guest operating system and kernel, so it suits workloads that need stronger isolation, a different operating system, VM-specific drivers, or behaviour that does not fit inside a container.

    1. Start with LXC for straightforward Linux services.
    2. Use a VM when the application's requirements make LXC awkward.
    3. Use a VM for Windows workloads.
    4. Consider isolation and recovery requirements before optimizing only for resource usage.

    The right answer also depends on your storage, networking, GPU requirements, backup strategy, and how much manual troubleshooting you are willing to own.

    Before running a Proxmox Helper Script

    Helper scripts are convenient because they automate privileged infrastructure changes. Treat every one of them as code that can alter your Proxmox environment.

    • →Open the official script page before running the command.
    • →Review the source when the host or workload is important.
    • →Confirm the command is meant for the Proxmox VE host shell.
    • →Confirm your Proxmox version is supported, and check the script page for warnings.
    • →Back up important workloads before system-level changes.
    • →Test unfamiliar automation away from production when practical.
    • →Do not keep using an old command simply because it worked last year.
    Helper Scripts or Hidden Risks?Proxmox backup strategy

    Proxmox Helper Scripts not working?

    A helper script can fail because the upstream file moved, the command is being run in the wrong shell, the host cannot reach the source, the script expects root privileges, or a Proxmox or application update introduced a temporary problem.

    The command returns 404

    The source path may have changed. The PVE Post Install script, for example, used to live at misc/post-pve-install.sh and now lives at tools/pve/post-pve-install.sh. Do not guess the new path — open the official directory, search for the script, and copy the current command.

    The script produces no useful output

    Check basic host connectivity first with curl -I https://community-scripts.org, then verify DNS resolution and confirm the raw script URL still exists. Do not repeatedly run a failing root-level command without first checking what it is downloading.

    You are running the command in the wrong place

    Most creation scripts start in the Proxmox VE host shell. Addons are the exception — some are meant to run inside an existing container's console. Each card above states where its command belongs.

    Permission denied, or root is required

    Most Proxmox creation scripts need root because they create guests, allocate storage, configure networking, and change host-level settings. If you are on a restricted shell account, switch to an appropriate administrative workflow rather than trying to bypass permission checks.

    Your Proxmox version is unsupported

    The Community Scripts repository currently lists Proxmox VE 8.4, 9.0, 9.1, and 9.2 in its requirements. That does not guarantee every script is problem-free on every patch release. Open the individual script page and check its notes, recent changes, and active issues.

    The guest was created, but the application is broken

    Separate infrastructure problems from application problems. If the container or VM was created correctly but the application fails to start or update, check the Community Scripts page for that application, the upstream project's documentation, the Community Scripts issue tracker, the service logs inside the guest, and recent application release notes.

    What happened to tteck Proxmox Helper Scripts?

    The original Proxmox Helper Scripts collection was created and maintained by tteck. After his passing in 2024, community maintainers continued the work under the Community Scripts organization.

    That matters when you follow older tutorials. A command that points to the old repository or an old directory can be obsolete even if the article still ranks well in Google. For current commands, start with the official sources:

    Community Scripts directoryProxmoxVE repository

    Frequently asked questions

    Are Proxmox Helper Scripts safe?

    They are widely used and useful, but they run privileged automation against your infrastructure. Check the source, use the official project rather than a copied command from an old article, keep backups, and test important changes before applying them to production systems.

    Do Proxmox Helper Scripts work with Proxmox VE 9.2?

    The Community Scripts repository currently lists Proxmox VE 8.4, 9.0, 9.1, and 9.2 among its supported versions. Individual scripts can still have temporary issues, so check the specific script page before deployment.

    Do I need root access?

    Most scripts that create LXCs or VMs, or that change the PVE host, are intended to run from the Proxmox VE host shell with administrative privileges.

    Should I run the script in the PVE shell or inside the LXC?

    For creation scripts, start from the Proxmox VE host shell. Addons vary: the Tailscale addon runs on the host and asks which container to target, while the Portainer addon runs inside an existing container's console. Always check the official page for the specific script.

    Can I customize CPU, RAM, storage, and networking?

    Many Community Scripts offer Default and Advanced installation modes. Advanced mode generally gives more control over guest resources and configuration before deployment, and you can adjust most VM and LXC settings afterwards through the Proxmox interface.

    Should I use LXC or a VM?

    Use LXC for lightweight Linux services where efficiency matters. Use a VM when you need a separate kernel, another operating system, stronger isolation, or application requirements that do not fit well in a container.

    Why did an old Helper Script command stop working?

    The repository changes over time. Files move, scripts get renamed or superseded, and old tutorials keep stale paths. Overseerr and AdGuard Home are both examples where the path or name changed. Open the current official script page and copy its install command.

    Can I automate Helper Scripts with Ansible?

    Yes, though interactive scripts need care if you want repeatable unattended automation. For broader host and guest maintenance, configuration management usually gives clearer version control and repeatability.

    Related Proxmox guides

    Proxmox guidesProxmox backup strategyProxmox automation with AnsibleHelper Scripts or Hidden Risks?Proxmox 9.1 OCI Containers

    About this directory

    Mr.PlanB does not maintain or publish the Community Scripts project. This page is a curated directory designed to make useful scripts easier to discover, with clearer LXC, VM, PVE, and addon classification, direct source links, safety guidance, compatibility context, and troubleshooting.

    Page review date: August 15, 2026. Because upstream scripts can change at any time, the official Community Scripts page for each application remains the source of truth for the current command.