https://api.www.ads-software.com/core/stable-check/1.7/

  • Response from version-check 1.6 and 1.7 endpoints is too slow and causes curl timeout.

    $ curl https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US

curl: (52) Empty reply from server

    and for wpcli:

    Error: RuntimeException: Failed to get url 'https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US': cURL error 28: Connection timed out after 10001 milliseconds. [error]FailedToExecuteWpCliCommand: exit status 1[/error]

    However from the same IP to same api subdomain, stable-check enpoint works as ususal:

    $ curl https://api.www.ads-software.com/core/stable-check/1.0/
{
"1.0.2" : "insecure",
"1.2.1" : "insecure",
"1.2.2" : "insecure",
"1.5.1" : "insecure",

    Are there any reported problems with the version-check at the moment? Can anybody with access to them please check, as I have currently the same problem on 9/10 servers..

    DNS works fine on all of them and another wp.org endpoint on sam api.www.ads-software.com domain works without a problem.

    $ nslookup api.www.ads-software.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: api.www.ads-software.com
Address: 198.143.164.251

    Thank you in advance.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Stefan Pejcic

    (@stefanpejcic)

    Hello,

    It looks like there might be a firewall or rate-limiting by nginx on those api endpoints, as curl from the same server but using another IP works as expected.

    • from the main server IP that is shared for majority of cpanel accounts *(shared ip):
    [xxxxxx@s30 ~]$ curl --interface 185.119.XX.X0 https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US

^C
    • from the same server with another IP dedicated to a single cpanel account:
    [xxxxxx@s30 ~]$ curl --interface 185.119.XX.X5 https://api.www.ads-software.com/core/version-check/1.7/?locale=en_US

{"offers":[{"response":"upgrade","download":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2.zip","locale":"en_US","packages":{"full":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2.zip","no_content":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2-no-content.zip","new_bundled":"https:\/\/downloads.www.ads-software.com\/release\/wordpress-6.3.2-new-bundled.zip","partial":false,"rollback":false},"current":"6.3.2","version":"6.3.2","php_version":"7.0.0","mysql_version":"5.0","new_bundled":"6.1","partial_version":false},{"response":"autoupdate","download":"https:\/\/downloads.www.ads-software.com

    It looks like there might be a firewall or rate-limiting by nginx on those api endpoints, as curl from the same server but using another IP works as expected.

    Works for me as well, and it’s totally reasonable to have such protection on any public-facing API endpoint.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘https://api.www.ads-software.com/core/stable-check/1.7/’ is closed to new replies.