Posting to Your Own Wordpress Site
Accidentally erased my post. 

Anyway, testing posting to my own Wordpress.
Using two accounts for each Wordpress engine in the Articles section of SER Engines, not sure which is correct. (The three engines I am testing are: WordPress Forum, Wordpresss XMLRPC (Article), and Wordpress Article (Article). I've tried all three.
One project for each engine uses a username and PW that I already made in Wordpress. Not sure if that works...
The other project for each of the Wordpress Article engines creates an account with a random username and PW.
Nothing is working. It's not even getting that far. 

Here is the SER log:
Any help would be greatly appreciated.
01:00:44: Setting up project
01:00:44: Setting up project
01:00:44: Setting up project
01:00:44: Setting up project
01:00:44: Setting up project
01:00:44: Setting up project
01:00:44: Starting project
01:00:44: Starting project
01:00:44: Starting project
01:00:44: Starting project
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: Starting project
01:00:44: Starting project
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: [ ] Loaded 1 URL from imported sites
01:00:44: [-] 1/1 no engine matches - ht tp://----------- .com/
01:00:44: [-] 1/1 no engine matches - h ttp://----------- .com/
01:00:44: [-] 1/1 no engine matches - h ttp://----------- .com/
01:00:44: [-] 1/1 no engine matches - htt p://----------- .com/
01:00:44: [-] 1/1 no engine matches - h ttp://----------- .com/
01:00:44: [-] 1/1 no engine matches - htt p://----------- .com/
01:00:44: [+] 1/1 matches engine Wordpress Article - ht tp://----------- .com/
01:00:44: [+] 1/1 new URL - ht tp://----------- .com/wp-login.php?action=register
01:00:44: [+] 1/1 new URL - ht tp://----------- .com/wp-login.php?action=register
01:00:44: [-] 1/1 wrong engine detected (!page not found) - ht tp://----------- .com/wp-login.php?action=register
01:00:44: [+] 1/1 matches engine Wordpress Article - htt p://----------- .com/
01:00:44: [+] 1/1 new URL - ht tp://----------- .com/wp-login.php?action=register
01:00:44: [+] 1/1 new URL - h ttp://----------- .com/wp-login.php?action=register
01:00:44: [-] 1/1 wrong engine detected (!page not found) - ht tp://----------- .com/wp-login.php?action=register
Comments
The Wordpress XMLRPC engine is sufficient to be able to publish on your Wordpress sites, add "/xmlrpc.php" to your urls.
<methodResponse>
<fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value>
<int>405</int>
</value>
</member>
<member>
<name>faultString</name>
<value>
<string>XML-RPC is disabled</string>
</value>
</member>
</struct>
</value>
</fault>
</methodResponse>
13:23:59: [+] 1/1 matches engine Wordpress XMLRPC - htt p:/zzzzzzzzzzzzzzzzzzzzzzz/xmlrpc.php
13:23:59: [+] 1/1 matches engine Wordpress XMLRPC - ht tp://zzzzzzzzzzzzzzzzzzzzzzz
13:23:59: [-] 1/1 unknown login status - ht tp://zzzzzzzzzzzzzzzzzzzzzzz/xmlrpc.php
I haven't used CF for a long time, it should be able to allow you to unblock IPs, but if you use proxies, it gets complicated.
“files/xmlrpc.php” Inside ‘files’ is the WP installation?
I'll answer you first thing tomorrow, now I'm going to the living room (in Spain it's late already)
Or change: “./xmlrpc.php” to “%original_targeturl%”, you'll have to do your tests, because I haven't tried any of this.
About using the PUBLIC_HTML folder of the hosting as destination of the subdomains, the domains you have added should not resolve that PATH in URL, but keep the sanity of “ht..p://example.this/xmlrpc.php”.
I don't know if you use CPanel or Plesk, but with CPanel you can quickly change the PATH of each hosted domain by making a previous backup.
It is a security risk to host sites inside the PUBLIC_HTML folder, I strongly recommend you to move them to the ROOT.