custom instance not detected as status.net instance

[Daniel Friesen]

I setup a private instance at http://shout.vancouver-anime.com/ (You won't be able to login)

However when I try to log into is using 'shout.vancouver-anime.com' as the server and using the OAuth login it simply says "Sorry, something went wrong.. / Test failed: this is not a statusnet instance"

Looking in my webserver logs Mustard does a single request to http://shout.vancouver-anime.com/api/statusnet/config.json

Which looks perfectly fine to me. Yet Mustard bails out right after seeing that and fails to consider the instance a Status.Net instance.

[Francis Blesso (frandroid2)]

I discovered this when upgrading to a new phone. Using the same version on an old phone, I was able to access my private instance. As a workaround, I downloaded and installed mustard-0.2.1.a.apk, set up my accounts and then upgraded to the current version. I'm now able to access my private instance

[Winfried Lorenzen (knallio)]

I have the same problem with Mustard 0.3.4. I don't have access to the server logs, but the workaround helped me too. Now I am able to access the statusnet instance, but I only see my own posts, not the posts from my friends. I don't know if this is related.

[Jason Haar (jhaar-launchpad)]

I too successfully had mustard running last year off my own statusnet-1.10 server, but stopped using it until this week, when I installed it on a new phone. End result is the same - Apache logs show a successful "200" download of /api/statusnet/config.json, but mustard returns "Test failed: this is not a statusnet instance"