admin-bar-v2.js?ver=12.2.1-202324-lite:1 Missing data from PHP

Hi @fotov60

The only thing I can see that might be relevant is that your xmlrpc.php file is not available. It simply redirects to your homepage:

https://www.fotov60.com/xmlrpc.php

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://wp.cloud/xmlrpc.php

I would recommend that you check the following:

1. Can you see the /xmlrpc.php file at the root of your WordPress installation when accessing your site via FTP? If you don’t, then please try re-installing WordPress. You can do this by going to the Dashboard -> Upgrades page, then click the “Reinstall” button.
2. Do you use any security plugins that may block access to this file? If so, could you try to disable them? You might also want to check your site’s .htaccess file for any rules that might be blocking access to the xmlrpc.php file.
3. Does your hosting provider block access to this file? If you don’t find any plugin that may block access to the file on your site, I would recommend that you get in touch with your host.

Once we are able to access your site’s xmlrpc.php file, please try to reconnect your site:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reconnecting-jetpack

If you want to learn more details about XML-RPC and how it interacts with Jetpack, you can check out our detailed guide here: https://jetpack.com/support/jetpack-and-xml-rpc

I had already discussed this issue with my hosting provider to clarify it (after reading this text “You should be able to protect a site’s XML-RPC file without having to allow specific IP ranges. The most popular hosts use tools like fail2ban or ModSecurity, for example.” on Jetpack’s website), and after exchanging messages, their response was:

In our service with you, there is protection for the "xmlrpc.php" file, which only allows connections from JetPack and some known applications.

Therefore, I believe that the issue wouldn’t be with the xmlrpc.php file since, according to them, the connection is allowed, and I also have Jetpack linked to my WordPress.com account.

Hey @fotov60 – I’d like to start by apologizing for not getting back to you before. Unfortunately, we have received an unusual amount of support requests, which is delaying our response time, and we generally answer in the order received. I would like to assure you that this is not a common occurrence, and we are doing our best to get up-to-date.

Here are some steps you can take to troubleshoot and potentially resolve the problem:

1. Uninstall/Reinstall: Please delete the Jetpack plugin and reinstall the fresh copy from WordPress. Check the if the issue is still there? If yes, then check the next point:
2. Clear Cache: Start by clearing your browser cache to ensure that you do not see any cached or outdated data. Check the if the issue is still there? If yes, then check the next point:
3. Check with a different new browser. Check the if the issue is still there? If yes, then check the next point:
4. Disable Plugins/Themes: Although you mentioned that the issue occurs when Jetpack is active and other plugins are deactivated, it’s worth double-checking if there are any conflicting plugins. Temporarily deactivate all plugins except for Jetpack to see if the issue persists. Similarly, switch to a default WordPress theme (such as Twenty Twenty-One) to rule out any conflicts with your current theme.
5. Disable Jetpack Plugin: Could you please confirm if the issue disappears on disabling the Jetpack plugin?
6. Disable Jetpack Modules: Jetpack offers various modules with different functionalities. Disable all the Jetpack modules and enable them one by one to identify if a specific module is causing the issue. This way, you can narrow down the source of the problem.

Remember to always back up your website before making any changes or updates, and follow best practices for troubleshooting to avoid any potential data loss or further issues.

Hello @fotov60

Do you have updates about that? We usually close inactive threads after one week of no activity, but we want to make sure we’re all set before marking it as solved. Thanks!

Due to personal problems I have not been able to review it, but I will try to do so soon and update the answer with any changes.

An issue has been opened on GitHub for this error message.

Hi @gwynethllewelyn – thank you for the detailed post there!