TOO MANY REQUESTS AND LOGIN FAILS

@lastsplash Looks like requests are reduced. Does it reduces any features or performance/?
And would like to know why those requests are made and for which feature.

@lastsplash @gwberto also, I have some more sites that needs to reduce these requests.

Hi @akiraanastasia

The change that was made was in the typc of sync used for your site to commmunicate with WordPress.com. We had changed this from Dedicated sync to Incremental sync which seemed to lessen the number of requests. This should have no impact on features or performance.

If you want to send us the other sites, we can make that change there as well.

Ok, where I can send site urls.

Hi @akiraanastasia –

If you can share them here, that would be easiest. Otherwise, if you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.

Thanks!

Okay, Some of them are these: Nature Blog, Crypto Blog
Please reduce those requests. Other sites I will send you in form.

• This reply was modified 1 year, 11 months ago by akiraanastasia.
• This reply was modified 1 year, 11 months ago by akiraanastasia.

Some of them are these: Nature Blog, Crypto Blog

Both of those sites have broken connections to Jetpack. In order to change the sync system, we’ll need to have a working Jetpack connection.

On both sites, I see 503 Service Unavailable errors. Please make sure that your site’s xmlrpc.php file is publicly accessible and that you don’t have any plugins or server settings blocking access. You may need to allow access to our IPs as described here:

https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

Let us know once you have made those changes and we can check on the connection and make the adjustment.

@lastsplash just checked, it is showing connected to Jetpack. Where i need to change any settings../?

Hi @akiraanastasia,

We made the same changes for Nature Blog, which should reduce the number of Jetpack sync requests made to that site.

For?Crypto Blog, diagnostics show that we’re getting 403 Forbidden errors when Jetpack tries to perform sync actions, so it looks like you’re already blocking some incoming sync requests somehow for that site.

@ihenetudan ok thanks.
About the crypto blog, it is getting blocked bcz jetpack sends so many requests. So once IP gets removed from the block list (Its auto blocking), the same problem will start again. So please reduce the requests from your side.

@akiraanastasia

Unfortunately, we can’t make that change from our side without a working connection. It’s a change that needs remote access.

I hope this helps explain the situation!

@ihenetudan Just removed that IP from block list. Please check now.

Hi there

We are still getting 403 errors on Crypto Blog. Please double check that you have allowed Jetpack’s full IP range, as specified here.

@drawmyface added all IPs in list. Please check.

No change I’m afraid. The response is:

HTTP/1.1 403 Forbidden
Date: Wed, 18 Jan 2023 12:23:50 GMT

It looks like you may have a security plugin installed that is blocking Jetpack’s requests. If you’re able to add exceptions in the plugin settings you can try that, otherwise I’d suggest disabling that security plugin so that Jetpack can connect successfully.