I changed the URL of my discourse site, and promptly members started complaining that they could not log in. Exactly the problem reported in Changing domain names prevents Discourse ID from working. Looks like the fix is to empty the credentials via the rails console. I thought the Regenerate credentials button would help but selecting that generated an error as well. [Screenshot 2026-07-02 at 6.37.24 AM] Seems to me this is worth investing in addressing, since it’s not unheard of to change the URL of your site. My feeling is that Discourse ID should auto correct itself in some way. Or at least there should be a way to refresh Discourse ID via the admin UI. Failing that, I’d suggest adding a note linking here from Change the domain name or rename your Discourse.

[image] tobiaseigen: My feeling is that Discourse ID should auto correct itself in some way. Or at least there should be a way to refresh Discourse ID via the admin UI. In our hosting, this is handled automatically. In self-hosted sites, it’s running into the issue you described. There is no event or screen in the admin UI where an admin indicates to the app that they are about to change the domain of the app, so we can’t act on it at the right time… A similar issue happens with all the other social login providers, they need new apps to be created. Did you see any issues in the admin dashboard? I would expect problem checks to possibly have fired.

I don’t recall seeing any issues in the admin dashboard, but then I didn’t watch out for it either. Can you add a button next to “Regenerate credentials” to delete the credentials? Or a JIT popup when disabling Discourse ID to ask if you want to delete the credentials? Either of those would have helped me to avoid having to go to the command line. I’m not using any other social login provider.

Will have a look at this shortly. My first instinct is not to add another button, it can be confusing when browsing these pages in normal times (i.e. outside of domain changes). But maybe disabling ID should clear the credentials upstream anyway. No harm in that, potentially, since re-enabling would create new credentials.

[image] pmusaraj: re-enabling would create new credentials. That’s true! Immediately after toggling on/off I went to test it, and it worked.

Can't regenerate Discourse ID credentials after changing domain name

Product Support

tobiaseigen (Tobias Eigen) July 3, 2026, 1:58pm 6

That’s true! Immediately after toggling on/off I went to test it, and it worked.

Topic		Replies	Views
The Discourse ID cannot be used after changing the forum domain Product Support discourse-id	2	356	January 24, 2026
Changing domain names prevents Discourse ID from working Product Support discourse-id	2	453	October 19, 2025
Changed subdomain/domain and can't get Discourse ID to work Product Support discourse-id	2	208	February 8, 2026
Discourse-ID displays it's own logo & name instead of my forum's Product Support bug , discourse-id	25	666	August 24, 2026
无法登录什么原因 Product Support discourse-id	8	409	April 14, 2026

Can't regenerate Discourse ID credentials after changing domain name

Related topics