Support » Requests and Feedback » Is wordpress.org restricting visits from China region?

  • Hi there,

    When I go to upgrade to WordPress 5.2.4, and see it’s release notes, but found the website return HTTP 429 (Too Many Requests). It’s my first time to visit today. So it’s impossible to say visiting frequently, then I found all China region is restricting as HTTP 429:

    http://www.17ce.com/site/http/20191018_55ae4a50f18911e9ab8c05c7fa0e7c63:1.html

    The people in China could be hard to download new version WordPress. I sad to see WordPress.org restricting visits from China, and wonder why. I hope it will be fixed.

    Detail information:

    $ curl -v https://wordpress.org
    *   Trying 198.143.164.252...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0x55a96b399f50)
    * Connected to wordpress.org (198.143.164.252) port 443 (#0)
    * ALPN, offering h2
    * ALPN, offering http/1.1
    * successfully set certificate verify locations:
    *   CAfile: none
      CApath: /etc/ssl/certs
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    * TLSv1.3 (IN), TLS handshake, Certificate (11):
    * TLSv1.3 (IN), TLS handshake, CERT verify (15):
    * TLSv1.3 (IN), TLS handshake, Finished (20):
    * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    * TLSv1.3 (OUT), TLS handshake, Finished (20):
    * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
    * ALPN, server accepted to use h2
    * Server certificate:
    *  subject: OU=Domain Control Validated; CN=*.wordpress.org
    *  start date: Nov  6 17:42:01 2017 GMT
    *  expire date: Dec 15 20:11:21 2020 GMT
    *  subjectAltName: host "wordpress.org" matched cert's "wordpress.org"
    *  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
    *  SSL certificate verify ok.
    * Using HTTP2, server supports multi-use
    * Connection state changed (HTTP/2 confirmed)
    * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
    * Using Stream ID: 1 (easy handle 0x55a96b399f50)
    > GET / HTTP/2
    > Host: wordpress.org
    > User-Agent: curl/7.64.0
    > Accept: */*
    > 
    * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    * old SSL session ID is stale, removing
    * Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
    < HTTP/2 429 
    < server: nginx
    < date: Fri, 18 Oct 2019 11:29:11 GMT
    < content-type: text/html
    < content-length: 162
    < 
    <html>
    <head><title>429 Too Many Requests</title></head>
    <body>
    <center><h1>429 Too Many Requests</h1></center>
    <hr><center>nginx</center>
    </body>
    </html>
    * Connection #0 to host wordpress.org left intact
    • This topic was modified 3 months, 1 week ago by Jan Dembowski.
    • This topic was modified 3 months, 1 week ago by Jan Dembowski. Reason: Moved to Everything else WordPress, this is not a Requests and Feedback topic
Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.