Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Mars Edit Trial Problems with Auto Detect, xmlrpc, Http Username

edited December 2010 in MarsEdit
I'm attempting to use Mars Edit for the first time. I'd like to use it to post to Wordpress on my site.
The auto detect failed.

I entered the following:
to see if the API Endpoint URL is correct, and go the following message:
"You don't have permission to access /wp_blog/xmlrpc.php on this server."
So, I may not have that set up correctly. Please let me know what I need to do here.

Also, I am getting prompted to enter the HTTP username and password. I am sorry, but I don't know what a HTTP username is? Please explain.



  • jemjem
    edited December 2010
    If you get prompted for HTTP username it usually means that you (or someone else) has set up the site to require user/password before someone can use view it.

    The first error you describe is probably the cause of this, the server doesn't allow MarsEdit to access the end-point.

    The solution should be that when asked you enter the user/password you enter to view the site.


    I just went to the site and I get the same error message in my browser, also if I check the URL then I get a 404 error -- the files that makes up the WP blog has been removed (so MarsEdit can't find them either). Have you set RapidWeaver to remove files that are non-RW files?
  • Hi jem,

    Thanks for the reply.
    I only have two possible username and passwords:
    1. for my ftp uploads to the site
    2. for login to my WordPress admin
    Neither one of these allows me in from the HTTP Username/password request that I am getting from Mars Edit.

    Thanks for checking my site... the 404 error is due to your use of a dash instead of an underscore -- meaning it is /wp_blog.

    Any other thoughts would be appreciated.

  • Hi Bruce - it looks like something about the configuration of your server, or the policy of your web hosting company, is causing the XMLRPC API to be inaccessible:

    If you try to load that in a browser you'll see an error. This should load in the browser successfully if MarsEdit is going to be able to connect to it.

    You can ask your hosting company's support team to "make it so clients have GET and POST access to this URL:\", and that should take care of it if they fix that.

    (I think the requests for username/password are just a confusion on MarsEdit's part - since the error from your server is "Forbidden" it 's assuming it just needs to authenticate).

  • I can confirm the the current trial of MarsEdit 3.2.2, is not able to properly detect Wordpress blogs. I suspect that this could be specific to blogs running in the root of the domain and for domains without www. Example:

    If I manually specify the XML-RPC file for API it will work, but for a commercial product I would not expect to find a bug in less than one minute after installation.
  • It would help a great deal if you can share the home page URL for an example blog that is not being auto-detected by MarsEdit. If that is too private, then the next best thing would be to examine the home page source, and see if it contains a line like this:

    <link rel="EditURI" type="application/rsd+xml" title="RSD" href="" />

    This is the line that points MarsEdit at the "RSD" for your blog. If the home page doesn't contain this, then it may be a problem with your theme or with other plugins installed (I know you mentioned that it's a WPMU setup, but it should still contain an RSD line).

    If it DOES contain the RSD line, then MarsEdit should be trying to open that URL and look at the configuration info. If you want me to look into this in more detail and are comfortable sharing details about the blog privately with me, please contact me at

Sign In or Register to comment.