I’m not sure if this is a bug or an issue with my configuration. When I try to make a new user using Discourse ID signup, the Discourse ID verification part works fine, but on going back to my instance at keppari.discourse.diy, the signup fails silently even with a Discourse ID verified email signed in in the browser. The signup button is available but does nothing when clicked and there’s no warning on the page. I was previously able to create other users with Discourse ID. In my login and authentication settings, my only overridden setting is disabling 2FA and allowing Discourse ID. I’m self host and I don’t have SMTP configured. Between creating the previous users and this attempt, I briefly disabled local logins because I thought since I didn’t have SMTP configured that it made the login form confusing, but now I’ve got local login re enabled. I’m not sure if this is related, but in the console for all anonymous user page views, there’s a bunch of 404 errors for my plugins, but also for /assets/vendor.map and assets/start-discourse.map. A logged in user does not have these console errors. I don’t see anything recent in my /logs. I’d appreciate any guidance on other settings to change if this is a configuration error on my part! I’m self hosted, 2026.3.0-latest

[image] asc: The only non-core plugins I have installed are Fingerprint (now disabled), Staff Alias, and Always-Anonymous Categories Plugin . The other enabled plugins I have are all from core. One gotcha to keep in mind is that some plugins still run some code even when they are disabled. I don’t know if this is the case for these three, but if you’re trying to determine if a given plugin is the culprit, your best bet is to remove it completely from the app.yml file and test. You could do the same with the theme components, but as you note, they don’t seem to interact with logins.

Were you alerted of my attempt at sighn up? Also will you want me to sighn up non-id instead to see if that works?

No, I don’t see a new user and got no alerts of any kind, thank you for trying.

I don’t think non-ID will work since I don’t have SMTP configured.

I did a rebuild in case that helped anything and I’m still getting the can't alloc thread errors and signup problems.

[image] asc: I’m on a 1GB memory Digital Ocean droplet while I set things up, in case that’s relevant. I know it’s not the recommended size If it’s possible for you, can you try a new test Discourse install in a new droplet of the same size? If you run into the same issue, you’ll know that it’s the size that is the problem. (I can do the same and test this out on a 1GB droplet, but will only be able to test in a day or two.)

On a brand new install on a new 1GB droplet, I have no errors and I’m able to log in with Discourse ID just fine. I didn’t start having issues with my main install until I disabled and then reenabled local login, if that makes any difference. I was able to reproduce by unchecking “enable local logins”, which made it so that a new user can’t sign up and gave the same errors in the browser console. I got these errors in logs on the fresh install: MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-City.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-City.mmdb 8:00 pm MaxMindDB (/var/www/discourse/vendor/data/GeoLite2-ASN.mmdb) could not be found: No such file or directory @ rb_sysopen - /var/www/discourse/vendor/data/GeoLite2-ASN.mmdb 8:00 pm (discourse_id) Authentication failure! access_denied: OmniAuth::Strategies::OAuth2::CallbackError, access_denied | The resource owner or authorization server denied the request. 8:08 pm But checking “enable local logins” allowed new users to sign up on the fresh install again and stopped the console errors for anonymous users. I haven’t been able to reproduce the can't alloc thread log error.

I regenerated credentials but I still get the 404 errors in browser console and can’t sign up a new users. I don’t see any new errors in /logs since regenerating but I can post them again if that would help.

Oh, I see. I think there is a separate misconfiguration here. Can you share the list of login-related site settings and their values? Not credentials obviously, but I am curious how your site is set up to handle new signups. (If you prefer to send via PM, feel free to do so.)

In Admin > Login & Authentication, the only changes I have from default are: disable “Enforce second factor on external auth” enable Discourse ID I did briefly disable local logins, but I have them reenabled now.

New users can't sign up, 404 errors in console

Product Support

pmusaraj (Penar Musaraj) March 16, 2026, 5:43pm 15

With ID enabled, can you regenerate credentials from Admin > Login & Authentication > Discourse ID?

Topic		Replies	Views
Error: Users can't make new accounts Bug	12	2248	July 6, 2023
Error While Trying to load, New and Admin accounts Product Support	14	3320	July 20, 2015
Unable to setup discourse in my windows 10 Self-hosting	22	2682	August 23, 2022
Stuck with 500 error after weird bugs and a rebuild Self-hosting	17	2354	January 8, 2024
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	1092	October 22, 2025

New users can't sign up, 404 errors in console

Related topics