ProxMenux LogoProxMenux

Post-Install Scripts

Settings post-install Proxmox~3 minView script

Configure a fresh Proxmox VE host with ProxMenux's post-install optimizations. Apply the baseline automatically, choose individual options, update installed functions or restore supported reversible changes. Package upgrades are not presented as reversible.

What this menu is for

Right after installing Proxmox VE, there are dozens of small changes that make the host faster and easier to maintain — free repositories, sane journald limits, sensible TCP buffers, SSD-friendly log storage, bashrc niceties, and more. ProxMenux automates them and tracks the supported reversible configuration changes.

Opening the menu

From ProxMenux's main menu, select Settings post-install Proxmox. You will see this:

Post-Installation Scripts menu — Automated, Customizable, the conditional Apply Available Updates (only when updates are pending), and Uninstall, followed by the Community Scripts section

Four ways to apply optimizations

The four ProxMenux entries share the same underlying code and the same registry of installed tools — they just give you different levels of control. The Apply Available Updates entry only shows when at least one installed optimization has a newer version on disk than what is registered; on a freshly applied host it stays hidden.

Automated

A curated set of 14 safe, always-useful optimizations applied in sequence with zero prompts. Good default for most users.

  • Free repos + system upgrade
  • Memory, kernel, network tuning
  • Log2RAM (auto-detected on SSD/NVMe)
  • Journald + logrotate size limits
  • Persistent interface names

Customizable

~35 individual optimizations across 10 categories. You pick exactly which ones to apply. Same engine as Automated, but with full control.

  • Checklist UI per category
  • Includes everything Automated does, plus opt-in items (IOMMU, Fastfetch, Figurine, Ceph, HA, AMD fixes…)
  • Run as many times as you want — changes are idempotent

Apply Available Updates

When a post-install optimization (Log2Ram, Memory Settings, Logrotate…) gets a newer version on disk than what is registered on the host, this entry surfaces only the ones that moved. Re-runs the corresponding function and refreshes the registry — touches nothing else.

  • Per-optimization opt-in (only what changed)
  • Same picker available from the Monitor dashboard
  • Single grouped notification when new updates land

Uninstall Optimizations

Supported reversible changes are tracked in a JSON registry and paired with a restoration function. Actions without a safe rollback, such as a full package upgrade, are intentionally excluded.

  • Detects previously applied optimizations automatically
  • Reversal picks the right path for each item — restores from a .bak backup where one was made, deletes the sysctl.d snippet where nothing needed backing up, or reinstalls the vanilla package with --force-confnew (e.g. subscription banner)
  • Reboot prompt if needed (VFIO, persistent names, etc.)

Which one should you pick?

If this is a fresh Proxmox install and you want the sensible baseline with no decisions: Automated. If you already know which tweaks you want (or which you definitely don't want): Customizable. If something you already applied has a newer version on disk and you want to lift only that: Apply Available Updates. If you applied something earlier and want to back it out cleanly: Uninstall Optimizations. You can mix them — apply Automated first, then open Customizable to add opt-ins like Fastfetch or IOMMU, and revert any individual item later.

Mixing with other post-install scripts

Don't stack multiple post-install scripts

Running several post-install scripts on the same host can cause duplicated configuration files, conflicting sysctl entries, or worse — broken networking after reboot. If you already applied the Helper-Scripts Post Install, some ProxMenux optimizations may overlap with what it already configured. Stick to one post-install tool per host.

xshok-proxmox: deprecated

Earlier versions of ProxMenux referenced xshok-proxmox as a companion post-install tool. That project is now deprecated and no longer offered from ProxMenux. If a previous run of xshok-proxmox left markers on the host, ProxMenux still detects them and will warn you — but it is not something you should install alongside ProxMenux today.

Community scripts

The menu also exposes two third-party scripts from the community-scripts project: Proxmox VE Post Install and Proxmox VE Microcode. These are wrappers that wget | bash the original authors' scripts. They are not maintained by ProxMenux. See External Repositories for details and trust considerations before running them.

Related

ProxMenux Monitor: Previous
Integrations
ProxMenux Scripts: Next
Automated