Uninstall ProxMenux

Removes ProxMenux from the Proxmox host with an interactive flow: confirmation, optional dependency removal, ProxMenux Monitor service cleanup, restoration of /root/.bashrc and /etc/motd backups. Shows a progress bar throughout.

Affects the ProxMenux install only — not your VMs / CTs / storage

Uninstalling ProxMenux removes the ProxMenux scripts, the menu launcher, the optional Monitor service and any backups ProxMenux took of system files when you installed it. It does not touch your VMs, containers, storage, network configuration, Fail2Ban, NVIDIA driver or anything else you installed via ProxMenux. Those stay as they are.

The uninstall flow

Confirmation dialog. Yes/no — “Are you sure you want to uninstall ProxMenux?”
Dependency removal checklist. Pre-selected list depends on install type (see table below). All boxes default to OFF — you opt in to removing each dependency.
Removal runs with a progress bar. Removes the venv (Translation install only), the menu launcher, the /usr/local/share/proxmenux/ tree, the ProxMenux Monitor service if present, the dependencies you ticked, and finally restores the system file backups (see below).
Completion dialog. Lists removed dependencies and exits.

Dependency removal: what's offered

The checklist depends on install type. None of the boxes is checked by default — these are system-wide packages that other applications might use, so the safer default is to leave them.

Install type	Offered for removal
Translation	`python3-venv`, `python3-pip`, `python3`, `jq`
Normal	`dialog`, `jq`

System-wide packages — think twice

python3, jq and dialog are commonly used by other tools (including Proxmox itself in some workflows). Removing python3 in particular can break Proxmox helpers, Ceph utilities and many third-party scripts. Leave them unless you're positive nothing else needs them.

What gets removed

/usr/local/bin/menu                                  # the launcher
/usr/local/share/proxmenux/                          # everything: scripts, config, cache, version
/opt/googletrans-env/                                # virtual env (Translation install only)
/etc/systemd/system/proxmenux-monitor.service        # Monitor service unit
/root/.config/proxmenux-monitor/                     # Monitor config dir
                                                     # + dependencies you ticked in the checklist

What gets restored

If /root/.bashrc.bak exists → renamed back to /root/.bashrc (your original bashrc returns).
If /etc/motd.bak exists → renamed back to /etc/motd. Otherwise the ProxMenux line (“This system is optimised by: ProxMenux”) is stripped from the existing motd with sed.

Other ProxMenux-installed components stay

Anything ProxMenux installed via other menus — Fail2Ban, Lynis, NVIDIA drivers, post-install tweaks — is not touched by this uninstaller. Each has its own uninstall flow inside its respective menu (or you can remove with apt directly). Look at Show Version Information first to see what's registered.

Manual uninstall

If for some reason the menu uninstaller can't run (e.g. dialog already missing), the equivalent manual sequence:

# 1. Stop and remove the Monitor service (if installed)
systemctl stop proxmenux-monitor.service 2>/dev/null
systemctl disable proxmenux-monitor.service 2>/dev/null
rm -f /etc/systemd/system/proxmenux-monitor.service
rm -rf /root/.config/proxmenux-monitor
systemctl daemon-reload
systemctl reset-failed 2>/dev/null

# 2. Remove the venv (Translation install only)
rm -rf /opt/googletrans-env

# 3. Remove ProxMenux files
rm -f /usr/local/bin/menu
rm -rf /usr/local/share/proxmenux

# 4. Restore backups
[ -f /root/.bashrc.bak ] && mv /root/.bashrc.bak /root/.bashrc
[ -f /etc/motd.bak ] && mv /etc/motd.bak /etc/motd \
    || sed -i '/This system is optimised by: ProxMenux/d' /etc/motd

Reinstalling later

Run the official ProxMenux installer again. Pick Translation or Normal as you prefer — the choice is independent of what you had before.

Troubleshooting

Uninstall hangs at “Removing googletrans and virtual environment”

pip uninstall can stall if pip is unresponsive. From another shell: rm -rf /opt/googletrans-env directly (the script does the same as a fallback after pip).

apt warns about packages still in use during dependency removal

Expected if you ticked python3 or jq while other things on the host depend on them. apt's autoremove will refuse to remove them in that case (which is the safe behaviour). Untick that dependency and re-run.

MOTD still shows the ProxMenux line after uninstall

Either no /etc/motd.bak existed and the sed strip didn't match (e.g. the line was modified). Edit /etc/motd by hand and remove any leftover ProxMenux line.

Show Version Information — see what would be removed before uninstalling.
Settings overview.

ProxMenux Scripts: Previous

Show Version Information

Commands Reference: Next

Overview