That doesn’t sound good. The Jetpack plugin doesn’t include that sentence anywhere in its code, so you may have been hacked. I’d suggest going through the steps here:
https://codex.wordpress.org/FAQ_My_site_was_hacked
Let me know how it goes.
Hey Jeremy…
I have gone through the steps… spent four hours we four different adware/spyware.malware detection tools. They found nothing on my laptop. Then I used google developer and it found no anomalies and then I downloaded sucuri and ran full diagnostics on the site and they found no bad code or malware or anything. The site is designated clean.
The issue resolved itself after five hours but it has given me cause for concern. Like whatever the problem was, it has not been dealt with properly and could just reoccur at any given point.
You have any ideas for me at all. I would love to put this to bed.
Thanks for you help.
Mark
You have any ideas for me at all. I would love to put this to bed.
It might be worth installing a security scanning plugin on your site, to look into this a bit deeper and get results that may be different from outside scanning services like Sucuri’s sitecheck. Sucuri offers such a service, and VaultPress does too.
Thanks Jeremy. I already installed the plugin from Sucuri.
But if you hear of anyone else with the same issue and you manage to work out what it was please let me know.
Cheers
Sure thing, I’ll post again here if I ever get a similar report from someone else!
Same problem here. Only shows up on Chrome from time to time, and disappears when clearing cache and cookies.
Even though the words are not in the source code, I’m sure it’s part of the handshake that goes on when jetpack checks that external connections to the site are available.
Chrome’s “Data Saver” extension might be responsible – if disabled, it goes away, at least when you shift-refresh.
I’m sure it’s part of the handshake that goes on when jetpack checks that external connections to the site are available.
I looked for “All systems go” in all our codebase, including what’s handling the connection itself, and couldn’t find such reference.
Chrome’s “Data Saver” extension might be responsible – if disabled, it goes away, at least when you shift-refresh.
Thanks for the info!
@kissthecore Do you happen to be using that extension as well?
Nope. Not me. But I haven’t had that issue reoccur since that first post nor have I had any complaints from readers.
Thankfully.
Hello,
I’m writing to add to reports of the same issue and hopefully to help narrow down the possible causes.
Here are a few items I’m thinking through for my own setup. I have yet to find the cause. Flushing all caches (local and network edge) seems to help:
– I maintain similarly configured WP sites on GoDaddy Managed WP and WPEngine accounts, and so far I have only seen the issue on the former.
– The issue has appeared twice on one site. Both times were in close proximity to Jetpack Plugin updates. The site on which the issue appears is set to update plugins automatically.
– When the issue has appeared, it has not affected all users. Only some are seeing the “Hi jetpack! All systems go.” message. This fact has me wondering whether there is an issue with CloudFlare edge caching and Jetpack plugin updates.
– GoDaddy managed WP utilizes an automatic object caching mechanism. In terms of local caching, I’m wondering whether there is an issue with the object cache not flushing properly during the automatic plugin update.
– The site on which the error occurs utilizes CloudFlare’s flexible SSL feature and full page caching.
– Flushing all local and edge caches seems to have solved the issue for a majority of the site’s users, but I have at least one user claiming that flushing his browsers cookies and cache after I flushed the server caches had no effect (i.e., he still sees the error message when trying to load the site’s homepage).
– The site on which the error is occurring uses the Avada theme.
It’s CloudFlare/chrome
Google search console details as follows – the Page View is , instead of our homepage, Hi Jetpack! All systems go.
But , in most browsers, the homepage renders properly
————————————————————-
HTTP/1.1 200 OK
Date: Fri, 04 Mar 2016 13:25:59 GMT
Content-Length: 30
Connection: keep-alive
Set-Cookie: __cfduid=d46c6b307b2c09f71b0c956c43a3174631457097959; expires=Sat, 04-Mar-17 13:25:59 GMT; path=/; domain=.nordicstaff.com; HttpOnly
X-Cache: uncached
X-Cache-Hit: MISS
X-Backend: all_requests
CF-Cache-Status: HIT
Vary: Accept-Encoding
Expires: Fri, 04 Mar 2016 13:55:59 GMT
Cache-Control: public, max-age=1800
Accept-Ranges: bytes
Server: cloudflare-nginx
CF-RAY: 27e5a847774f020c-IAD
Hi Jetpack! All systems go.
@scderry Thanks for chiming in with more details. I wasn’t able to reproduce the issue with any of my own sites using CloudFlare, but I think your site’s CloudFlare caching settings are different from mine. It might be worth playing with your CloudFlare settings to see if it helps.
Let us know what you find!
In my case it was fixed by removing the caching rule:
http://www.nordicstaff.com/* — cache everything
