We also encountered this issue. This is happening far too frequently and has a significant detrimental impact on our business’ reputation. What is being done to rectify this issue permanently?
Yesterday, there was a cluster issue that we couldn’t predict. Later that night, most of the billing services were migrated to a new cluster, and for now, it seems stable. I asked the admin team about the possibility of new failures, and if migration is completed, they told me that the most challenging part is over, and they put all their efforts into making it as stable as before.
Yes it was the billing service down, they haven’t got the root cause yet, once they shared with me I will update you
I got a RCA from the billing team:
There was a connection issue with the DB, which suddenly stopped responding to requests and sent a timeout exception to the billing application. Our hosting team migrated the VM with the database closer to other applications to avoid network hops. Also, some settings have been updated to address this issue, like increasing the maximum number of connections to DB and keeping alive monitoring has been set to check if the DB is okay.
The issue is happened again.
ASPOSE licencing issue - Free Support Forum - aspose.cloud
Could you please take a look Urgently and let us know what is happening
Status page says it is working fine now, do you still have problems with billing?
it looks like the same connectivity issue.
Could you try to restart your container of aspose to check if it connects to billing to check that you should call v4.0/words/info method
The container restart solved the issu.
Could you please investigate why is this happening ? and what will be the good solution to implement in order nto prevent this happening again
We are now working on changing the request pipeline to avoid such issues.
Thx for you replay.
Please let us know once the solution is in place
Yes I answered you on other topic.
We are currently experiencing a major outage with Aspose. What is going on?? We cannot activate billing on our self-hosted instance or generate your documents on your cloud API.
We need this fixed ASAP @yaroslaw.ekimov
There was a connectivity issue with DB; the billing work has been restored, and the admin team is analyzing why this happened.
There is still no service for doc to pdf transformation. Can you please check and fix?
Thank you!
I am also not able to convert doc to html from last 1 hour, what is the issue please check on urgent basis…
The API is working fine now. Sorry for the inconvenience.
Hi. Was there another issue yesterday (24th February, around 16:00-17:00 UTC)?
I got a number of errors thrown yesterday in our “inline viewer” component. The line of code in question simply creates the API client object:
api = AsposeWordsCloud::WordsApi.new
Error:
**JSON::ParserError** in **inline_viewer#show**
unexpected character: 'Request could not be proxied.
A'
There’s no mention of any of these outages on the status page
image.png (115.8 KB)
Hi I am getting mentioned error, please resolve it ASAP as this is on production environment.