Hi there,
We’re experiencing issues with saving to docx with the publishing failing due to
Error: SaveAs. Exception: Error while get files in folder ‘CustomFonts’ from storage: Error while get file list in folder ‘CustomFonts’ from storage: AmazonS3 Stor…
Is there any news on what’s causing this?
The error you are encountering while trying to save a document to DOCX format seems to be related to accessing custom fonts stored in your Amazon S3 bucket. The specific message indicates that the bucket must be accessed using a designated endpoint, which is a common requirement when working with Amazon S3.
To resolve this issue, please ensure that you are using the correct endpoint for your S3 bucket. Each S3 bucket is associated with a specific region, and you need to use the endpoint that corresponds to that region. For example, if your bucket is in the US East (N. Virginia) region, the endpoint would typically be s3.amazonaws.com. If it’s in another region, the endpoint will differ accordingly.
Additionally, make sure that the folder where your custom fonts are stored is correctly named and accessible. The folder should be named ‘CustomFonts’ as per your error message, and it should be located in the root of your storage.
If you continue to experience issues, consider checking the permissions for your S3 bucket to ensure that your application has the necessary access rights to read from the ‘CustomFonts’ folder.
For further assistance, you might want to refer to similar posts where users have encountered and resolved related issues. Here are a couple of relevant discussions:
If you have any additional details or specific configurations, feel free to share them for more tailored assistance.
Sorry I should have clarified, the custom fonts are saved on aspose and nothing our end has changed!
API call to https://api.aspose.cloud/v4.0/words/online/put/saveAs?fontslocation=CustomFonts
Please check that this folder exists on storage, and also check the retention policy is set for your storage. And one more thing, if you want your files not to be deleted after the time set in settings, you can specify a regex expression which will be used to remove the file from the list for deletion
Hey @yaroslaw.ekimov
The folder exists on storage and we have an exclusion rule for the folder. This hasn’t changed for months and earlier on today the requests were working ,and then stopped working so there is an issue on your side.
Please could you take a look please?
Sure, I will check it right away.
One of the errors that may cause such behavior has been fixed; now we are waiting for a fix for another error that is being deployed.
Recent testing shows that this is still not resolved.
Could you please check that it now works?
Hi @yaroslaw.ekimov no it’s still broken… trace-id of a recent saveAs attempt 9f2544f5-72fe-4c31-aeeb-a3a259483a1f if that helps. This is majorly impacting our clients now so we need a resolution to this ASAP.
And also now one of our internal storages has just been deleted…
Please share your client id I will send it to the storage team to fix this.
client_ID:
c10af0e8-e414-4f80-bb65-c846042555f0
Thanks for sharing, I sent all the information to the responsible team.
Storage team hasn’t shared any updates on that matter, I will reach out to them to check the progress.
Please do, if this cannot be resolved we will be unable to continue using the service.
They are now fixing the issue, it’s a dashboard project with regex expiration problem, hope it will be resolved soon.
The storage team hasn’t finished the task, but they shared the regex, which is working for preserving fonts. I will contact you once they complete their task and the regex begins to work as usual. Here is a regex
.*\.(ttf|TTF|otf)$