PBS 4 mega.nz as s3 endpoint - missing header: date

trevorludgate

Active Member
Jul 7, 2020
2
0
41
29
Hi,

I updated one of my backup servers to PBS4.0 to take advantage of the S3 upload feature - super happy about this!
I tested it using Backblaze B2 and I can run a sync job without issues.
I tried adding a Mega 'S4' endpoint and it adds itself successfully (needed to enable 'Path Style'). But I receive the following error when running a sync job (appears on every object):

2025-08-07T11:08:27-04:00: sync group ct/4300 failed - group lock failed: missing header 'date'
2025-08-07T11:08:27-04:00: create_locked_backup_group failed

Has anyone run into this same error? proxmox-backup-manager s3 check with the endpoint and bucket ID doesn't report any issues.
Please let me know if I can add any additional information.

Thanks!
 
Hi, thanks for the report! Seems to be an incompatibility with that provider. I will see if we can introduce an exception for this.
 
I'm testing the S3 Endpoints functionality with MEGA and I'm encountering the following issue. If I try to delete a backup, I get an "unexpected status code 501 Not Implemented (400)." If I try to prune it, I get a message that says "A header you provided implies functionality that is not implemented."
 
Hi.
With MEGA as an S3 Endpoint, PBS has a strange behaviour.
This is the content of my cache HD:

img1.jpg
This is the content saved in MEGA:

img2.jpg

For one single backup, there is more than one folder on MEGA, but just 1 on cache HD. If i try to prune or delete backups it give me errors or if i try to refresh content from bucket.
 
Last edited: