Could you post your site URL here, so I can have a look?
If you want it to remain private, you can also contact us via this contact form:
http://jetpack.me/contact-support/
If you contact us through our form, please make sure to include a link to this thread in your message.
Also, have you turned off the Monitor module?
Thread Starter
Steve
(@steveatty)
Its all the subdirectory blogs on blogs.canalplan.org.uk
The monitor module is not enabled on any of the sites as far as I can see
I’m also seeing the uptime monitor POSTing to the xmlrpc.php file on wordbooker.tty.org.uk. The monitor module is not enabled there either
Can you list every site for me? That way I can make sure that Monitor is off for those sites.
Thread Starter
Steve
(@steveatty)
sure
They’re
/
/steve
/development
/mintball
/canalplanac
Steve
Hi Steve,
All those sites seem to be blocking access to the xmlrpc.php file behind an HTTP authorization login prompt. As such, Jetpack can’t function with these sites (including wordbooker.tty.org.uk). Can you try disconnecting all these sites from WordPress.com on your end, and let me know if you continue to get Monitor emails for them?
Thread Starter
Steve
(@steveatty)
I wasn’t getting monitor emails
I was seeing lots of monitor accesses making POSTS to xmlrpc.php when the monitor was not enabled.
Why is Jetpack making post calls to xmlrpc anyway?
Hi Steve,
Can you show me exactly what it is you see in your log? I’ll then confer with the developpers to find the reason for those calls. Thanks!
Thread Starter
Steve
(@steveatty)
This is what I was seeing:
66.155.10.75 - - [12/Apr/2014:23:06:31 +0100] "POST /steve/xmlrpc.php?for=jetpack HTTP/1.1" 200 348 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [12/Apr/2014:23:22:08 +0100] "POST /development/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:00:45:35 +0100] "POST /xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:00:45:37 +0100] "POST /mintball/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [13/Apr/2014:01:36:55 +0100] "POST /canalplanac/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:03:09:53 +0100] "POST /steve/xmlrpc.php?for=jetpack HTTP/1.1" 200 348 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:03:26:22 +0100] "POST /development/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:04:50:03 +0100] "POST /xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.75 - - [13/Apr/2014:04:50:04 +0100] "POST /mintball/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [13/Apr/2014:04:50:05 +0100] "POST /canalplanac/xmlrpc.php?for=jetpack HTTP/1.1" 200 409 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [02/Apr/2014:04:56:01 +0100] "POST /canalplanac/xmlrpc.php?for=jetpack HTTP/1.1" 200 448 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [02/Apr/2014:05:06:21 +0100] "POST /steve/xmlrpc.php?for=jetpack HTTP/1.1" 200 448 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [02/Apr/2014:05:14:40 +0100] "POST /development/xmlrpc.php?for=jetpack HTTP/1.1" 200 448 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [02/Apr/2014:05:40:18 +0100] "POST /xmlrpc.php?for=jetpack HTTP/1.1" 200 448 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [02/Apr/2014:05:40:20 +0100] "POST /mintball/xmlrpc.php?for=jetpack HTTP/1.1" 200 448 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [03/Apr/2014:13:42:28 +0100] "POST /canalplanac/xmlrpc.php?for=jetpack HTTP/1.1" 200 569 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [03/Apr/2014:13:57:44 +0100] "POST /steve/xmlrpc.php?for=jetpack HTTP/1.1" 200 569 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [03/Apr/2014:14:03:04 +0100] "POST /development/xmlrpc.php?for=jetpack HTTP/1.1" 200 569 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [03/Apr/2014:14:26:54 +0100] "POST /xmlrpc.php?for=jetpack HTTP/1.1" 200 503 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
66.155.10.74 - - [03/Apr/2014:14:27:00 +0100] "POST /mintball/xmlrpc.php?for=jetpack HTTP/1.1" 200 503 "-" "jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)"
[Moderator Note: Please post log files between backticks or use the code button.]
It has stopped now – and these were from when I’d taken the .htaccess rule off
It has stopped now – and these were from when I’d taken the .htaccess rule off
What does this mean, exactly? YOu don’t see this anymore at all, or you are blocking them?
Thread Starter
Steve
(@steveatty)
I don’t see them any more
But why was I ever seeing them? I never activated the Jetpack uptime monitor and why is Jetpack attempting repeated POST calls to the xmlrpc file?
Howdy, Steve.
The User Agent string identifying Jetpack Monitor was a bit of a goof on our part — it was part of a maintenance system where the WordPress.com servers were touching base with remote Jetpack sites to determine version, but we accidentally left the wrong User Agent in place! Sorry about that.
That being said, Jetpack is a two-way connection between your WordPress.org site and WordPress.com. In fact, if WordPress.com can’t reach your site via XMLRPC, it won’t even be able to connect in the first place. This can be for purposes of the JSON API module, post indexing for Related Posts, or — as was the case for this — checking your Jetpack version and testing for potential vulnerabilities concerning our recent Security Release.
