XMLRPC, NGX moved permananetly, fatal for BlogDesk

• 

  tim212 · Member · Dec 11, 2014 at 11:29 pm

  • Copy link
  • Add topic to favorites

  Several people are reporting BlogDesk fails on upload, reporting an XMLRPC error. An ethernet trace shows the WordPress response is moved permanently, which for whatever reason Blogdesk cannot handle and of course might not be the actual change.

  This has worked reliably for years, I have many hundreds of posts (~700), some large on more than one blog.

  XMLRPC is working normally with WordPress from here with my own code, nothing to do with the above.

  What has changed? No change here.

  The blog I need help with is: (visible only to logged in users)

• 

  tim212 · Member · Dec 12, 2014 at 1:24 am

  • Copy link

  Thread originator writes: –

  I may have found a solution and if true will help other people.

  Reconfiguring BlogDesk to specifically use port 443 and SSL seems to work. (I’d assumed handover was automatic) Why 80 worked for a number of years, well, life.

  This makes some sense given the recent wild time over OpenSSL security issues on servers. The permanent move might be to SSL so a direct call to the SSL initial port might be removing whatever was causing trouble.

  Successfully put up a minor post. Normal practice is rough offline, upload and then final edit online.

  Lets wait and see. Not changed to resolved just yet.

• 

  tim212 · Member · Dec 25, 2014 at 2:27 am

  • Copy link

  Traced this to erratic behaviour by WordPress servers.

  Some xxx.wordpress.com sites insist on HTTPS and some xxx.wordpress.com sites accept HTTP