Thanks for sharing additional information
Hi,
Any update on this?
The admin team is working on it. Once they share any update, I will contact you here.
@centris.aspose
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSCLOUD-3039
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
we are still seeing error , can you let us know if there is a solution being worked? we are using aspose 4.0 and client is reporting lot of issues
“common.apex.runtime.impl.ExecutionException: ASPOSE File Upload Service Exception : DataSourceException:[]: ASPOSE Service Exception : System.CalloutException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 503 Service Unavailable"”|0x259190f1
I’m afraid that for now, I don’t have any new information about that issue, and the admin team hasn’t shared any new information
Could you please share the IP address of your service that sends requests to our service? The admin team is working on analyzing logs to find all the requests your service makes.
Also, do you use the same code for all of your clients?
This is another user IP 148.168.96.5 who is getting same error intermittently, we are not having reason why only specific client is always is having issue when trying to use aspose. can you check and let us know.
The users IPs won’t help as it’s your service that sends requests to aspose, so share your service IP which sends requests we trying to find some reasons why. For now we don’t have any restriction for IPs
Salesforce as a Service has IP Ranges for outbound call might originate from any below IP within those ranges. can you check if we need to whitelist ALL relevant IP ranges for Salesforce to avoid issues?
[
“141.163.208.0/23”,
“141.163.200.0/23”,
“141.163.214.0/24”,
“141.163.204.0/23”,
“141.163.216.0/24”,
“141.163.196.0/23”,
“141.163.192.0/23”,
“141.163.212.0/24”,
“155.226.152.0/23”,
“145.224.208.0/23”,
“145.224.198.0/24”,
“145.224.204.0/23”,
“145.224.196.0/24”,
“145.224.200.0/23”,
“145.224.212.0/24”,
“145.224.192.0/24”,
“145.224.194.0/24”,
“155.226.188.0/23”,
“155.226.144.0/22”,
“155.226.156.0/23”,
“155.226.128.0/21”
]
Thanks for sharing. Admins are looking for the solution.
They didn’t find any blocked requests from that range of IPs. Let’s check the code. Do you use the same code for clients who can connect to our service and those who can’t? Could it be that some settings differ?
we use same code for all clients who connect to Aspose, which settings are you referring to? on aspose storage cloud?
Yes, all of them use default aspose storage? or their own buckets?
most of them are using default storage, some use dedicated storage
the clients who are facing issue 1 using default and 1 using own bucket. both have issue
the one who has own issue what is the region of the bucket? I mean, us-east1, us-west2 and etc.
for own storage issue, we are not sure where to check the region on Aspose site but the outbound call might originate from the this region on us-west-2
155.226.128.0/21 - IP ranges
We have created Internal Storage dedicated to a Client for separation only but not using any external storage for any of our CLients.
image.png (65.3 KB)