FreePBX 17 Issue - Filestore

Just completed a FreePBX upgrade from 16 to 17 and a restore of the server

One issue i have come across is with the Filestore module – previously we were backing up the server to Backblaze B2 using S3 custom settings without incident

After the switch to 17 ran into ACL errors:

InvalidArgument

Unsupporte (truncated…) InvalidArgument (client): Unsupported value for canned acl ‘public-read’ -

InvalidArgument

Unsupported value for canned acl ‘public-read’

Seems like a known S3 to Backblaze issue: https://framacolibri.org/t/backblaze-s3-storage-troubleshooting-unsupported-value-for-canned-acl/20767

At the same time also seems like some small tweaks to the ACL section of S3 should fix

Can someone assist me in fixing this or point me in the right direction for the config files

Filestore is a wrapper around Flysystem File Storage Abstraction for PHP - Flysystem

If the bug has been resolved in their s3 driver it is just a matter of updating the s3 driver

Will look into it

Another item i noticed is that many of my FPBX 16 systems which had been working fine for a long time appear to have stopped working around the beginning of July 2024 –

The backup says that is completing without errors but the files are not getting uploaded to my B2 bucket

Can someone from Sangoma tell me if something was changed to the module about a month ago?

It is all open source :slight_smile:

I decided to switch my S3 storage from Backblaze to Cloudflare R2 and seems to work fine

Will call this closed for now

thanks

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.