Error Aspose Cloud API

Aspose.Total Cloud Product Family
1

From HTTP Request

Error code

ETIMEDOUT

Full message

connect ETIMEDOUT

Request

{ "headers": { "accept": "application/json,text/html,application/xhtml+xml,application/xml,text/*;q=0.9, image/*;q=0.8, */*;q=0.7", "content-type": "multipart/form-data; boundary=--------------------------a31879c22ed66140678efd2e" }, "method": "POST", "uri": "https://api.aspose.cloud/connect/token", "gzip": true, "rejectUnauthorized": true, "followRedirect": true, "resolveWithFullResponse": true, "followAllRedirects": true, "timeout": 300000, "formData": { "_overheadLength": 329, "_valueLength": 86, "_valuesToMeasure": [], "writable": false, "readable": true, "dataSize": 0, "maxDataSize": 2097152, "pauseStreams": true, "_released": true, "_streams": [], "_currentStream": null, "_insideLoop": false, "_pendingNext": false, "_boundary": "--------------------------a31879c22ed66140678efd2e", "_events": {}, "_eventsCount": 3 }, "encoding": null, "json": false, "useStream": true }

yesterday was everything ok

2

@Labor_AI

The ETIMEDOUT error when connecting to api.aspose.cloud on port 443 may indicate a temporary network or service-side issue.

Other users have previously reported connection timeouts and unresponsive behavior when accessing api.aspose.cloud:443, including cases where the server did not respond to requests . Specifically, there were incidents where POST requests to /connect/token failed to return a response, even with valid credentials, and the issue was later confirmed and resolved by the Aspose team after redeploying the credentials server . Inconsistent behavior across different environments has also been noted, with some clients failing while others succeed under the same configuration .

Since your integration was working previously and no changes were made on your end, this could be a transient service disruption.

Recommended actions:

  1. Retry the request — the issue may have already been resolved.
  2. Check the Aspose forum for any ongoing service announcements.
  3. If the problem persists, consider reaching out to Aspose support with your request timestamp and client details for further assistance.