Search results

Great!

yes

(EDIT: it seems indeed file truncation ...) I've indagated furthermore, and what seemed file truncation is a file corruption, unrelated to file size (probably big files have more chances to be read as corrupted). # find virtio-win-0.1.221 -size +8M | while read f; do diff -qr...

I have tried to switch my repo to Proxmox Backup Client Repository ... which resulted in a downgrade to client version: 2.2.1 No difference. I tried the .pxar mount with client version: 2.2.4 (pve enterprise repository) on a pve node; same behaviour.

The vm is debian 11 Filesystem on vm: ext4 proxmox-backup-client package version (from dpkg -l): 2.2.5-1 - repo: pve-no-subscription # proxmox-backup-client version client version: 2.2.5

I backup a filesystem tree inside a vm, then using proxmox-backup-client mount i tried to compare the original tree with the mounted backup. The filesystem I mounted is the content of a virtio .iso (virtio-win-0.1.221.iso). Original tree: /opt/restore/bigfs/virtio-win-0.1.221/ Mounted backup...

Hello, I'm currently trying to backup/restore on pbs some nfs-ganesha mounts. Currently I set up two mounts, one with a VFS backend and the other with RGW backend, both exported from a PVE cluster with ceph storage and radosgw configured. I setup a vm on the same cluster, which mounts both...

Note that no fingerprint is needed in pbs storage config, if the root is trusted by pve host.

Problem resolved, I report here my comment 2 in bug 4207:

Opened https://bugzilla.proxmox.com/show_bug.cgi?id=4207

If you want, send me a csr and i will generate a short lived cert for your test ... PS: Maybe is worthwhile to open an issue for this?

Chain. Three levels, excluding root. I tried to include the root as well, but it makes no difference.

These are quite common for web server certificates ... Will try this evening, I have not the privkey at hand now.

I tried generate a self signed cert (chain with only 1 cert) and it works. May be there is some problem in chain verification?

Certificate: Data: Version: 3 (0x2) Serial Number: 56 (0x38) Signature Algorithm: sha256WithRSAEncryption Issuer: C = IT, O = Comune di Trento, OU = Servizio Sistema informativo, CN = Comune di Trento Component CA Validity Not Before: Aug...

Here's the result of a curl connection test (without -k because the root is in my trusted certs list) $ curl -v https://REDACTED_HOST:8007 * Trying REDACTED_IP:8007... * Connected to REDACTED_HOST (REDACTED_IP) port 8007 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile...

I checked the sha-256 fingerprint of my custom cert with openssl, and it is identical to the fingerprint copied from pbs dashboard.

The pbs storage addition seems succesful at first, but the storage icon has a question mark, and browsing the storage for backup listing gives the error in the first message here. Same message in syslog.

Hello @fabian , just tried on a test server (pbs 2.2-1, error connecting it as a storage from pve 7.2-4). Same error. How can I provide you the cert?

I can provide cert and chain, but may be is more productive if I do a new attempt on a test server.