ProxSave
Star on GitHub, it's really important Star on GitHub

How to Request Support

ProxSave support works best when you include enough context to reproduce the issue and correlate it with a specific build.

The workflow is:

  1. Open a GitHub issue with the required information.
  2. If needed, run Support mode (--support) to send the full debug log to the developer.

Support channels

What to include in every report

1) Version + build signature

Copy/paste the header printed by ProxSave at startup, for example:

===========================================
  ProxSave - Go Version
  Version: 0.11.2
  Build Signature: 60d0d998f* (2025-12-02T14:46:14+01:00) hash=eeb72ef6b8b6ad89
===========================================

2) Proxmox type and version

Include whether you are running on PVE or PBS and the detected version (ProxSave prints this early in the run).

3) Clear reproduction steps

  • What you ran (the exact command line)
  • What you expected to happen
  • What actually happened
  • Whether it reproduces consistently

4) Logs

For most issues, run a dry-run with debug logging and attach/copy the relevant part of the log:

proxsave --dry-run --log-level debug

ProxSave writes logs under LOG_PATH (example filename: backup-<hostname>-YYYYMMDD-HHMMSS.log) and also prints the log path during the run.

If proxsave is not available directly as a terminal command, run it via the full path to the binary (example: /opt/proxsave/build/proxsave).

Sensitive data and redaction

ProxSave does not intentionally log secrets, but logs and config files can still contain sensitive information such as:

  • hostnames, IPs, paths, and filenames
  • Telegram bot tokens (TELEGRAM_BOT_TOKEN)
  • Gotify tokens (GOTIFY_TOKEN)
  • Webhook URLs and auth tokens (WEBHOOK_*_URL, WEBHOOK_*_AUTH_*)
  • any custom headers you configured for webhooks

Never post private keys (for example AGE secret keys) in issues or chats.

If you need to share configuration, prefer a redacted excerpt of configs/backup.env with secrets replaced (for example ***REDACTED***).

Support mode (send full debug log)

Support mode runs a normal backup with forced DEBUG logging and emails the complete log to github-support@tis24.it.

proxsave --support

Support mode is interactive and requires:

  • your explicit consent (the log may contain sensitive information)
  • an existing GitHub issue (you will be asked to confirm it)
  • your GitHub nickname and issue number (format #1234)
  • a working local sendmail setup (Support mode uses sendmail delivery)

After the run, ProxSave prints the local log file path so you can review it before/after sending.

Issue template (copy/paste)

Summary:
Version / Build Signature:
Proxmox type + version (PVE/PBS):
Command(s) run:
Expected behavior:
Actual behavior:
Reproduction frequency:
Relevant logs (or attach log file):
Anything else relevant (storage tiers, encryption, notifications enabled):