One of my clients’ IP’s has a site-wide block on WordPress
-
I provide systems support for a variety of companies, some of them have fixed IP’s. One company in particular just discovered their fixed IP has a site-wide block to WordPress.
This is unusual since the company provides healthcare consultations and typically has nothing to do with WordPress at all.
We’re at a loss to explain how this happened, the ISP can’t determine a cause either.I’ve fed the IP to mxtoolbox to no avail, it says we’re clean.
-
Hi there,
I have no idea what you’re speaking of :)
You are posting in the support forums for the hosting provider, WordPress.com. I’m not sure how either WordPress.com or the WordPress software could be blocked on a site. WordPress.com could be blocked on a particular network, but not WordPress itself, as WordPress is just a piece of software – only the IP of the server on which that software is installed could be blocked on a network.
Can you please provide more detail on what exactly is wrong, and what are the sites involved? Then we might be able to point you in the right direction to get help.
-
the static IP 184.70.167.222 is blocked by WordPress.com
when we switch the forward router to use any of our other ip’s, we’re not blocked
-
Would you please reply with your
traceroute -Iandcurl -svvoutputs from that IP to WordPress.com? -
184:~ root# curl -svv wordpress.com
* Rebuilt URL to: wordpress.com/
* Trying 192.0.78.17…
* TCP_NODELAY set
* Immediate connect fail for 192.0.78.17: Host is down
* Trying 192.0.78.9…
* TCP_NODELAY set
* Connection failed
* connect to 192.0.78.9 port 80 failed: Operation timed out
* Failed to connect to wordpress.com port 80: Operation timed out
* Closing connection 0
184:~ root# -
184:~ root# traceroute -I wordpress.com
traceroute: Warning: wordpress.com has multiple addresses; using 192.0.78.17
traceroute to wordpress.com (192.0.78.17), 64 hops max, 72 byte packets
1 * * *
2 * *traceroute: sendto: No route to host
traceroute: wrote wordpress.com 72 chars, ret=-1
*
traceroute: sendto: Host is down
3 traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*
traceroute: sendto: Host is down
4 traceroute: wrote wordpress.com 72 chars, ret=-1
* * *
5 * * *
traceroute: sendto: No route to host
6 traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*
traceroute: sendto: Host is down
7 traceroute: wrote wordpress.com 72 chars, ret=-1
* * *
8 * * *
traceroute: sendto: No route to host
9 traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote wordpress.com 72 chars, ret=-1
*
traceroute: sendto: Host is down
10 traceroute: wrote wordpress.com 72 chars, ret=-1
* * * -
Thanks! I have forwarded this to our Systems Team.
We’ll let you know as soon as we know more.
-
-
The traceroute does not appear to be leaving your network. A common issue is users/providers want to block RFC1918 IPs and end up mistakenly blocking 192.0.0.0/8 instead of 192.0.0.0/16. I would suggest you double check your filtering rules.
Or if not blocking, maybe you’re trying to route the 192.0.0.0/8 netblock internally on your network.
-
it is leaving the network. That’s just one of the ISP’s gateways. Don’t be fooled by local-looking ip.
I’m on the same ISP here and I get the exact same first result on a trace96:~ devildevil$ traceroute -I wordpress.com
traceroute: Warning: wordpress.com has multiple addresses; using 192.0.78.9
traceroute to wordpress.com (192.0.78.9), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 0.757 ms 1.025 ms 0.915 ms
2 174.3.192.1 (174.3.192.1) 20.418 ms 19.382 ms 15.498 ms
3 rc1we-tge0-14-0-14-1.ed.shawcable.net (64.59.184.173) 20.728 ms 20.300 ms 17.589 ms
4 rc3no-be6.cg.shawcable.net (66.163.64.69) 25.113 ms 26.192 ms 26.579 ms
5 rc2wt-be100.wa.shawcable.net (66.163.75.233) 43.577 ms 41.247 ms 42.750 ms
6 rc1wt-be18-1.wa.shawcable.net (66.163.64.81) 42.845 ms 43.573 ms 40.386 ms
7 six.automattic.net (206.81.81.70) 41.266 ms 36.186 ms 43.189 ms
8 192.0.78.9 (192.0.78.9) 42.602 ms 44.506 ms 44.229 ms
96:~ devildevil$ -
Here’s one from earlier today, it picks the gateway via load:
96:~ devildevil$ traceroute -I wordpress.com
traceroute: Warning: wordpress.com has multiple addresses; using 192.0.78.17
traceroute to wordpress.com (192.0.78.17), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 0.768 ms 1.251 ms 2.149 ms
2 174.3.192.1 (174.3.192.1) 9.819 ms 8.448 ms 9.099 ms
3 rc1we-tge0-14-0-14-1.ed.shawcable.net (64.59.184.173) 12.235 ms 10.313 ms 9.992 ms
4 rc3no-be6.cg.shawcable.net (66.163.64.69) 16.439 ms 16.912 ms 13.919 ms
5 rc2wt-be100.wa.shawcable.net (66.163.75.233) 30.725 ms 26.535 ms 30.020 ms
6 rc1wt-be18-1.wa.shawcable.net (66.163.64.81) 29.014 ms 31.020 ms 32.202 ms
7 six.automattic.net (206.81.81.70) 31.043 ms 29.705 ms 31.142 ms
8 192.0.78.17 (192.0.78.17) 30.419 ms 31.475 ms 32.622 ms
96:~ devildevil$ -
-
-
-
It’s not clear to our team what the last two traceroutes you sent are for, and they’re significantly different from the one you sent originally. Were they done from one of the working IP addresses?
Can you please again provide the
traceroute -Iandcurl -svvoutputs to the endpoint you think is blocking you, from both IP addresses (the working one, and the not working one). Can you also in each case specify the IP you’re running the check from?We’re unable to complete a traceroute to your IP address 184.70.167.222, and our systems team can see the traffic drops at the hop just before reaching your IP address, which still indicates to them that the traffic is being incorrectly routed or filtered by your router. The information you’ve provided and what we see on our end does not indicate that this is a block on our side.
do a whois of 192.0.78.17
What exactly do you want us to see if we do that? All a Whois search indicates is where that IP is hosted. It in no way indicates whether you’re being blocked from accessing it.
-
the last 2 traces are from a separate machine in a different part of the city, on a cablemodem under the same ISP
the *ONLY* server group on the planet that 184.70.167.222 cannot connect to is the wordpress datacenter
our suite’s router is sitting behind the cablemodem assigned that ip.
184.70.167.222 is literally a cablemodem in bridge mode.
The router is completely exposed right now, firewall is turned off and there’s no rules outside of some devices with local dhcp reservations.
There’s a small switch behind that router set to be completely transparent.
Honestly, the office itself isn’t a wordpress customer, the issue has more to do with a sudden influx of contractors sending us wordpress-hosted sites. -
ugh your dumb exposed 192.0.x.x addresses are fucking with the local subnets
this is the problem. how could you guys not know this would be a problem
-
Please note we do not tolerate abusive language or profanity in this forum.
If you provide more detail on what you believe the problem is, I can relay that to our systems team to look into, but if you leave further comments like the last one I’m closing this thread to further replies.
https://en.forums.wordpress.com/topic/best-practices-community-standards/
-
-
I fixed the problem. you guys can jam your heads back up your asses with your goofy 192 ip’s
- The topic ‘One of my clients’ IP’s has a site-wide block on WordPress’ is closed to new replies.
WordPress.com Forums 