"500 Internal Server Error" on PDF file upload

When trying to upload a file, we get the following response:

<head><title>500 Internal Server Error</title></head>
<center><h1>500 Internal Server Error</h1></center>

Performing a PUT request to https://api.aspose.cloud/v3.0/pdf/storage/file/test.pdf results in the above error.

Reproduce with the following Python script, setting appropriate values for client_id, client_secret, and filename.

import requests
import json
import urllib 
import datetime
import time

# fill in with your credentials
client_id = ""
client_secret = ""

# the filename to upload
filename = "test.pdf"

# get bearer token
start = time.perf_counter()
bearer_url = "https://api.aspose.cloud/connect/token"
bearer_headers = {"Content-Type": "application/x-www-form-urlencoded", "Accept": "application/json"}
bearer_data = {"grant_type": "client_credentials", "client_id": client_id, "client_secret": client_secret}
response = requests.post(bearer_url, headers=bearer_headers, data=bearer_data)
data = json.loads(response.content)
bearer_token = data["access_token"]
end = time.perf_counter()
print(f"Got bearer token: {end-start}s")

# uploading a file
start = time.perf_counter()
upload_url = "https://api.aspose.cloud/v3.0/pdf/storage/file/"
upload_header = {"Authorization": "Bearer " + bearer_token, "Content-Type" : "application/octet-stream"}
response = requests.put(upload_url + filename , data=open(filename, 'rb'), headers=upload_header)

Interestingly, the upload through the “slides” API works just fine (but has a different response than the “pdf” API):
PUT request to https://api.aspose.cloud/v3.0/slides/storage/file/test.pdf returns a JSON with the filename in uploaded compared to Uploaded in the https://api.aspose.cloud/v3.0/pdf/storage/file/ request…

1 Like


We apologize for the error. Our team is actively investigating the issue and working to resolve it promptly.

We are impacted by this error badly. Please fix it asap.

We are impacted as well. Why is your status page indicating all systems operational if you are aware of the issue???

This incidence occured since 8:20 am EST, which is 5 hrs from now. But we could not find a way to report it. I hope there is a way to report incidence. Otherwise, we would have to move away due to reliability.

1 Like

Is there anyone actually working on this product? We’re paying $ 800 / mo for no live support, no successful API call for the past 13 hours, no indication of an outage on your status page, and no update on your support forum?

What is this?

We are experiencing same issue, is there any update @tilal.ahmad

@acmernlit @slegay.oceg.org @anteklogistics @nimagnaag

We truly apologize for the inconvenience you are facing in uploading the files to storage. The issue is still not fixed, however, our product team is working hard to fix the issue as soon as possible.

@nimagnaag @anteklogistics @acmernlit @slegay.oceg.org

Thank you for your patience. The issue has been resolved. We identified and fixed some network problems in the cluster.

@tilal.ahmad this issue is still happening today


I am afraid we are unable to notice any issues. Please create a separate post and provide more details of the issue along with your sample code and input document. We will investigate the issue and guide you accordingly.