PVE Guard Help

Connection refused / timeout

• Make sure your iPhone is on the same network as the Proxmox server, or that the server is reachable from your current network.
• Verify the URL includes the correct port (default: 8006).
• Check that the Proxmox web UI is accessible in your browser at the same URL.
• If using a firewall, ensure port 8006 (TCP) is open.

Authentication failed (401)

• Double-check the API Token ID format: user@realm!tokenid (e.g. root@pam!pveguard).
• Verify the Token Secret is correct — it is only shown once when created.
• If the token was recently created, try refreshing the Proxmox web UI to confirm it exists.
• Make sure "Privilege Separation" is configured as intended.

Certificate errors

Proxmox uses self-signed certificates by default. PVE Guard handles this, but issues can occur:

• First connection: PVE Guard will ask you to trust the certificate. Tap Trust to proceed.
• Certificate changed: If you replaced the Proxmox certificate (e.g. with Let's Encrypt), you may need to reconnect or re-add the server.
• Intermediate proxies: If a reverse proxy sits in front of Proxmox, make sure it passes the correct certificate chain.

Missing VMs or containers

• The API token may lack permissions to see all resources. Use a token with the PVEAuditor role on / (root path) for full read access.
• Templates are hidden by default — they are not shown in the guest list.

Cannot start/stop VMs

VM actions require write permissions. A token with the PVEAuditor role can only monitor. Use a token with PVEAdmin or Administrator role, or disable "Privilege Separation" on a root@pam token.

Notifications not working

• Make sure notifications are enabled in the iOS Settings for PVE Guard.
• Check that background refresh is enabled: Settings → General → Background App Refresh → PVE Guard.
• iOS may delay background checks. With the app open, notifications arrive within minutes.

Still stuck?

Contact us at support@hans-renz.de with a description of the issue and any error messages you see.