Error 301 Moved permanently

• 

  augustine04 · Member · Nov 25, 2014 at 3:13 pm

  • Copy link
  • Add topic to favorites

  please help me provide a solution,,,,i do have a problem posting a content on my blackberry worldpress app,,,,with an error that said… SERVER ERROR 301 MOVED PERMENANTLY… please a quick reply with a solution thanks.

• 

  binzaranda · Member · Dec 19, 2014 at 2:10 pm

  • Copy link

  I can’t make a post in my blog binzaranda.wordpress.com. It said server error 301. Moved permenantly .

• 

  cyberlwl · Member · Jan 4, 2015 at 1:59 am

  • Copy link

  I have the same issue using the API across all of my WordPress.com-hosted blogs. For instance, cloudpundit.wordpress.com has this issue. I’m using the metaweb API with XML-RPC, pointed at http://cloudpundit.wordpress.com/xmlrpc.php

  It appears that we’re not the only users with this error. I see github reports of supposed errors with XML-RPC libraries that are used by blogging clients to communicate with WordPress.

  Something has clearly changed with WordPress.com. What is it? (I will note that I am thus far able to use the API just fine with non-Wordpress.com-hosted WordPress blogs.)

• 

  timethief · Member · Jan 4, 2015 at 3:44 am

  • Copy link

  @augustine04
  Have you tried posting to this support forum?
  http://blackberry.forums.wordpress.org/
  If you don’t have a username account at WordPress.ORG click http://wordpress.org/support/ and register one on the top right hand corner of the page that opens, so you can post to the support forums there and receive advice from WordPress.ORG bloggers.

• 

  cyberlwl · Member · Jan 4, 2015 at 4:21 am

  • Copy link

  @timethief, I would bet that his issue is exactly the same as mine. I’m guessing it has something to do with the change of endpoints from http to https endpoints. Because of that, it’s going to impact all clients that use the API in similar ways.

  I’ve found that the python library python-wordpress-xmlrpc, which uses the WordPress native API rather than the metaweb API, fails in the exact same way when giving an http endpoint. However, it’s fine when http is changed to https.

• 

  worldwebventures · Member · Jan 20, 2015 at 12:25 am

  • Copy link

  I am receiving this exact error.

  I have an application that remotely posts to http://mydomain/wordpress.com/xmlrpc.php that worked perfectly until Jan 12th.

  Now, I am getting the following error when trying to post remotely:

  “00201138 Can’t connect:The server responded with an error: http/1.1 301 moved permanently”

  I did not change anything – it just stopped posting, even though I can see that there are plenty of posts to post.

  This is very similar to the above posts, and the post here: https://wordpress.org/support/topic/xml-rpc-newpost-broke-when-site-changed-to-https

  Thanks!

• 

  raincoaster · Member · Jan 20, 2015 at 12:28 am

  • Copy link

  Many people are reporting this error.

• 

  worldwebventures · Member · Jan 20, 2015 at 12:32 am

  • Copy link

  BTW – I did try changing my posting URL from http://site/wordpress.com/xmlrpc.php to https://site/wordpress.com/xmlrpc.php and it didn’t fix it.

• 

  worldwebventures · Member · Jan 21, 2015 at 1:47 pm

  • Copy link

  I have read that WordPress.com has changed its websites to go to https instead of http.

  Could this be the issue? If so – what is the resolution?

• 

  worldwebventures · Member · Jan 23, 2015 at 2:15 pm

  • Copy link

  Is there any other troubleshooting I can do within WordPress.com, such as an area where I can review error reporting in WordPress?

  All I know is that what worked before Jan 12th just stopped working with an error of “Can’t connect:The server responded with an error: http/1.1 301 moved permanently” – and I didn’t change anything…

  Thanks!