CanbiZ (MickLesk)
8854585a1a
* Move the top 25 scripts onto the core engine The engine work of the last few days reaches 30 of 561 ct scripts, about 5% of ProxmoxVE traffic: retry on engine downloads, exit 227 instead of a misfiled dpkg error, the umask fix that stops a hardened host producing containers apt cannot resolve in, the TMPDIR guard, the toolchain restore. All of it has been sitting where almost nobody runs it. All eighteen at once rather than in waves. A slow rollout does not exercise the paths only some scripts take, and broad exposure is what surfaces bugs -- a deliberate call about release risk. Checked before touching anything, because "migrate" meant far more than a line swap last time: - None of the eighteen has an alpine-* variant, so there is no merge to do. - No script references misc/ outside its bootstrap line. - Of the 61 functions that exist only in misc/, none is called by any of them. So it is one line per script, and every head is now byte-identical to the ones migrated earlier. With these, ProxmoxVE goes from 30 scripts on the core engine to 48 -- and from roughly 5% of traffic to the majority, since these are the ones people actually install. Two to watch: immich sits at 44.7% success and vaultwarden at 42.1% before this. If their numbers move, the engine is one of two changed variables rather than the only one. * Move update-apps onto the core engine Entry 11 of the list and the only one that is not a ct script, so it was left out of the previous commit. It is a host tool: it never used build.func at all, it sources misc/core.func and misc/api.func directly. The swap is therefore two lines rather than one, and worth checking rather than assuming. It uses exactly five engine functions -- header_info, init_tool_telemetry, msg_info, msg_ok, msg_error -- all present in the core, and both files load standalone, which they had not had to do before: everywhere else they arrive through build.func. That completes the list. All 25 now run on the core engine. Fixing this one matters beyond the migration: update-apps is what drives unattended updates across every container on a host, and it is the path where PHS_SILENT was being ignored (#16593). It now gets the engine that honours it.
Proxmox VE Helper-Scripts
One-command installations for services, containers, and VMs on Proxmox VE
A community project — built on the foundation of @tteck's original work
What is this?
Simplify your Proxmox VE setup with community-driven automation scripts.
Install and configure popular self-hosted services with a single command — no manual package hunting, no config file archaeology. Paste a command into your Proxmox shell, answer a few prompts, and your container or VM is up and running.
The collection covers hundreds of services across categories like home automation, media servers, networking tools, databases, monitoring stacks, and more.
Requirements
| Component | Details |
|---|---|
| Proxmox VE | Version 8.4, 9.0, 9.1, or 9.2 |
| Host OS | Proxmox VE (Debian-based) |
| Access | Root shell access on the Proxmox host |
| Network | Internet connection required during installation |
Getting Started
The fastest way to find and run scripts:
- Go to community-scripts.org
- Search for the service you want (e.g. "Home Assistant", "Nginx Proxy Manager", "Jellyfin")
- Copy the one-line install command from the script page
- Open your Proxmox Shell and paste it
- Choose between Default or Advanced setup and follow the prompts
Each script page documents what the container includes, default resource allocation, and post-install notes.
How Scripts Work
Every script follows the same pattern:
Default mode — Picks sensible resource defaults (CPU, RAM, storage) and asks only the minimum required questions. Most installs finish in under five minutes.
Advanced mode — Gives you full control over container settings, networking, storage backends, and application-level configuration before anything is installed.
After installation, each container ships with a post-install helper accessible from the Proxmox shell. It handles common tasks like:
- Applying updates to the installed service
- Changing application settings without manually editing config files
- Basic troubleshooting and log access
What's Included
The repository covers a wide range of categories. A few examples:
| Category | Examples |
|---|---|
| Home Automation | Home Assistant, Zigbee2MQTT, ESPHome, Node-RED |
| Media | Jellyfin, Plex, Radarr, Sonarr, Immich |
| Networking | AdGuard Home, Nginx Proxy Manager, Pi-hole, Traefik |
| Monitoring | Grafana, Prometheus, Uptime Kuma, Netdata |
| Databases | PostgreSQL, MariaDB, Redis, InfluxDB |
| Security | Vaultwarden, CrowdSec, Authentik |
| Dev & Tools | Gitea, Portainer, VS Code Server, n8n |
Browse the full list at community-scripts.org/categories — new scripts are added regularly.
Contributing
This project runs on community contributions. Whether you want to write new scripts, improve existing ones, or just report a bug — every bit helps.
Where to start
| I want to… | Go here |
|---|---|
| Add a new script | ProxmoxVED — new scripts are tested here first |
| Fix or improve an existing script | Contributing Guidelines — open a PR in this repo |
| Report a bug or broken script | Issues |
| Request a new script or feature | Discussions |
| Report a security vulnerability | Security Policy |
| Get help or chat with other users | Discord |
Before you open a PR
- New scripts go to ProxmoxVED, not here. PRs with new scripts opened directly against this repo will be closed.
- Bug fixes and improvements to existing scripts belong in this repo — read the Contributing Guidelines first.
- Keep PRs focused. One fix or feature per PR.
- Document what your script installs and any non-obvious decisions in the corresponding JSON metadata file.
Core Team
 MickLesk |
 michelroegl-brunner |
 BramSuurdje |
 CrazyWolf13 |
 tremor021 |
 vhsdream |
 asylumexp |
Project Activity
Support the Project
This project is maintained by volunteers. All infrastructure costs come out of pocket, and the work is done in people's spare time.
30% of all donations are forwarded directly to cancer research and hospice care — a cause that was important to tteck.
License
This project is licensed under the MIT License — free to use, modify, and redistribute for personal and commercial purposes.
See the full license text in LICENSE.
Maintained and expanded by the community · In memory of tteck
Proxmox® is a registered trademark of Proxmox Server Solutions GmbH