The original poster, Noah, is having trouble removing associated accounts from their Discourse site. cocococosti confirms that this feature has been available since 2019, and provides a link to the relevant code.
After some troubleshooting, pfaffman suggests that a misconfigured reverse proxy might be causing the issue, but Noah confirms that this is not the case.
With the latest Discourse update, the error disappears, but Noah still can’t access their associated accounts. david asks about the red wastebasket button, which Noah says doesn’t exist on their main account.
david then points out that Associated Accounts can’t be used alongside two-factor authentication (2FA), which Noah has enabled. To remove the associated accounts, Noah would have to disable 2FA. Alternatively, david provides a Rails console command that can be used to destroy the associated accounts, but this requires admin access and knowledge of the console.
Hiya,
so after a bit of looking around I’ve found that there’s no easy way to remove associated accounts.
I’ve linked my Google account via the Associated accounts category under “account” in preferences, before you link anything, this is how it looks:
On my discourse site I have 2 “associated accounts”.
However when I go to my “preferences” tab there is no button to “remove them”.
Am I missing something here, or is there no way to remove associated accounts?
Thanks for any help in advance!
What version of Discourse are you running?
You should be able to remove them, this has been possible for a while: Future Social Authentication Improvements
And here’s the code that controls it: discourse/lib/auth/managed_authenticator.rb at eb70ea44780ad6d31db82baec4845b6eb4b8e804 · discourse/discourse · GitHub
I didn’t even own a discourse website in 2019, I surely am past this update.
From which auth providers?
Is this happening with all of your users? Do you see any error in your browser’s console?
The 429 error is a rate limiting error. It is mostly likely caused by a misconfiguration of a reverse proxy.
You can confirm this is the isssue by checking user IP addresses and seeing that they are all the same (they are all the IP of the reverse proxy).
If I’m understanding you correctly, I checked & I can confirm this doesn’t seem to be the issue.
With the latest discourse update now installed it seems that error has disappeared, however I can still not access my associated accounts.
What happens when you click the red 
button? Any logs in your browser or on the server at /logs?
Doesn’t exist on my accounts view, on my alternate view the red button does work. On my main account I don’t even get the “associate accounts” table.
Do you have two-factor authentication enabled? Associated Accounts can’t be used alongside 2FA.
I do indeed have 2FA enabled, my associated accounts are still inked.
Will I have to disable 2FA to remove them?
Via the user interface, yes you would have to disable 2fa.
If you’re the admin, and comfortable on the rails console, then you could run something like:
User.find_by_username("my-username").user_associated_accounts.destroy_all