TASK ERROR: client error (Connect) with ACME and Sync jobs

[SnowFox]

I updated my PBS to 4.2.0 at 2 weeks ago, running on 4.1.x prior.
On the surface it looks fine, backups from PVE are being made fine. However, the ACME (running on OpenBao) renewal fails:

2026-05-20T08:54:44+02:00: Placing ACME order
2026-05-20T08:54:44+02:00: skipping disabled matcher 'default-matcher'
2026-05-20T08:54:44+02:00: TASK ERROR: client error (Connect)

As a result, the certificate has expired. For now I have removed my custom cert and reverted back to the self-signed certificate generated by PBS.

Additionally, I have a sync job that syncs backups to an off-site location, this seems to be failing as well since the upgrade. Worked fine before.

2026-05-20T08:55:36+02:00: Starting datastore sync job 'local:OMV_NFS:Local::s-7f591276-4dc3'
2026-05-20T08:55:36+02:00: sync datastore 'Local' to 'local/OMV_NFS'
2026-05-20T08:55:37+02:00: queued notification (id=8c8549a0-faf7-409d-beb6-4d25f7491d6a)
2026-05-20T08:55:37+02:00: TASK ERROR: client error (Connect)

The error is not very verbose. Where is it connecting to and what "error" does it get?
Without this information it makes fixing this very hard. Can I somehow get move verbose output from this jobs?

Strangely, the "last sync" date shows today however the sync failed.

 

[Chris]

From the logs you provided this seems to be a low level connection error. Can you assure you are able to ping the remote PBS instance and the ACME renewal endpoint domain from your local PBS instance? Did you recently change network or firewall settings in your local network?

 

[SnowFox]

Managed to fix the sync issue by setting the fingerprint in the Remote config.
As I previously used ACME and had the CA certificate in the trust store this was not needed, but with ACME broken the fingerprint (obtained via proxmox-backup-manager cert info) had to be set.
I did also have to check the "Use node proxy" otherwise I wouldn't let me change the settings for the remote.

The ACME issue is probably relating to a config-change I did a few weeks ago, will have to look in to that.

It would however help if this log could provide a bit more verbosity (e.g. the host it is connecting to, the error it received).