Checking for friends fails with a 500 error

[Changaco]

I've successfully logged in with Twitter and [email protected], but on the /friends page I get an error message:

We're sorry, but something went wrong.

If you are the application owner check the logs for more information.

[druxstr]

Same story here. Tried different from browsers (FF, Chr), OS (Win, Debian), and networks.

Tried to revoke and regrant access. Never ever got this app to work.

I'm using the instance on https://mamot.fr

[edsu]

I'm seeing this too, although it worked for me a few weeks ago...

[ghost]

Same here, using mamot.fr

[clement-analogue]

Same but when I try to log in with Mastodon

We're sorry, but something went wrong.

If you are the application owner check the logs for more information.

[flopreynat]

same issue here.

Mastodon bridge gives following error message after logging onto both services and clicking on 'check for friends':

"We're sorry, but something went wrong. If you are the application owner check the logs for more information."

Landing page: https://mastodon-bridge.herokuapp.com/friends

No error in the console.

[clement-analogue]

In my case, but I'm not sure it is related, it was because the variables LOCAL_DOMAIN and WEB_DOMAIN are different. So I used username@WEB_DOMAIN to log in with the bridge and it worked.

[schmittlauch]

I didn't set a WEB_DOMAIN, this configuration is commented out in my .env.production Nevertheless I get exactly this issue.

[nolanlawson]

This happened to me as well; I believe it happens when you log in with the wrong Twitter username and then try to change it to another one later.

[Cassolotl]

That's not what happened to me, so if that's true that's not always the cause, I think?