Blocked from ww.wp.xz.cn

  • Resolved CaliZ

    (@caliz)


    8 years, 10 months ago

    Self-Hosted WordPress website running on Interworx based hosting platform with CentOS 6.

    Problem: All websites hosted are accessible, wp-admin accessible, but when navigating to “add new” in plugins area, receiving “An unexpected error occurred. Something may be wrong with ww.wp.xz.cn or this server’s configuration. If you continue to have problems, please try the support forums.” error.

    Diagnosis:
    -Checked and switched DNS/nameservers for hosting server. (Not nameservers for the websites, just for the hosting server)
    -Able to resolve ww.wp.xz.cn (66.155.40.250) but ping test times out.
    -When connecting via telnet to ww.wp.xz.cn from another IP, connected fine, when telnet from specified questionable IP to ww.wp.xz.cn, connection times out.
    -IP address is not blacklisted using MXToolbox search.
    -Restarted services, tested with firewall disabled, no change.
    -Add a few of ww.wp.xz.cn’s IP’s to whitelist on firewall.

    I have a hard time believing that my one IP address used for hosting websites is blocked by ww.wp.xz.cn, but I’m running out of ideas as to what else it could be. Any thoughts?

    • This topic was modified 8 years, 10 months ago by CaliZ.
Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Bob Cristello

    (@gntmidnight)

    8 years, 10 months ago

    Is your WordPress installation asking you to provide FTP credentials prior to installing any plugin?

    There are many reasons why this connection fails and it is a fairly common problem. Are you on a hosting company setup or is this a configuration you have set up on a local box acting as a server? If this is a hosting company, have you tried contacting your hosting company for support?

    As a plan B alternative, you can always install plugins manually.

    https://codex.ww.wp.xz.cn/Managing_Plugins#Manual_Plugin_Installation

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    Hi Bob,

    Thanks for the reply. No, all sites are already installed, and prior to this all plugins to be updated or installed did not require FTP credentials.

    I’m not concerned about “installing” plugins at this time as they can still be completed manually using a FTP client. But this is not ideal. The only change was replacing the namesever/DNS listed (/etc/resolv.conf and ifcfg-eth) as our ISP replaced their servers.

    This is a server with a dedicated connection and static IP’s. (Not home brew) Listed in the original post, the server will ping to all websites and IP’s fine with exception to downloads.wp.xz.cn, ww.wp.xz.cn. With the firewall temporarily disabled (Wide open), there is no change so I can’t believe it to be any sort of configuration error with the server.

    The IP in question is not blacklisted anywhere, and cannot be changed. However, without it being able to cURL or wget from ww.wp.xz.cn, leaves it pretty useless.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    8 years, 10 months ago

    Check your version of openSSL — if you’re using an old one, you may not be able to connect to the WP download servers. My CentOS 6 machine us using openssl-1.0.1e-57.el6.x86_64.

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    Hi Steve,

    openssl-devel-1.0.1e-57.el6.x86_64 is installed. That would make sense, getting a little closer but still no change.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    8 years, 10 months ago

    Try “sudo yum install openssl”

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    Done, latest version already installed.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    8 years, 10 months ago

    Fudge. OK, that’s not it, I guess.

    What do you see with

    wget -dv https://ww.wp.xz.cn/latest.tar.gz

    I see this

    URI encoding = ‘UTF-8’
Converted file name 'latest.tar.gz' (UTF-8) -> 'latest.tar.gz' (UTF-8)
Converted file name 'latest.tar.gz' (UTF-8) -> 'latest.tar.gz' (UTF-8)
--2017-07-24 17:56:32--  https://ww.wp.xz.cn/latest.tar.gz
Resolving ww.wp.xz.cn (ww.wp.xz.cn)... 66.155.40.249, 66.155.40.250
Caching ww.wp.xz.cn => 66.155.40.249 66.155.40.250
Connecting to ww.wp.xz.cn (ww.wp.xz.cn)|66.155.40.249|:443... connected.
Created socket 3.
Releasing 0x00000000017edfa0 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 3 to SSL handle 0x0000000001832e70
certificate:
  subject: /OU=Domain Control Validated/CN=*.ww.wp.xz.cn
  issuer:  /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
X509 certificate successfully verified and matches host ww.wp.xz.cn

---request begin---
GET /latest.tar.gz HTTP/1.1
User-Agent: Wget/1.14 (linux-gnu)
Accept: */*
Host: ww.wp.xz.cn
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response... 
---response begin---
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 24 Jul 2017 22:56:32 GMT
Content-Type: application/octet-stream
Content-Length: 8169865
Connection: keep-alive
Cache-control: private
Content-Disposition: attachment; filename=wordpress-4.8.tar.gz
Last-Modified: Thu, 08 Jun 2017 14:30:14 GMT
X-Frame-Options: SAMEORIGIN
Content-MD5: b91248a7220a7fb1ca293c3a0ec8db6c
X-nc: HIT lax 249
Accept-Ranges: bytes

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 8169865 (7.8M) [application/octet-stream]
Saving to: ‘latest.tar.gz.1’

100%[======================================>] 8,169,865   7.33MB/s   in 1.1s   

2017-07-24 17:56:34 (7.33 MB/s) - ‘latest.tar.gz.1’ saved [8169865/8169865]
    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    wget -dv https://ww.wp.xz.cn/latest.tar.gz produces the following:

    Setting --verbose (verbose) to 1
DEBUG output created by Wget 1.12 on linux-gnu.

--2017-07-24 17:02:59--  https://ww.wp.xz.cn/latest.tar.gz
Resolving ww.wp.xz.cn... 66.155.40.250, 66.155.40.249
Caching ww.wp.xz.cn => 66.155.40.250 66.155.40.249
Connecting to ww.wp.xz.cn|66.155.40.250|:443... Closed fd 3
failed: Connection timed out.
Connecting to ww.wp.xz.cn|66.155.40.249|:443... Closed fd 3
failed: Connection timed out.
Releasing 0x0000000001b4c6e0 (new refcount 1).
Retrying.

--2017-07-24 17:03:30--  (try: 2)  https://ww.wp.xz.cn/latest.tar.gz
Found ww.wp.xz.cn in host_name_addresses_map (0x1b4c6e0)
Connecting to ww.wp.xz.cn|66.155.40.250|:443... Closed fd 3
failed: Connection timed out.
Connecting to ww.wp.xz.cn|66.155.40.249|:443... Closed fd 3
failed: Connection timed out.
Releasing 0x0000000001b4c6e0 (new refcount 1).
Retrying.

    Doing this with any of the other servers (Same connection, different IP, set of 5 IP’s used) works fine.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    8 years, 10 months ago

    What’s the IP address for your server?

    Moderator Samuel Wood (Otto)

    (@otto42)

    ww.wp.xz.cn Admin

    8 years, 10 months ago

    > “Wget 1.12”

    That version is pretty much outdated and cannot talk to modern servers via SSL connections.

    Upgrade your wget version to something more recent. 1.19 is the latest, but anything better than 1.12 will probably work. Version 1.12 is eight years old now.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    8 years, 10 months ago

    Similarly, make sure you’re using the latest version of curl. My C6 box can successfully connect to ww.wp.xz.cn and download wordpress using curl 7.19.7

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    IP is 96.53.101.45.
    I updated wget to version 1.19 and cURL to 7.54.1 using city-fan.repo.

    Tested wget, no change still times out.
    Test cURL, same thing, connection timed out.

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    Any further progress with checking on the specified IP address? I have checked through everything I can possibly search through on the server and cannot find anything that could be blocking it.

    Thread Starter CaliZ

    (@caliz)

    8 years, 10 months ago

    With nothing changed since the above replies, the server is now able to access ww.wp.xz.cn. I believe that my original assumption that the one IP used, was blocked, and is now unblocked by ww.wp.xz.cn. It would be nice to know why it was, but regardless, I am happy that the websites are able to update and install plugins as normal.

    Thanks.

    Thread Starter CaliZ

    (@caliz)

    8 years, 7 months ago

    Hello,

    I’m back once again with the same IP having connection timed out to planet.ww.wp.xz.cn. Checked blacklist reports and do not see any issues. Any help is appreciated.
    Thanks.

Viewing 15 replies - 1 through 15 (of 16 total)
1 2

The topic ‘Blocked from ww.wp.xz.cn’ is closed to new replies.