I have several sites that use a subdirectory for the actual WordPress installation and the site. This use to be a very common practice and still is in some circles as it allows the WordPress installation to stay pure and very easily manageable with tools like Composer and others.
However, it appears that the support forums and other sites are littered with problems concerning Jetpack and more importantly WooCommerce not being able to connect back.
The issue also represents itself as an xmlrpc connection issue.
I have checked high and low; and cannot find a way to change the behavior or allow for Jetpack and Woocommerce and www.remarpro.com site in general to connect back to my site.
I have this occurring on three sites that are using a new layout / design setup that uses a subdirectory for the actual WordPress installation files.
I know many others have seen this issue.
Can someone help me with how they ended up resolving it?
]]>
The environment:
– PHP: 8.2 (ea-php82)
– WordPress 6.7.1 with Customify theme
– WP and plugins are up to date
– The app is on Android Xiaomi Hyper OS
What I’ve tried based upon suggestions I’ve found in this theme:
The plugin wrote on the link unfortunately doesn’t do anything.
However, I found xmlrpc.php in the file browser on the hosting, so I tried in manual mode.
1st try with the solution written on the link:
Based on xmlrpc.php I’ve created a copy called xmlrpc2.php.
I got a little help with whis: “you might want to check if it works correctly after the renaming by typing (https://barangolasok.hu/xmlrpc2.php) into the browser’s address bar, and you should get the same result as you see now when typing https://barangolasok.hu/xmlrpc.php: XML-RPC server accepts POST requests only.”
So in the browser the result is: XML-RPC server accepts POST requests only
.
I set https://barangolasok.hu/xmlrpc2.php
in the app, unfortunately the result is still IP ban.
2dn try:
In the xmlrpc2.php file I replaced all xmlrpc.php strings with xmlrpc2.php and updated the file on the server.
In the browser the result is: XML-RPC server accepts POST requests only
.
I set https://barangolasok.hu/xmlrpc2.php
in the app, unfortunately the result is still IP ban.
3rd try:
While searching, I came across a page where this file can be validated https://xmlrpc.blog/https://barangolasok.hu/xmlrpc.php
→ Congratulations! Your site passed the first check.
You can add the blog within the mobile app using the following URL: https://barangolasok.hu/xmlrpc.phphttps://barangolasok.hu/xmlrpc2.php
→ Congratulations! Your site passed the first check.
You can add the blog within the mobile app using the following URL: https://barangolasok.hu/xmlrpc2.php/xmlrpc.php
This is interesting because it does not write only xmlrpc2.php.
Despite this, I tried all three ways, but unfortunately the result is the same, IP ban.
https://barangolasok.hu/xmlrpc.php
https://barangolasok.hu/xmlrpc2.php
https://barangolasok.hu/xmlrpc2.php/xmlrpc.php
4th try:
Renamed xmlrpc.php to xmlrpc.old on the server so that only xmlrpc2.php remains, but the page doesn’t work at all.
I am a simple user, I don’t know too much about WP.
I welcome any suggestions, thank you
Expected behaviour: Disabling top-option should also disable sub-option.
No Nonsense 3.5.0, WordPress 6.6.2
]]>OLW reports:
“Unexpected error has occured while attempting to log in:
Invalid Server Repsonse – The repsonse to the blogger.getUsersBlogs method received from blog server was invalid:
Invalid response document receioved from XmlRpc server”
OLW is unchanged in years. I have several wholly different sites that all behave the same. Something appears to be broken.
In the migration, the xmlrpc.php is now stored in the /cms directory. Is there a way we can update this in Jetpack or something the service can help resolve?
]]>on my website xmlrpc is active and running (when your plugin is deactivated).
Actviating the plugin, xmlrpc is not possible anymore and is not reported in the lists for whitelisting. So in principle, is it possible to use XMLRPC along with CSP active? Or what could be the reason this does not work here?
]]>I have a site in which, after activating an activity log plugin, I have discovered unauthorized admin account logins despite changing password multiple times, using long randomly generated passwords. I have already blocked xmlrpc.php using a plugin. When I checked visit logs in C-Panel, matching the suspicious login IP address and time to that recorded in the dasboard’s activity log (plugin), it looks like login was via example.com/wp-json/wp/v2/users (where example.com is our own url) which I think has something to do with REST API. It looks like the hacker was able to somehow login WITHOUT a password.
I understand I can easily disable the /wp-json/wp/v2/users but we NEED REST API because xmlrpc.php has been disabled (which helped reduce brute force attack) and we have plugins (such as Mail SMTP) that require connections to third party sites such as Google (where secret keys are used). How can I secure the site and still be able to use REST API?
]]>