[SOLVED] PBS 4.x S3 Datastore Initialization Failure: 'unexpected non-empty response body' with FileLu S5

[torroe]

Hi everyone,

I am trying to configure an S3-compatible datastore on my Proxmox Backup Server (PBS) 4.1 using FileLu S5.

I have verified all local steps (correct local cache permissions, network connectivity, and S3 naming conventions), but the initialization fails immediately when PBS attempts to upload the necessary 'in-use marker'.

The exact error message is:

Task failed: failed to upload in-use marker for datastore: got unexpected non-empty response body

This typically indicates that the S5 endpoint is sending a non-empty HTTP response body (e.g., HTML/text) on a successful PUT request, which violates the strict S3 protocol rules PBS enforces.

What I have already tried:​

1. Verified and corrected local cache permissions (chown backup:backup).
2. Ensured the S3 bucket is empty (newly created).
3. Checked the S3 endpoint URL and credentials.
4. Tried the available Skip If-None-Match header Provider Quirk (did not solve the issue).

Has anyone else successfully integrated FileLu S5 with PBS or is it possible in PBS to tolerate the non-empty response body?

Any insight would be greatly appreciated!

Thanks
Torsten

 

[torroe]

Hi everyone,

I am trying to configure an S3-compatible datastore on my Proxmox Backup Server (PBS) 4.1 using FileLu S5.

I have verified all local steps (correct local cache permissions, network connectivity, and S3 naming conventions), but the initialization fails immediately when PBS attempts to upload the necessary 'in-use marker'.

The exact error message is:


This typically indicates that the S5 endpoint is sending a non-empty HTTP response body (e.g., HTML/text) on a successful PUT request, which violates the strict S3 protocol rules PBS enforces.

What I have already tried:​

1. Verified and corrected local cache permissions (chown backup:backup).
2. Ensured the S3 bucket is empty (newly created).
3. Checked the S3 endpoint URL and credentials.
4. Tried the available Skip If-None-Match header Provider Quirk (did not solve the issue).

Has anyone else successfully integrated FileLu S5 with PBS or is it possible in PBS to tolerate the non-empty response body?

Any insight would be greatly appreciated!

Thanks
Torsten

Filelu fixed this problem very fast. I can confirm that this problem is now resolved, and I was successfully able to initialize and add the S5 datastore to my Proxmox Backup Server.
But i run now in a other problem - It appears that in certain requests or responses the Content-Length header is missing, or it does not conform to the AWS S3 reference specification. I hope filelu can this fix also.

best regards
Torsten

 

[torroe]

[SOLVED] Confirmation: FileLu S5 is now working for me Natively with PBS 4.1​

Hi ,

I wanted to provide a quick final update on this issue for anyone trying to integrate FileLu S5 with Proxmox Backup Server (PBS).

FileLu support was extremely fast and helpful: They have resolved both the initial unexpected non-empty response body error and the subsequent missing header 'content-length' error on their S5 endpoint.

I can now confirm that a full backup job from PBS 4.1 to the FileLu S5 Datastore is running perfectly without any errors.

This confirms native S3 integration between PBS and FileLu is functional.

best regards
Torsten