I experienced that before, and I solve the problem by logging in with private key not posting key as a password. It should work! :) I guess the error message should be changed to understand what happens for end-users. Cheers!