Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/troubleshooting/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ All service widgets work essentially the same, that is, homepage makes a proxied

1. URLs should not end with a / or other API path. Each widget will handle the path on its own.

2. All services with a widget require a unique name.
2. All services with a widget require a unique name as well as a unique group (and all subgroups) name.

3. Verify the homepage installation can connect to the IP address or host you are using for the widget `url`. This is most simply achieved by pinging the server from the homepage machine, in Docker this means _from inside the container_ itself, e.g.:

Expand Down
3 changes: 3 additions & 0 deletions docs/widgets/services/proxmoxbackupserver.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ description: Proxmox Backup Server Widget Configuration

Learn more about [Proxmox Backup Server](https://www.proxmox.com/en/proxmox-backup-server/overview).

Create a user and an API token similar to the [Proxmox VE description](proxmox.md). The "Audit" role is required for both the user and token (not group).

Allowed fields: `["datastore_usage", "failed_tasks_24h", "cpu_usage", "memory_usage"]`.

```yaml
Expand All @@ -13,4 +15,5 @@ widget:
url: https://proxmoxbackupserver.host:port
username: api_token_id
password: api_token_secret
datastore: datastore_name #optional; if ommitted, will display a combination of all datastores used / total
```