Comments on Client authentication failed

I checked the client secrets (the app has to register as a client for every instance) and found two lines matching, and that's obviously a bug. I've deleted the older one. That didn't help, so I deleted the other one as well. Finally, it worked.

– Alex Schroeder 2018-08-20

Same for two more users. I'm not sure whether the problem is all the client ids I registered before a certain date or not. I guess at the point where I changed the redirection URL I should have deleted all the client ids?

– Alex Schroeder 2018-08-22 21:11 UTC

Then again, I just confirmed that some instances will not work even if the client id is removed:

I'll be adding to this list.

– Alex Schroeder 2018-08-23 08:52 UTC

Today, Eloisa told me she was having the same issue:

Somebody had contacted her with the same issue:

But also:

Two days ago, somebody from was getting a different error: ""Authorisation failed. Did you try to reload the page? This will not work since we're not saving the access token." I have no idea what this is. People deleting cookies?

– Alex Schroeder 2018-09-12 21:29 UTC

Today I heard from who tried to join multiple lists with logging enabled and every single attempt failed with "Authorisation failed." Clearly, this is still not working. The logs show saltycoffee getting redirected, being authorized, coming back with a code, requesting a token, and then being denied.

Checking credentials shows that we have another duplication! is a duplicate. This is unrelated to but still a problem. Perhaps we need file locking?

– Alex Schroeder 2018-09-17 18:01 UTC

Today I got a message from a user on saying that they had received the same message.

– Alex Schroeder 2018-10-14 20:31 UTC

Looking at some logs:

[Mon Oct 15 08:20:50 2018] [debug] wants to authorize the 'follow' action for the Vim list
[Mon Oct 15 08:20:50 2018] [debug] found client credentials for id yes, secret yes
[Mon Oct 15 08:20:50 2018] [debug] has a client: yes
[Mon Oct 15 08:20:50 2018] [debug] is being redirected to
[Mon Oct 15 08:20:50 2018] [debug] 302 Found (0.049717s, 20.114/s)
[Mon Oct 15 08:20:50 2018] [info] GET 302 0.0548s

And that's it. So this user is getting redirected to and isn't coming back.

Checking the credentials file I see an entry for and fosstodon (which is clearly wrong). I'm going to remove both and see what happens.

– Alex Schroeder 2018-10-16 20:47 UTC

I just received the same "Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method." error trying to add the Catholic list. However, the Follow button for individual list members works fine. Then I created the list and added the members manually.

– David Meyer 2018-11-17 04:02 UTC

Yeah, manual following always works because then you're doing the clicking instead of Trunk trying to tell your instance to remote-follow all these people. :(

– Alex Schroeder 2018-11-17 10:52 UTC

Same client authorization failed message from

Django 2019-01-22 13:51 UTC

I'm getting the error from my instance ( while trying to follow the Sysadmins list.

– mhamzahkhan 2019-02-22 11:56 UTC

Problem also exists on

jeroenpraat 2019-02-25 12:18 UTC

I'm starting to feel like perhaps I should simply remove those buttons, as suggested by one of you on Mastodon.

– Alex Schroeder 2019-02-26 19:00 UTC

Yup, unfortunately, happening while trying to authenticate with instance.

decentral1se 2019-03-19 17:38 UTC

Gah, I will have to disable it!

– Alex Schroeder 2019-03-21 20:33 UTC

Same problem occurs when trying to sign in with a account.

– Anonymous 2019-04-28 23:53 UTC

I have disabled it. I don't know how to fix this. :(

– Alex 2019-04-29 16:04 UTC

This wiki uses a variant of Markdown.

To save this page you must answer this question:

Please write "new issue" into the field below.