24 Jun
2013
24 Jun
'13
4:20 p.m.
The recent WordPress update has reminded me that in the WordPress wiki
page (updated with a couple more tips, BTW) I mention the WP Remote
service which lets you do things like upgrade WordPress on many sites
with a click or two.
When it works, it's great, but I am finding it is not always able to
communicate with my sites. It wasn't working on Saturday, it was on
Sunday, it's not now.
At one point, they were using their own server and a single IP address.
Now they're using AWS and the IP address varies according to whatever
Amazon assign to them at the time.
My suspicion was that assorted nasties are also using AWS, behaving
badly, triggering a Fail2Ban jail one way or another, and this sometimes
leads to WP Remote being caught in the ban when it is assigned the same
IP address as the nasties had.
The problem with that theory is that if I look at the IP addresses that
have been successfully used over the past few months, via looking in the
webserver logfiles, there are three:
50.16.139.168
54.224.171.85
54.242.241.26
.. and none of them are currently being blocked by iptables.
This is affecting both my VPS. Surprisingly few addresses are being
currently being blocked, and none of them look to be anywhere near
those, and I can only spot one in common between the two. And that's
nothing to do with Amazon.
Is anyone else seeing anything similar?
Ian
24 Jun
24 Jun
4:29 p.m.
Hi Ian,
On Mon, Jun 24, 2013 at 05:20:52PM +0100, Ian wrote:
This is affecting both my VPS. Surprisingly few
addresses are being
currently being blocked, and none of them look to be anywhere near
those, and I can only spot one in common between the two. And that's
nothing to do with Amazon.
Is anyone else seeing anything similar?
It is not clear to me from reading your email what your actual issue
is.
If there is some IP address that you are unable to reach from your
VPS(es), can you let us know what it is?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4:57 p.m.
Andy asked:
It is not clear to me from reading your email what
your actual issue
is.
If there is some IP address that you are unable to reach from your
VPS(es), can you let us know what it is?
The other way around:- some IP addresses, ones used by AWS, aren't
always reaching my VPS.
The service that uses AWS is currently working for me, i.e. it is
reaching my VPS. It wasn't earlier this afternoon.
It's not easy to know which IP addresses aren't reaching it, but
54.224.171.85
50.16.139.168
just have. Neither are in /var/log/kern.log as being blocked earlier,
but it's not easy to know what IP address they were using then beyond
saying 'ones in the range assigned to amazonaws.com'.
Does that make sense?
Ian
5:11 p.m.
Hi Ian,
On Mon, Jun 24, 2013 at 05:57:48PM +0100, Ian wrote:
The other way around:- some IP addresses, ones used by
AWS, aren't
always reaching my VPS.
You can still test this from your VPS as neither a ping nor a
traceroute will work without bi-directional connectivity. Paths can
be asymmetric, with only a failure in A>B or B>A.
The service that uses AWS is currently working for me,
i.e. it is
reaching my VPS. It wasn't earlier this afternoon.
We are not likely to make much progress on this without knowing
which IP address(es) are unreachable.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
5:20 p.m.
Andy said:
S as neither a ping nor a
traceroute will work without bi-directional
connectivity. Paths can
be asymmetric, with only a failure in A>B or B>A.
OK, the next time it doesn't work, I will try the ones that have worked
in the past and see if they still are.
We are not likely to make much progress on this
without knowing
which IP address(es) are unreachable.
The problem with that is that Amazon AWS apparently uses about two
million IP addresses, and it could be any of them...
Ian
7 Jul
7 Jul
9:37 a.m.
I said..
OK, the next time it doesn't work, I will try the
ones that have worked
in the past and see if they still are.
The AWS-hosted service is not working for me at the moment if I do a
traceroute from the server to two addresses I know have been used, I get
this:
traceroute to 54.224.171.85 (54.224.171.85), 30 hops max, 60 byte packets
1 obstler.bitfolk.com (85.119.80.8) 0.113 ms 0.103 ms 0.089 ms
2 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.408 ms 0.511 ms 0.638 ms
3 * * *
4 xe-6-0-3.r22.londen03.uk.bb.gin.ntt.net (129.250.6.52) 0.560 ms
0.554 ms 0.536 ms
5 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 79.069 ms
70.485 ms 78.792 ms
6 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 82.304 ms
78.405 ms 78.850 ms
7 ae-5.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.183) 76.464 ms
86.242 ms 76.499 ms
8 ae-1.r04.asbnva02.us.bb.gin.ntt.net (129.250.3.17) 75.842 ms
78.450 ms 74.581 ms
9 ae-5.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.74) 123.036 ms
77.411 ms ae-4.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.50)
74.463 ms
10 72.21.220.45 (72.21.220.45) 79.393 ms 72.21.220.37 (72.21.220.37)
85.883 ms 72.21.220.61 (72.21.220.61) 86.360 ms
11 72.21.222.149 (72.21.222.149) 103.169 ms 85.841 ms 205.251.245.65
(205.251.245.65) 85.791 ms
12 * * *
13 * * *
14 * * *
15 216.182.224.81 (216.182.224.81) 79.537 ms 216.182.224.27
(216.182.224.27) 75.167 ms 216.182.224.25 (216.182.224.25) 79.071 ms
16 * * *
..
30 * * *
traceroute to 50.16.139.168 (50.16.139.168), 30 hops max, 60 byte packets
1 obstler.bitfolk.com (85.119.80.8) 0.082 ms 0.057 ms 0.043 ms
2 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.482 ms 0.470 ms 0.577 ms
3 * * *
4 xe-6-0-3.r22.londen03.uk.bb.gin.ntt.net (129.250.6.52) 0.520 ms
0.506 ms 0.495 ms
5 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 72.303 ms
69.084 ms 70.409 ms
6 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 69.746 ms
70.370 ms 75.362 ms
7 ae-5.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.183) 77.942 ms
78.535 ms 89.859 ms
8 ae-1.r04.asbnva02.us.bb.gin.ntt.net (129.250.3.17) 85.620 ms
75.852 ms 75.955 ms
9 ae-4.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.50) 78.942 ms
ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38) 76.686 ms 80.720 ms
10 72.21.220.29 (72.21.220.29) 85.432 ms 72.21.220.61 (72.21.220.61)
85.848 ms 72.21.220.69 (72.21.220.69) 86.161 ms
11 205.251.245.65 (205.251.245.65) 81.914 ms 72.21.222.149
(72.21.222.149) 84.430 ms 88.348 ms
12 * * *
13 * * *
14 * * *
15 216.182.224.77 (216.182.224.77) 85.632 ms 216.182.224.243
(216.182.224.243) 96.197 ms 216.182.224.121 (216.182.224.121) 85.606 ms
16 * * *
...
30 * * *
.. and I get much the same result from home:
ian@core2 ~ $ traceroute 54.224.171.85
traceroute to 54.224.171.85 (54.224.171.85), 30 hops max, 60 byte packets
...
6 * tele-ic-4-ae0-0.network.virginmedia.net (62.253.174.18) 76.585
ms 76.599 ms
7 equinix01-iad2.amazon.com (206.126.236.68) 110.352 ms 119.683 ms *
8 72.21.220.53 (72.21.220.53) 128.953 ms 132.245 ms 144.806 ms
9 72.21.222.149 (72.21.222.149) 144.837 ms 205.251.245.65
(205.251.245.65) 162.165 ms 162.195 ms
10 * * *
11 * * *
12 * * *
13 216.182.224.211 (216.182.224.211) 105.777 ms 216.182.224.209
(216.182.224.209) 100.980 ms 114.747 ms
14 * * *
...
30 * * *
Hmm, set up a WP site at home and see if it is seen by the service?
Ian
9:39 a.m.
I'm not really sure I understand the problem here, but amazon instances addresses do
and will change - every time you reboot the instances or every time an instance gets
replaced in an auto-scaling group. Are your instances rebooting? If so, you could just be
trace routing to an IP address that's no longer attached to anything...
Have you considered using EIPs (Elastic IPs) on your instances, which will effectively
give them a static IP address?
Paul
Sent from my iPhone. Please excuse brevity, spelling and punctuation.
On 7 Jul 2013, at 10:36, "Ian"
<ian@lovingboth.com<mailto:ian@lovingboth.com>> wrote:
I said..
OK, the next time it doesn't work, I will try the ones that have worked
in the past and see if they still are.
The AWS-hosted service is not working for me at the moment if I do a traceroute from the
server to two addresses I know have been used, I get this:
traceroute to 54.224.171.85 (54.224.171.85), 30 hops max, 60 byte packets
1 obstler.bitfolk.com<http://obstler.bitfolk.com> (85.119.80.8) 0.113 ms 0.103 ms
0.089 ms
2 jump-gw-4.lon.bitfolk.com<http://jump-gw-4.lon.bitfolk.com> (85.119.80.4) 0.408
ms 0.511 ms 0.638 ms
3 * * *
4 xe-6-0-3.r22.londen03.uk.bb.gin.ntt.net (129.250.6.52) 0.560 ms 0.554 ms 0.536 ms
5 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 79.069 ms 70.485 ms 78.792 ms
6 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 82.304 ms 78.405 ms 78.850 ms
7 ae-5.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.183) 76.464 ms 86.242 ms 76.499 ms
8 ae-1.r04.asbnva02.us.bb.gin.ntt.net (129.250.3.17) 75.842 ms 78.450 ms 74.581 ms
9 ae-5.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.74) 123.036 ms 77.411 ms
ae-4.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.50) 74.463 ms
10 72.21.220.45 (72.21.220.45) 79.393 ms 72.21.220.37 (72.21.220.37) 85.883 ms
72.21.220.61 (72.21.220.61) 86.360 ms
11 72.21.222.149 (72.21.222.149) 103.169 ms 85.841 ms 205.251.245.65 (205.251.245.65)
85.791 ms
12 * * *
13 * * *
14 * * *
15 216.182.224.81 (216.182.224.81) 79.537 ms 216.182.224.27 (216.182.224.27) 75.167 ms
216.182.224.25 (216.182.224.25) 79.071 ms
16 * * *
..
30 * * *
traceroute to 50.16.139.168 (50.16.139.168), 30 hops max, 60 byte packets
1 obstler.bitfolk.com<http://obstler.bitfolk.com> (85.119.80.8) 0.082 ms 0.057 ms
0.043 ms
2 jump-gw-4.lon.bitfolk.com<http://jump-gw-4.lon.bitfolk.com> (85.119.80.4) 0.482
ms 0.470 ms 0.577 ms
3 * * *
4 xe-6-0-3.r22.londen03.uk.bb.gin.ntt.net (129.250.6.52) 0.520 ms 0.506 ms 0.495 ms
5 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 72.303 ms 69.084 ms 70.409 ms
6 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 69.746 ms 70.370 ms 75.362 ms
7 ae-5.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.183) 77.942 ms 78.535 ms 89.859 ms
8 ae-1.r04.asbnva02.us.bb.gin.ntt.net (129.250.3.17) 85.620 ms 75.852 ms 75.955 ms
9 ae-4.amazon.asbnva02.us.bb.gin.ntt.net (168.143.232.50) 78.942 ms
ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38) 76.686 ms 80.720 ms
10 72.21.220.29 (72.21.220.29) 85.432 ms 72.21.220.61 (72.21.220.61) 85.848 ms
72.21.220.69 (72.21.220.69) 86.161 ms
11 205.251.245.65 (205.251.245.65) 81.914 ms 72.21.222.149 (72.21.222.149) 84.430 ms
88.348 ms
12 * * *
13 * * *
14 * * *
15 216.182.224.77 (216.182.224.77) 85.632 ms 216.182.224.243 (216.182.224.243) 96.197
ms 216.182.224.121 (216.182.224.121) 85.606 ms
16 * * *
...
30 * * *
.. and I get much the same result from home:
ian@core2 ~ $ traceroute 54.224.171.85
traceroute to 54.224.171.85 (54.224.171.85), 30 hops max, 60 byte packets
...
6 *
tele-ic-4-ae0-0.network.virginmedia.net<http://tele-ic-4-ae0-0.network.virginmedia.net>
(62.253.174.18) 76.585 ms 76.599 ms
7 equinix01-iad2.amazon.com<http://equinix01-iad2.amazon.com> (206.126.236.68)
110.352 ms 119.683 ms *
8 72.21.220.53 (72.21.220.53) 128.953 ms 132.245 ms 144.806 ms
9 72.21.222.149 (72.21.222.149) 144.837 ms 205.251.245.65 (205.251.245.65) 162.165 ms
162.195 ms
10 * * *
11 * * *
12 * * *
13 216.182.224.211 (216.182.224.211) 105.777 ms 216.182.224.209 (216.182.224.209)
100.980 ms 114.747 ms
14 * * *
...
30 * * *
Hmm, set up a WP site at home and see if it is seen by the service?
Ian
_______________________________________________
users mailing list
users@lists.bitfolk.com<mailto:users@lists.bitfolk.com>
https://lists.bitfolk.com/mailman/listinfo/users
11:23 a.m.
Paul Lewis said:
I'm not really sure I understand the problem here,
but amazon instances
addresses do and will change - every time you reboot the instances or every
time an instance gets replaced in an auto-scaling group.
See other post :) I am having problems with the wpremote.com site and
its (in)ability to see my VPS. At some point, it switched to using AWS
rather than their own server.
I am aware that as a result the IP address it uses may change, but
these are the ones that have been used successfully, over an extended
period.
Ian
4:18 p.m.
Hi Ian,
On Sun, Jul 07, 2013 at 10:37:34AM +0100, Ian wrote:
The AWS-hosted service is not working for me at the
moment if I do a
traceroute from the server to two addresses I know have been used, I
get this:
But all this proves is that traceroute is blocked.
Port 80 TCP seems to work for me:
$ sudo tcptraceroute 54.224.171.85 80
Selected device eth0, address 85.119.80.223, port 38020 for outgoing packets
Tracing the path to 54.224.171.85 on TCP port 80 (www), 30 hops max
1 president.bitfolk.com (85.119.80.16) 0.181 ms 0.070 ms 0.064 ms
2 jump-gw-4.lon.bitfolk.com (85.119.80.4) 0.372 ms 0.269 ms 0.242 ms
3 * * *
4 xe-6-0-3.r22.londen03.uk.bb.gin.ntt.net (129.250.6.52) 0.574 ms 0.553 ms 0.673 ms
5 ae-4.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.126) 68.628 ms 68.893 ms 68.721 ms
6 ae-0.r23.nycmny01.us.bb.gin.ntt.net (129.250.3.73) 68.716 ms 68.656 ms 93.718 ms
7 ae-5.r20.asbnva02.us.bb.gin.ntt.net (129.250.2.183) 101.893 ms 85.113 ms 85.150 ms
8 ae-1.r04.asbnva02.us.bb.gin.ntt.net (129.250.3.17) 85.567 ms 85.570 ms 85.583 ms
9 ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38) 76.055 ms 122.410 ms 80.925
ms
10 72.21.220.29 75.326 ms 75.298 ms 128.344 ms
11 205.251.245.65 85.463 ms 85.474 ms 85.683 ms
12 * * *
13 * * *
14 * * *
15 216.182.224.241 76.584 ms 75.871 ms 75.882 ms
16 * * *
17 * * *
18 * * *
19 ec2-54-224-171-85.compute-1.amazonaws.com (54.224.171.85) [open] 77.399 ms 77.240 ms
77.141 ms
$ telnet 54.224.171.85 80
Trying 54.224.171.85...
Connected to 54.224.171.85.
Escape character is '^]'.
QUIT
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.2.1</center>
</body>
</html>
Connection closed by foreign host.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
3968
days inactive
3981
days old
8 comments
3 participants
participants (3)
-
Andy Smith -
Ian -
Paul Lewis