Can't connect to api.aspose.cloud

I’m using the PHP API.
I’m getting this error running the code on my development server:
cURL error 28: Failed to connect to api.aspose.cloud port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

If I probe the port in the terminal I get:

$ nmap -p 443 api.aspose.cloud
Starting Nmap 7.80 ( https://nmap.org ) at 2025-02-13 09:40 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.04 seconds

I can probe google so outbound connections are working:

$ nmap -p 443 google.com
Starting Nmap 7.80 ( https://nmap.org ) at 2025-02-13 09:39 UTC
Nmap scan report for google.com (142.250.75.238)
Host is up (0.00090s latency).
Other addresses for google.com (not scanned): 2404:6800:4017:804::200e
rDNS record for 142.250.75.238: par10s41-in-f14.1e100.net

PORT    STATE SERVICE
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds

I have the same code running on a Heroku (https://www.heroku.com/) server and it is working okay.
I use the cloud IDE gitpod (https://www.gitpod.io/) so I’m wondering of you are blocking these IP addresses?

@FFSPUD

It seems you are experiencing a connection issue with the Aspose Cloud API from your development server, as indicated by the cURL error you received. The error message cURL error 28: Failed to connect to api.aspose.cloud port 443: Connection timed out suggests that your server is unable to establish a connection to the Aspose API.

Here are a few steps you can take to troubleshoot this issue:

  1. Check Network Configuration: Ensure that your server’s firewall or network settings are not blocking outbound connections to api.aspose.cloud on port 443. Since you mentioned that you can connect to other services like Google, it may be specific to the Aspose API.

  2. Test Connectivity: You can use tools like ping or curl from your terminal to check if you can reach api.aspose.cloud. For example:

    curl -I https://api.aspose.cloud
    
  3. Temporary Network Issues: Sometimes, connection issues can be due to temporary network problems. It might be worth trying again after some time.

  4. IP Blocking: If you are using a specific cloud IDE or hosting service, it’s possible that the IP addresses from which you are trying to connect are being blocked. You may want to reach out to Aspose support to confirm if there are any restrictions on IP addresses from your hosting provider.

  5. Check Service Status: Occasionally, the Aspose API service may experience downtime or maintenance. You can check the status of the service or any announcements regarding outages.

If the problem persists after these checks, consider reaching out to Aspose support for further assistance, as they may have more insights into any ongoing issues with their API.

Sources:
No specific sources were referenced in this response.

Testing the connectivity on my Heroku server:

curl -I https://api.aspose.cloud
HTTP/1.1 200 OK
content-length: 1
content-type: text/plain

The same command timeouts out on my gitpod cloud IDE - so does this mean that Aspose is blocking gitpod?

I will ask the admin team.