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 signe…

[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 …

[image] asc: The signup button is available but does nothing when clicked and there’s no warning on the page. So, the user is stuck on the signup screen with a disabled signup button? Can you share a screenshot? Are there any errors in your /logs?

The signup button isn’t even disabled, it’s enabled but does nothing when clicked. The first screenshot below is before trying to click signup, but it looks the same after clicking. [Screenshot_20260309-102453] These are my logs right now; I attempted a signup at 10:25 in these logs. I had though…

Yes, please post the backtrace and env for the can’t alloc thread error, that seems to be causing the havoc on your instance.

Here’s the backtrace for the most recent can't alloc thread error: Message (159137 copies reported) Job exception: can't alloc thread Backtrace /usr/local/lib/ruby/3.4.0/socket.rb:712:in 'Thread.new' /usr/local/lib/ruby/3.4.0/socket.rb:712:in 'block in Socket.tcp_with_fast_fallback' /usr/local/l…

Hey i attempted to veiw this from a regular user POV i go to sighn up with discourse ID and just am given the prompt once the field [image] Is filled out i press the sighn up and the button presses but dose not do what it should

These are the console errors for an anonymous user, on /signup and all other pages: [Error] Failed to load resource: the server responded with a status of 404 () (discourse-lazy-videos.map, line 0) [Error] Failed to load resource: the server responded with a status of 404 () (poll.map, line 0) [Err…

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.

Les nouveaux utilisateurs ne peuvent pas s'inscrire, erreurs 404 dans la console

Soutien

pmusaraj (Penar Musaraj) Mars 9, 2026, 2:45 4

Oui, veuillez publier la trace de la pile et l’environnement pour l’erreur « impossible d’allouer un thread », qui semble être à l’origine du chaos sur votre instance.

Sujet		Réponses	Vues
Error: Users can't make new accounts Bug	12	2052	Juillet 6, 2023
Error While Trying to load, New and Admin accounts Support	14	3170	Juillet 20, 2015
Unable to setup discourse in my windows 10 Self-hosting	22	2394	Août 23, 2022
Stuck with 500 error after weird bugs and a rebuild Self-hosting	17	2147	Janvier 8, 2024
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	715	Octobre 22, 2025

Les nouveaux utilisateurs ne peuvent pas s'inscrire, erreurs 404 dans la console

Sujets connexes