1.JetPack plugin error: The Jetpack server was unable to communicate with your site https://pdfmz.free.nf [IXR -32300: transport error: http_request_failed cURL error 52: Empty reply from server] (Status 500)
2. WordPress mobile app error: The site under this address is not a WordPress site. In order for us to connect, this site must use WordPress.
Other Information
I installed the ‘Rename XMLRPC’ plugin for this matter and followed the online tutorial to copy and rename ‘xmlprc.php’ to ‘xmlprc2.php’. Although I can access’ pdfmz.free.nf/XMLprc2php 'in the browser, the WordPress mobile version cannot detect JetPack and still cannot connect. What should I do？
Non-browser devices are blocked from accessing your website. I recommend deleting g the jet pack plugin, it is very resource intensive and you probably don’t need all the features it provides.
You can’t use the JetPack plugin (there are many reasons why it doesn’t work on InfinityFree hosting).
Also, you can’t use the LiteSpeed Cache plugin because InfinityFree servers run on Apache, not LiteSpeed.
Many other plugins might not work properly either because the Cron Job on InfinityFree hosting is disabled and doesn’t actually run.
I’ve tested all cache plugins and did a lot of research. In my opinion, the best option is WP Fastest Cache. I’ve tried both the free and premium versions. Honestly, the premium version isn’t worth much and there’s no significant difference compared to the free one. I can even say the free version is better (because it’s free ).
However, even if you use WP Fastest Cache, automatic cache won’t work properly due to disabled cron. To manually preload the cache, you can visit this link:
your-site.com/?action=wpfastestcache&type=preload
That said, I don’t usually do this because even without manual preload, the plugin still performs
some compression and optimizations and works quite well.
If you want to know more about the preload feature of this plugin, you can click here: Preload Settings
I would avoid all cache plugins altogether. InfinityFree’s servers enforce caching for static items, and depending on the size of the WordPress site, it doesn’t always work. I’ve found that WordPress sites load/run at acceptable speeds, so I don’t see the need for caching plugins anyway.
Page level caching can be very useful, especially if you have complex site. It can save a lot of database queries and processing.
A simple WordPress site is fast enough, but when you start adding big, complex plugins, it can slow down a lot.
LiteSpeed Cache is indeed not a good choice. It’s intended to be used with LiteSpeed Server, which we don’t have. Some functionality will still work without LiteSpeed Server, but better options exist in my opinion.
To clarify, this only affects the Preload Cache feature, an optional feature that can be used to reduce the delay on the first page view where the cache doesn’t exist yet.
It will still “work properly” without this, and the cache will work exactly like how a cache is supposed to work. Preload is admittedly a cool feature, but your site will work fine without it.
).