the statusnet desktop client won't work

edited November 2010 in StatusNet Desktop
hi, I used the godaddy share host to set up a statusnet service with the statusnet 0.9.6, and then tried to connect to it via desktop client (newest release), but it kept returning message saying "bad nickname or password", I am 100% sure I got the right name. Anyone got any ideas?

Comments

  • @muakaka is your install the site root or in a subdirectory? Do you have fancy urls enabled?
  • it is in the site root, fancy URL enabled, does it matter
  • @muakaka Sometimes it can't find the api root if it's not set up in the root with fancy urls.
    View the source on any of your pages and look for rsd.xml that file will tell you your api root, try putting that in the server section of the client.
  • I had hit the same problem as well. But found the solution. As usual, most of the advice given here was correct but somewhat incomplete.

    If you run your own apache server, or have access to the config files make sure that:
    1) the .htaccess file is in place and possibly those two lines uncommented:
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
    2) if at first it does not seem to make a difference then this is because the .htaccess file
    may be ignored. I had to add these lines to my apache config file under the virtual
    server definitions:
    AllowOverride All
    Options ExecCGI FollowSymLinks SymLinksIfOwnerMatch
    the allowoveride enables the the reading of the .htaccess file. The second line was
    then needed to to make allowoveride work due to some symbolic links.

    I admit, the error messages are not even close to reveal what needs to be done.

    Hope this helps someone to avoid some headaches.
Sign In or Register to comment.

Howdy, Stranger!

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

Sign In with Google Sign In with OpenID