Error 403 accessing https://api.envato.com

Application Performance
1

Hi there,

We are using Wordpress hosted on a mutualized server at OVH (host: cluster028.hosting.ovh.net IPv4: 51.91.236.193 IPv6: 2001:41d0:301::28). When trying to update some Wordpress plugins, we get the error :

cURL error 7: Failed to connect to `api.envato.com` port 443: Connection refused
{"request_url":"https:\/\/api.envato.com\/whoami","response_code":"","response_cf_ray":"","response_server":""}

I wanted to check if the error was returned by Cloudflare or api.envato.com, so I launched cURL from command line with verbose output and I got:

curl -verbose `https://api.envato.com`
*   Trying 172.64.148.162...
* TCP_NODELAY set
* Expire in 149998 ms for 3 (transfer 0x562790e74220)
* Expire in 200 ms for 4 (transfer 0x562790e74220)
* connect to 172.64.148.162 port 443 failed: Connexion refusée
*   Trying 104.18.39.94...
* TCP_NODELAY set
* Expire in 149998 ms for 3 (transfer 0x562790e74220)
* connect to 104.18.39.94 port 443 failed: Connexion refusée
* Failed to connect to api.envato.com port 443: Connexion refusée
* Closing connection 0
curl: (7) Failed to connect to api.envato.com port 443: Connexion refusée

104.18.39.94 and 172.64.148.162 seems to be Cloudflare IPs.

I tried the same command on other servers (with different IP addresses) and I don’t have this issue, but only with this server.

Please what could I do to bypass this error and be able to update my Wordpress plugins ?

Thank you so much,

CĂ©dric

4

Sorry, the title is wrong, it’s not a HTTP 403 error, but a connection error :slight_smile:

5

There may be a network issue between your server and Cloudflare.

Try: mtr -P 443 -T 172.64.148.162

6

Thanks a lot for your reply :slight_smile: mtr is not installed and I can’t install it, because our SSH access is really restricted (it’s a mutualized server). I tried to use traceroute instead but it looks like I should run it as root. I’ll try other similar commands. wget and curl are installed though.

7

Traceroute doesn’t go over Port 443. You’ll have to find some way to trace the TCP/IP Port 443 connection.

Cloudflare won’t refuse a Port 443 connection like that. Your request hasn’t even gotten to the hostname part yet.

8

Yes, the DNS resolution just succeeded, but it couldn’t connect to any Cloudflare IP :frowning:

Is Cloudflare using public blacklists ? I noticed our server is blocklisted on dnsbl.spfbl.net.

9

I contacter OVH (the hosting company) and they succeeded to reproduce the issue, they are investigating :slight_smile: I hope they’ll be able to fix it.

10

Our hosting company was blocking these queries because another old user was spamming :frowning: They fixed the issue, so it wasn’t related to Cloiudflare :slight_smile: