guneet narula

Thanks for the response.

Here’s the output of the curl command with –resolve:

HTTP/2 200 
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
content-type: text/html; charset=UTF-8
content-length: 0
date: Mon, 12 Dec 2022 11:02:37 GMT
server: LiteSpeed
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

We have WP Control plugin installed, and we are able to run some of the tasks manually through it.

Hi,

We get a HTTP 200 response in the browser and in the terminal.

When we run the command curl -I -XGET https:/yourdomain.com/wp-cron.php?doing_wp_cron

Output is:

HTTP/2 200 
expires: Wed, 11 Jan 1984 05:00:00 GMT
cache-control: no-cache, must-revalidate, max-age=0
content-type: text/html; charset=UTF-8
x-litespeed-tag: 4b6_
content-length: 0
date: Fri, 09 Dec 2022 18:38:39 GMT
server: LiteSpeed
x-qc-pop: AS-IN-DEL-59
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

Thanks for the reply. Do you mean the Jetpack site accelerator for static files and images, or our DDOS protection service that includes caching as well.

Yes it worked itself last night, sorry I was going to resolve this myself.

Just FYI, I had generated a new key a couple of days ago (browser, any referral), it didn’t work immediately. Last night I happened to update to 3.0.5, that did the trick. I still feel your assessment that this is a Google problem is more accurate. Unless something drastic changed in 3.0.5

Thanks a lot though!

Thanks, but that was part of the instructions followed in the beginning. After doing all that, the error occurred.

Okay, I will report back soon.

Thanks!

Well I have not typed ‘anyone’ anywhere ??

I left the referrer field blank so it says ‘Any Referrer allowed’ in the summary page.

Yes I have used the browser key. I saw that error myself, I thought it was a restriction on the referrer. So I changed that to ‘anyone’

Also: I have updated the referrers to ‘any referrer allowed’ for the time being.

Just updated to version 3.0.3 after following instruction on the API key, same error when I use the widget: ‘Ups, something went wrong’

Sorry, my mistake. It was wp-twitter-widget.php.

And I am using 2.5.2, I just saw that an update has come in. I guess I should install the new version and then check