Account Wizard Problem: Wordpress

Hmm is this a fresh install or an upgrade.
If you go to your xmlrpc.php file in your browser do you get any feedback? (it should say "XML-RPC server accepts POST requests only" ).

Another option is to rename the file to say test.php and give it a try by manually configuring it in pff (click manual setup and enter the new url).

Let me know if you still have issues.

I do get the "XML-RPC server accepts POST requests only" message when I access the file in my browser. I'll try renaming it and see what happens... will let you know.

Tried renaming xmlrpc.php to test.php, and used that url for the manual login... but still no luck. I get the same message, incorrect username or password.

That is odd. Does your username or password have any 'odd' characters?
Could it be case sensitive?

Well, yes, my password has an ampersand... would that throw it off? Maybe I'll try changing my password and see what happens.

Hello bloggers, I have the same dificulty as Schamess , I'm using Flock browser, tried Firefox, tried an other computer and conection, of course I changed the password, install and reinstall everything ... and saddly ... no results.

I know of other people using wordpress blog on Flock, editing with Performancing, and no problems....

Any sugestions...?

I changed my password to something with only alphanumeric characters - no luck. I still get a message saying incorrect username or password. I'd be grateful for any other suggestions. I see I'm not the only one having the problem...

Just thought I would add this link... same problem:

I have a Wordpress 2.0.2 installation on my site. I've been trying to configure both Flock and Performancing to act as an external blog editor.

Both recognize the blog and prompt for username/password and attempt to log in. But both editors kick back an error which states "Login error. Please check your username and password for errors and try again."

Hi ! I have a Wordpress blog and Performacing tell me the same "Login error. Please check your username and password for errors and try again." Well, I tested all that I could except without a password :-)

I'm using a local proxy, tested without, shutdown firewall (data protection? Even if I don't use it). Performacing tell me the same. I use also macosx Panther and firefox and the problem is the same one as with Windows-firefox.

I also tried to rename xmlrpc.php but always the same message.

Someone knows why ?

Thank you

MiB

I have no idea, I can't reproduce this.
Almost sounds like the wp install is corrupted or disabled.

Did you guys install wp yourself or was it installed by your host or a script from your host? I'm wondering if they are disabling it.

Hi,

I don't have wp installed. Only a blog at wp.com

Maybe a Firefox problem. I found another problem... can't login to my http router "Bad username or password". But this works with IE...

Characters code problem ? Don't know...

Login error. I installed WP myself and it's been working fine otherwise. Can't connect with the plug-in.

I didn't install WP yet... still editing the blog trough wordpress.

I started a thread on the Wordpress Forum to see if anyone there has any suggestions.

It's actually a configuration problem, I stumbled onto it a couple of minutes ago after installing Performancing. You cannot (at least for some reason on some occasions) use the Account Wizard to automatically create a WordPress account. Use "Custom Blog" insteat and use the WordPress protocol. Works in an instant.

I wish it were thus. I'm afraid that's one of the first things I tried, with no success.

I guess Performancing just doesn't work consistently with Wordpress. It would appear a lot of people have this problem. Maybe there will be a new build later that does include Wordpress.

You cannot create an account at WP.com via PFF, but i've never had a problem posting ot an existing blog on WP...

I can understand I've been there when you've got something with some bugs and you don't have an answer. I'm sure these guys are just busy working on some kind of response.

Then again I use Wordpress but maybe they are more inclined to support Blogger or other services. Since it's been nearly a month since this thread was created I guess we just have to wait a while for Perfomancing to help us bloggers succeed.

Hey guys.
Actually, Wordpress is my personal top priority as it is what I use exclusively.
I can't seem to be able to reproduce this issue with any of my blogs. I've setup multiple versions of wordpress on my server and they all work without a hitch.

Could you specify whether your issue is with a Wordpress.com blog or a custom blog, and the exact version of the wp install (if it's custom)?

That would help me, I am very sorry you guys are having issues :(

Cheers
-Jed

I'm glad your looking into it. I would love to try the Firefox extension out!
I'm using Version 2.0.2 with a compatable Wordpress 2.0 blog theme.

I use Wordpess 2.0, installed via Fantastico auto-installer and upgraded manually by me.

I was having the login error after installing PFF today. I tried refreshing the xmlrpc.php file with no luck.

I renamed the xmlrpc.php file to "test.php" as suggested above, and was able to finish adding my blog with no problems.

I would recommend trying that if you are having issues.

deletedsoul,

Good to know, for some odd reason alot of webhosts disable xmlrpc's based on the name of the script.

krts, have you tried doing that?

If I change xmlrpc.php to test.php will that still allow the Wordpress dashboard to read that file?

Rather than renaming it you could copy it

So Wordpress would read both files then? Maybe I'm not understanding what the xmlrpc.php file does?

krts,

Wordpress itself never uses that file. A better way to think of it is that file uses wordpress and communicates it. Your wordpress install will never try to use the file byitself, hence why it doesn't matter what it's name is.

Unless you have some plugin on your server that uses it of course. If you are woried about that, do what Chris said and just copy it to a new name so that you have both files. But then again, if it doesn't work with the normal name, no reason to keep it around I would think.

Cheers

Discovered Performancing today, and installed WP (manually two days ago). Having the same problem as Schamess.

I installed WP and it works perfectly (hm, "WP w p" .. :] ). Anyways, Performancing just won't log into my blog. I just get the message of incorrect UN/PW.
Tried to rename the xmlrpc.php to no avail.

As I installed WP just days ago I'm using the latest stable version, which is 2.0.3.
Yes I've installed some plugins, but none that would affect logging into the WP admin tool.
I [am trying to] use Performancing 1.2 in FireFox 1.5.0.4
My WP-installation is not at wordpress.com

Thanks for caring about us lost souls, Jed.

This is weird,

There has to be something on common with all your installs, but we havn't figure it out yet ;)

JSON, when you rebamed the xmlrpc file I assume you also pointed PFF to that new URL in the custom dialog? If you rename it, the auto-detect feature will no longer work.

Later this week I'll re-install WP fresh from 2.0.3 and see if I can reproduce this. (I think I'm still on the first 2.0 build.

Yup, yup.

I did point PFF to test.php after renaming it from xmlrpc.php

I have characters in my password that are non-alphanumerics, thought that might be the reason. Tried a change of password, but that didn't help.

I tested to put back 'www' in my URL (in PFF custom dialog). Nopes, didn't help either.

Just to let you know what I've tried.

Looks like it's a race of trials and errors ahead of us ;)

Json,

Hmm, I just manually installed the latest Wordpress (2.0.3) and it worked perfectly fine with Performancing (see: jed.logicalnonsense.net/wp2latest/ )

Not sure what to tell you. Another option is to create a new user in Wordpress and try using that name and password.

Also, what do you get when you go directly to the xmlrpc.php file?
i.e. jed.logicalnonsense.net/wp2latest/xmlrpc.php
gives me the following:
XML-RPC server accepts POST requests only.

A number of people have been complaining about this problem for months now, myself included. I'm wondering if it has something to do with settings our web servers, but I have no idea what it would be.

Experts? Any thoughts on what I could ask my host?

Jed,

I get the same ouput as you do, and everyone else,

XML-RPC server accepts POST requests only.

Tried to create a new admin account and connect to my blog through Performancing using it, but it didn't help either.

JSON, could you PM me.
One thing we could do if you are interested is set up a temp username I could use and I'll debug and find out the exact error your wordpress install is sending pff.

That would rule out if it's a pff or wordpress install issue.

Hey, guys, I think I figured it out:)

I was having the same login problem as you guys, so I simply tested putting in a boolean at the end with advanced configuration, and it logged in instantly.

Below the API URL, where the default selection is "blog/xmlrpc.php," click on the "Advanced Configuration" button. Then, click the boolean checkbox, and under boolean, put a question mark (as in "?").

This logged me right in. I hope it works for you guys.

Oh, and by the way, if this works, could someone who'se registered also post it on the WordPress boards? http://wordpress.org/support/topic/78048#post-403900

Wow, could you guys confirm if that fixes it for you?
If so, for this next release (which will be very very soon) i will make the switch to have boolean be on by default for Wordpress blogs.

Let me know, thanks.

@jenius
The "?" are you placing it in the 'API KEY' textbox? That shouldn't make a difference as WP I believe ignores the api key.

I just tried it again, the fastest way seems to be:

1. Click the "Add" blog button.
2. Enter your blog's URL (in my case, http://mywebsite.com/blog/), and press Next. (Do not click "Manually Configure").
3. Under blog system type, select WordPress
4. Under API URL, enter "http://mywebsite.com/blog/xmlrpc.php?" This is nearly the same as the default value, except with the ? added to the end. Click Next.
5. Enter User Name and Password.

Note: I'm using an older version of WordPress that I installed a few months back, version 1.5. I haven't attempted it with a newer version.

I just ran the account wizard using using default settings. It logged me right in, which may mean that I didn't actually solve the problem:(

Now I'm not sure why I wasn't able to log in in the first place, or why I'm able to now, but for some reason it's letting me using the standard default settings.

After being bitten (again) by the infamous Blogger.com error #3 (and an error #1!), I decided to give wordpress a try. I'll have to figure out if I can migrate my old blogs later! :(

I created a new blog at wordpress.com this morning, but was unable to add it as an account via performancing. I got the same user/password error as described above. I found a solution that worked for me, by following the steps I saw documented (somewhere) for using multiple wordpress blogs:

- Add a blog, choose to manually configure
- Select a Custom blog service
- Choose wordpress.com, and enter a URL as follows:
http://[blogname].wordpress.com/xmlrpc.php
(I didn't need the advanced settings)
- Enter name and password

And that was it. This was the only way I could successfully connect to my wordpress.com account. I'm using the latest versions of Firefox and Performancing.

One comment about my account -- my blogname is not the default one that would have been created, which matched my user id. So maybe this caused the formatting of the URL string to have different requirements.

--Jason

I was having the same problem. When I went in to "Custom Blog" at the bottom of the service list. It gave me the next screen where I selected the Wordpress in the top drop down and the bottom drop down was some generic name. I just entered in my blog name.wordpress.com/xmlrpc.php and it worked fine.

Question, is your username different from the name in name.wordpress.com?

The 1.3 release should fix this, do I have any volunteers who would like to test it out for me?

Specifically this issue with wordpress.com

Thanks
-Jed

Hi guys,

I spent the last two or three hours fighting with this same problem. I host my own WordPress blog on my server and it kept giving me a login error for the username and password. The WordPress version is 2.0.3 and was installed through Fantastico on my cPanel. I'm running FireFox 1.5.0.5.

Here's how I got it to work:

1. Find the xmlrpc.php file in your blog’s root directory, download it, rename it, and copy it back to the same directory with the new name (I used apiurl.php for the new one). Then go to Performancing and click the Add button.
2. Click Manually Configure
3. Add Custom Blog
4. Select WordPress
5. For API url, use http://www.yourdomain.com/apiurl.php
6. Enter username & password
7. That’s it!

Make sure you have the www. in step 5. I couldn't get it to find the original xmlrpc file, but it worked fine with the renamed one and the www. Good luck!

Rachel

Wow, looks like more and more Hosting companies are blocking the xmlrpc.php file.
Odd.

Could you guys post who your host is?
It would be great to start a list of hosts who require this work around so future pff users can look up the details and find the solution.

It could also be the install software (aka Fantastico).

Could be, although I've installed WP via fantastico on my Dreamhost server and it works fine.

Testing with a few accounts that some of you set up for me (thank you), it seems your xmlrpc.php and my-xmlrpc.cgi (for wp and mt) give back the following error:

So it does indeed seem like your server is blocking something.
Either they are blocking the file or blocking any 'POST' requests to your server.

I would try renaming the file and see if that works.
Also complain to your Host that you need this functionality.

I also have tried all the fixes above to no avail. My Word Press is on Blue Host which install WP via Fantastico. So it is not an issue with the installation. Also Blue Host automatically disables the xmlrpc file for security reasons (I also did try the renaming tricks, etc.). Still nothing. Also tried custom vs auto installs. Ditto.

One thing that is NOT very clear in the installation instructions is WHICH password Performancing wants. My installation has a user name and password to enter the site which takes me to the site's control panel. Word Press also has a password for the Admin panel (which in my original installation was different--also for security reasons), but just to see if that was the problem I made them both the same.

This leads to three extremely important documentation questions that need to be answered for ANYONE installing Performancing:

1) do we use the custom or auto installation?

2) If we use the custom what settings need to be in there?

3) Can Preformancing handle systems with multiple passwords? Fed up with Perfomancing I tried ECTO, which is recommended on the WP support blog. I noticed right away the ECTO install has settings for TWO passwords--one for the site and another for WP Admin. I believe this may be the fix you need to make in Perfomancing.

4) The custom setting asks for the xmlrpc file, but if it is dsiabled how does that help? What should be in that box? As a bit of a newbie I am not sure what you mean by API? I had always thought it referred to load file of the program you were trying to access. So if xmlrpc is not that file what is?

5) My sense is also that Performancing is set up for certain hosts (the ones on the list) and if you have another host it is pot luck. I know you have to write the code to work with the most used hosts, but why should the code by different for blogger than for Blue Host?

By the way I like the product--enough that your logo is on my blog, but not sure how long I can keep doing that if it doesn't work with WP.

It took awhile plus some help from the help desk at Blue Host, but here are the answers to my own questions:

1) You can try the auto, but my advice is to ALWAYS use the custom.

2) Unless you are using one of the hosts provided enter "custom host." Select Word Press as your system

3) Multiple passwords are not needed--see below.

4) I had tried renaming the xmlrpc file "test" but for some reason that did not work. A post above suggesting naming it "Apiurl.php" worked. DON"T FORGET TO ADD THE EXTENSION. I know this sounds simple, but after a long day of struggling, you sometimes do dumb things. Clearly my host blocking the xmlrpc file was the root of the problem and may be the root of others' problems. That file needs to be renamed so Performancing can work. My sense is with a different name there should be no security issues. If you are concerned pick a crazy name no hacker will ever work out.

5) When you enter the path to "Apiurl.php" leave out the "blog" part of the path. Perhaps the easiest way to enter the right path is to click on the "Apiurl.php" file and copy down its path then paste it into the box.

6) PASSWORDS: the name and password you need will be in your wp-config.php file. This may be why many folks are struggling since probably servers like mine require a different password to enter the server. I also have lock down passwords protecting my wp-admin files and several other files. I had to do this after an attack on my blog made a mess of it. Trackback came from Netherlands. The point is you may have a lot of passwords floating around. Remember--the password you want for Performancing is the one you put in when you set up wp changing the sample wp-config file tp wp-config.php.

One other thing, I had a custom header in my blog that bypassed the blog name, thus I left it out in the options panel. BAD idea since Performancing gets the blog name from this file. Instead I edited the header to leave out blogname.

Hope this helps some one.

In response to nospam2222

4) Yeah, you always need to keep the extension with the filename. Sorry if those instructions to rename weren't quite clear.

5) The URL you're using is the http://pathtoyourblog/mayhavesubfolders/apiurl.php right?

6) The password and username in wp-config.php is the database username/password. That shouldn't be the username/password used in PFF. Hmm. I suppose if your that was the same as your login to WordPress, then that's ok...

Funny thing, I use bluehost and haven't had any of these issues. Perhaps this is something that has changed for new customers ...

Tough luck for me so far. I've been scouring around for a solution, but nothing seems to work for my Wordpress. :/

1. I've tried a few blogging clients, with a correct username and password (both my main blogging identity and admin account) I receive a 403 Forbidden error.
2. Renaming the files to abc.php, apiurl.php and so on doesn't work.
3. Ticking the binary option in the Performancing wizard doesn't work.

According to Ethereal I appear to be getting a:

Suggestions, anyone?

Zanglang,

When you renamed the file, did you then point the API url to the new name?
Since you changed the name, the auto-detect won't work.

Jed,

Yes, I've tested configuring it manually. Unfortunately it doesn't seem to work.

Just curious, but is there some sort of public security thing going on recently that many of these hosts here appear to be blocking XML-RPC?

No idea.
I think the issue is alot of hackers try and exploit old installations via xmlrpc exploits or brute force password checking. I assume they use standard urls like yourdomain.com/xmlrpc.php and yourdomain.com/blog/xmlrpc.php.

So purhaps blocking access keeps the load down off the server.

Hi. I have used PFF just fine on a couple WP installs, but ran into trouble setting up accounts for others.

Tried the "rename xmlrpc.php and use custom account" solution and that worked. Okay, good. But setting up the next one as a custom account worked without renaming xmlrpc. So, I deleted the former account and the renamed xmlrpc, then set it up as a Custom account like the latter. Worked great.

So, my experience is this: always just manually configure as a custom account and use xmlrpc.php.

This was on Dreamhost, if that matters.

Dreamhost doesn't block the xmlrpc.php file, while some other web hosts unfortunately do. So sometimes people will have to rename xmlrpc.php to get PFF to work.

I had the same problems while posting by performancing / firefox / to wordpress / in dreamhost.
I did exactly 'after being bitten again - riftweaver'told.
It just work :]
Thanks.

ibisgroupltda:
Is your username different from the name in name.wordpress.com?

Trying to figure out why it doesn't work right so I can reproduce this issue myself (any tips when signing up on wordpress.com to cause this?)

Thanks.

I'll try to explain myself since I'm not english spoken...
When i attempt to set a new blog in Performancing.... etc. so:

"Add a blog, choose to manually configure
- Select a Custom blog service
- Choose wordpress.com, and enter a URL as follows:
http://[blogname].wordpress.com/xmlrpc.php
(I didn't need the advanced settings)
- Enter name and password"
0. Open wizzard and select Manually Configure
1.In that first option combo, use the last option, custom blog. [and continue]
2.Then select wordpress in the upper field. And write your adress and right path to that xmlrpc.php file. [and continue]
3. Type your username and password (I am using the same to log in at my url + wp-admin login)

Hope that is what you are asking about, by the way just now i´ve uploaded a post using Performancing

Today I wanted to install Performancing with Firefox and Wordpress and it did not work, I've tried all the things listed above with no success, WordPress Version is 2.0.2 and Firefox is 2.0b2
The host I'm using is Simplehost.

P.S. Sorry for my english, it's not my native language.

Hey, Guys.

I have two Wordpress blogs. One is hosted by Bluehost and the other is hosted by iPower.

On some of my machines (I rotate between three) I can use Performancing, and on some of them I can't.

The problem is related to Performancing itself, and has nothing to do with Wordpress or your host.

I do not know the cause of the problem, but I am quite confident that it is something to do with how Performancing is configured on your LOCAL machine. Otherwise I would not be able to connect with Performancing to both Wordpress blogs on one machine, connect with neither on a second machine, and connect to one but not the other on the third.

Sorry, Jed. The problem is somewhere in Performancing itself.

The manual configuration of a "Custom" blog works.

@leb86305: I agree, sounds like maybe one one machine it got setup right and not on the others.

I'm thinking maybe the auto-detect is failing. Can you try and re-add your blogs and see what the difference between the autodetected options and what you are putting in 'custom' are?

I installed WP 2.03 via fantastico, and had this problem I changed the name to test.php and it seemed to work fine. I'm going to talk to my host about it when he gets on msn. my host is www.hargeo.com I will post again if he has the xmlrpc file blocked or something but yeah for me just changing the name seemed to work fine.

I was having the exact same login problem. I could not get Performancing or ecto to work with a newly created Wordpress blog. I followed the "rename xmlrpc file" method, pointed Performancing to that file and it worked perfectly. Went back and changed ecto to point to the renamed file and ecto finally connected too!

Thanks to all for posting the info here.

Sheila

I did the rename trick and here's the message I get back

"XML Response: XML-RPC server accepts POST requests only"

I have opened a new thread on this forum, regarding all this topic, without even realizing, that there was already a thread, but i got a little posibility, to help the developer finding the error, so it would be cool, if youse guys could pop in shortly and read through it, and after editing a little bit of code in your WP a) approve or b) deny my findings, at least i guess it could help the dev to narrow down the error on that subject

cheers and nighty night

Mitos

Dear all,

I have my Wordpress 2.0.4 installed on Fedora Core 6. I got the same login problem as all of you here when I used Performancing v1.3.5 to login to my blog. After a few unsuccessful logins, I checked the /var/log/httpd/error_log on my computer and found a few entries like the following:

[Sat Dec 30 12:54:41 2006] [error] [client xxx.xxx.xxx.xxx] mod_security: Access denied with code 406. Pattern match "!(^$|^application/x-www-form-urlencoded|^multipart/form-data)" at HEADER("Content-Type") [severity "EMERGENCY"] [hostname "myhostname.com"] [uri "/wordpress/xmlrpc.php"]

I think that is relevant. Any ideas?

I have tried everything that has been suggested, and it still doesn't work for me. I've deleted the file, and just kept the renamed file, I've kept both files. I still get the login errors, and I know my u/n & p/w are correct as I can login and out of my wordpress site. I've put in a ticket at my host to see if it is something on their end. My host is The Prime Host.

**EDIT**

Just got a response back from my host. They block it due to the possibility of spam &/or are insecure and could cause a breach. Nothing more they can do.

Hi,

I've tried all the things in this post, but no one worked for me.

What DID work was adding the following packages to my web server:
xml.so
xmlrpc.so

My BSD now report the following:
php4-xml-4.4.5 = up-to-date with port
php4-xmlrpc-4.4.5 = up-to-date with port

apachectl stop
apachectl start

and it works :)

General conclusion for most people should be: Apache is missing the necessary xml/rpc packages. Ask your webhost or add if yourself if you have the privilege.

I'm not exactly sure why WP isn't accepting the responses. I loaded LiveHTTPHeaders and sent the request. The first response was a 302 response which usually means redirect, but it didn't specify a location. When I replayed the response (which I though would do the exact same thing as initially), I got a 413 response (Request Entity Too Large). I have other things to do now, but maybe this weekend I'll have time to go more into the responses and WP code to try to help this. I am using the latest and greatest stable release 2.1.1 on Dreamhost.

My host sorted it out! I tried the suggestions and fixes suggested here (at least the ones that didn't need me to mess with the guts of the install!) all to no avail. So I emailed my host, Acenet (brilliant folk, and unbelievably helpful and fast, no exaggeration at all!). Five minutes later I got the reply from them and it's fixed! They said they'd disabled mod_security specific for my account and that should fix it. Sure enough when I tried again Scribefire created the account for my Wordpress blog in the standard manner with no problem at all!

Unable to login to wordpress on a cpanel installation with scribefire

*** THIS IS THE FIX ***

Create a file called .htaccess within the root directory for your installation.
Place this line in that file:

# disable mod_security:
SecFilterEngine off

This will disable for that entire directory.