Please double check the file path/availability; It seems that the specified file is missing in the cloud storage.
@tilal.ahmad, the file is missing due to another Aspose process not creating it as expected. Again, nothing at all has changed in our code in 3+ years. These intermittent issue are all on the Aspose side. Was the API updated today? We are seeing more errors today than any other day.
@tilal.ahmad, we consistently see this pattern of errors:
GET:502:https://api.aspose.cloud/v3.0/pdf/storage/exist/xxxxxxxxxxx.pdf | Bad Gateway Occurred: 3
System.CalloutException | Read timed out Occurred: 1
GET:404:https://api.aspose.cloud/v3.0/pdf/storage/file/xxxxxxxxxxx.pdf | Not Found Occurred: 10
GET:502:https://api.aspose.cloud/v3.0/pdf/storage/file/xxxxxxxxxxx.pdf | Bad Gateway Occurred: 1
We apologize for any inconvenience. The issue has been acknowledged, and our team is diligently working to address it.
@tilal.ahmad, we are seeing the errors again this morning. Are there any updates on the existing case?
We have released a new version of the API, along with additional VMs, and are monitoring the issue. Please share the error details(logs/screenshots) from today morning. It will help to further investigate it.
@tilal.ahmad, the errors we are seeing this morning match the same pattern:
GET:502:https://api.aspose.cloud/v3.0/pdf/storage/exist/xxxxxxxxxxx.pdf | Bad Gateway Occurred: 3
System.CalloutException | Read timed out Occurred: 1
GET:404:https://api.aspose.cloud/v3.0/pdf/storage/file/xxxxxxxxxxx.pdf | Not Found Occurred: 10
GET:502:https://api.aspose.cloud/v3.0/pdf/storage/file/xxxxxxxxxxx.pdf | Bad Gateway Occurred: 1
1 Like
I am getting the same errors, and posted in a different thread before I saw this one. I’m a week away from production launch and this is feeling very unstable as a paid service. There has to be an ETA a root cause analysis provided. I really don’t want to have to switch PDF providers a week before launch but this seems to be an ongoing problem.
@rucksack , this service is extremely unstable as of late. I would strongly recommend evaluating alternatives. It has generally been stable up until these past two weeks have been a nightmare. Our code has not changed at all in three years. We occasionally see intermittent errors, but they are usually limited to a few hours or a day. This have been over two weeks. @tilal.ahmad replies to this thread that Aspose is attempting to fix, but we haven’t seen any difference since we started reporting the error. Clearly something changed on the Aspose side or they are not properly managing capacity with AWS. We are actively evaluating options to replace Aspose.
@tilal.ahmad, the same errors are occurring again today. As I mentioned to @rucksack above, we are exploring options to replace Aspose this week. This was not planned development, so is extremely inconvenient on our end. It is disappointing that Aspose can not resolve this issue.
We sincerely apologize for this inconvenience. Your concern has been elevated to the next level for immediate attention. We are actively deploying all our resources to investigate and promptly resolve this performance issue.
Kindly test it today and provide your feedback. We have implemented some changes, and our test results came back without any issues.
@tilal.ahmad, the errors started again today. Same exact thing as I reported numerous times before. Again, nothing has changed on our side. Whatever you did 13 days ago worked. This needs to be fixed ASAP!
1 Like
@tilal.ahmad, the errors are back again today. Same thing as all the other times I reported it previously. Please add resources or whatever you do to address this. Again, just like before this is a major production issue for us and nothing has changed on our end. This again, illustrates how unreliable this Aspose service is.
1 Like
We are truly sorry for this recurring error. We are investigating it and will fix it as soon as possible.
Is there any update to this issue? We are also having gateway errors.
Thanks for your patience, the issue is resolved. We found some network problems in the cluster, which are fixed.