Blocked Script Execution

Hi there,

I checked your site, and currently, the Jetpack connection is not good. We will need first to resolve the issue here, and if the same error persists even after that, then we can go ahead with the next steps.

Why is the Jetpack connection not good?

While your site is publicly accessible, we cannot access your site’s XML-RPC file. This file is used by Jetpack and other plugins and apps to connect to your site. It must return the following message: XML-RPC?server accepts POST requests only.

You can see a working example here: https://jetpack.com/xmlrpc.php

Since you can see the Cloudflare is blocking your XML-RPC file. I would recommend you temporarily disable Cloudflare and try to connect Jetpack Boost again with your site. After connecting Boost, you can verify if Jetpack is get successfully connected by visiting here: https://jptools.wordpress.com/debug

If you see the message “Everything looks great!” then it means the Jetpack connection is good and now you can check if Blocked script execution in '<URL>' because the... error is still there?

Let me know how it went!

Jetpack connects with WordPress.com.

Have special rules in place to allow access to xmlrpc.php to Jetpack and WordPress but block for rest.

Now critical CSS is being generated but the error I mentioned above does occur.

Error occurs in Brave as well as Chrome browser.

Plus once you install the Jetpack Boost plugin you can’t delete.

Hi @iamkunaldesai

Apologies for the confusion here – you don’t actually need the Jetpack plugin installed and connected on your site for Jetpack Boost to work, however the connection flow is similar.

If you use a Web Application Firewall service such as CloudFlare which it appears you do, can you please configure a rule to allow access to your site from 35.188.32.9? Boost’s speed scores are always returned from that address.

You should be able to delete the Jetpack Boost plugin after installing it. However we’ve just received similar reports so it looks like there may be a temporary issue deleting the plugin here. We’re looking into this and will let you know as soon as that is resolved!

• This reply was modified 3 years, 4 months ago by Karen Attfield. Reason: Adding information about plugin deletion issue

Hi @iamkunaldesai

Regarding the plugin deletion issue, we have investigated further and have found the cause of the issue. During deletion, the plugin is trying to clear up a few things, but one of them fails due to leftover legacy code. This will be fixed in the next release.

In the meantime, you can either:
1. Delete the plugin manually. The process of doing it might depend on your hosting. You might be able to do it via FTP, or via SSH access.
2. Delete the plugin via the Dashboard by following the instructions in this video clip: https://cloudup.com/cLf_E6ZSS8F

Hope that helps!

Not generating critical css on search pages.

Thanks for the report, we’re looking into this and will get back to you when we have an update.

Hi @iamkunaldesai –

At present, we don’t generate Critical CSS on search result pages.

Critical CSS only speeds up rendering when all the relevant CSS files aren’t already cached on the user’s browser. For example, the first time the user lands on a site or browses to an area of the site which uses different CSS files.

Search results pages wouldn’t normally be the first page on a site users land on. By the time users see search results, their browser will generally have your theme’s main CSS files cached.

Hi there,

It has been more than one week since we have heard from you, so I’m marking this topic as resolved. But If you have any further questions or need some more help, you’re welcome to reply here or open another thread.