How-to • Dynamic plan

Connect your Dynamic plan to Proxmox VE.

Five details from the billing portal, one storage dialog in Proxmox VE, one test backup. That's the whole setup — about five minutes end to end.

How Dynamic works — read this first

Dynamic is our shared tier: we run the Proxmox Backup Server, and you connect to it. There is no PBS web interface or shell access on this plan — everything you need lives in two places you already have: the OneColo billing portal (your credentials) and your own Proxmox VE interface (everything else).

If a guide tells you to "check something in the PBS UI," that's for Dedicated plans. On Dynamic, every step below happens in Proxmox VE. Pruning, verification, and server maintenance run on our side.

Step 1: Get your connection details

Log into the billing portal and open your Dynamic service. You'll find five values — you need all of them:

  • Server — the PBS hostname to connect to
  • Fingerprint — the TLS certificate fingerprint you'll confirm in Proxmox VE
  • Datastore — the name of your datastore (case sensitive)
  • Username — your backup credential
  • Password — shown in the portal; treat it like any production secret
OneColo client portal showing Proxmox Backup connection information — username, password, datastore, hostname, and fingerprint

Your connection details in the client portal — everything the Proxmox VE storage dialog asks for.

Step 2: Add the storage in Proxmox VE

In the Proxmox VE web interface: Datacenter → Storage → Add → Proxmox Backup Server. Fill the dialog from the portal:

  • ID — a name for this storage in PVE. Something obvious like onecolo-backup.
  • Server, Username, Password, Datastore — paste exactly as shown in the portal.
  • Fingerprint — paste the fingerprint from the portal. This is how PVE knows it's talking to the right server, so paste it rather than blind-trusting.
  • Content — leave VZDump backup file selected.

Prefer the command line? The same thing on any PVE node:

# values come from your billing portal service page
pvesm add pbs onecolo-backup \
  --server <server> \
  --fingerprint <fingerprint> \
  --datastore <datastore> \
  --username <username> --password '<password>'

Your Proxmox hosts connect outbound to a single port (TCP 8007). Nothing inbound is required, so no firewall changes on your side beyond allowing that outbound connection.

Step 3: Run a test backup

Pick one small VM or container, click Backup → Backup now, choose the new storage, snapshot mode, and ZSTD compression. The first backup uploads everything, so it's your slowest one ever — every backup after it is incremental and typically a small fraction of the size.

Watch the task log. You want to see it finish with TASK OK and no fingerprint or authentication warnings along the way.

Step 4: Confirm the snapshot — from Proxmox VE

Select the new storage on any node and open Backups. Your snapshot should be listed with its timestamp and size. This view is your window into everything stored on your Dynamic plan — you'll use it again for restores, so it's worth knowing where it is.

That's the setup done. Next: put backups on a schedule with retention so this happens every night without you.

Quick checks

  • Storage shows Active in the PVE storage list.
  • Test backup ends in TASK OK.
  • Snapshot visible under the storage's Backups view.
  • No fingerprint or auth warnings in the task log.

If something fails

  • Fingerprint error: re-copy it from the portal — no shortening, no spaces.
  • Auth error: re-check username and password; both are case sensitive, as is the datastore name.
  • Connection refused/timeout: confirm outbound TCP 8007 is allowed from your PVE nodes.
  • Still stuck? Contact us — you'll reach the engineers who run the server.

Not on Dynamic yet?

$6.95/month with the first 1TB included, then pay only for what you store. Provisioned the same day.

See pricing

You'll need

  • Billing portal login (billing.onecolo.com)
  • Proxmox VE admin access
  • Outbound TCP 8007 from PVE nodes
  • One small guest for a test backup