Error while using API

Aspose.PDF Cloud Product Family
1

Hello!

We have faced error
Aspose.Words.Cloud.Sdk.ApiException: Error while get files in folder ‘Font’ from storage: Error while get file list in folder ‘Font’ from storage: AmazonS3 Storage exception: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
at Aspose.Words.Cloud.Sdk.RequestHandlers.ApiExceptionRequestHandler.ThrowApiException(HttpWebResponse webResponse, Stream resultStream)
at Aspose.Words.Cloud.Sdk.RequestHandlers.ApiExceptionRequestHandler.ProcessResponse(HttpWebResponse response, Stream resultStream)
at System.Collections.Generic.List1.ForEach(Action1 action)
at Aspose.Words.Cloud.Sdk.ApiInvoker.ReadResponse(WebRequest client, Boolean binaryResponse)
at Aspose.Words.Cloud.Sdk.ApiInvoker.InvokeInternal(String path, String method, Boolean binaryResponse, String body, Dictionary2 headerParams, Dictionary2 formParams, String contentType)
at Aspose.Words.Cloud.Sdk.WordsApi.ConvertDocument(ConvertDocumentRequest request)

Could you please help us with this error?
We want to notice, that we use an internal storage to save fonts.

Thank you!

2

@AsposeCreatio

I have tested the ConvertDocument API using the fontsLocation parameter and have been unable to notice any issues. Please share your sample code and credentials via a private message. We will investigate the issue and guide you.

3

@AsposeCreatio

We have made some changes and it should be working now. Please try now and share the results.

4

It works. Thank you

1 Like
5

@tilal.ahmad We seem to be getting the same error when using the WordsApi().uploadFile() function

Sort of came out of nowhere

Any help would be appreciated

6

@jessewilliams

We sincerely apologize for any inconvenience this may have caused. We are actively investigating the matter of Aspose storage failures experienced by certain users.

7

We continue to receive errors from the service. We expect a prompt solution to the problem.

8

@AsposeCreatio, @jessewilliams

We have fixed the issue; please try now.