Some of my members are facing a constant issue. Snapshot below. Could anyone please help me understand why this is happening and which setting I should change to avoid this?
AI-generated summary
Users are experiencing a login issue where they’re met with a ‘Please wait before trying to login again’ message. samp_one reports the issue affects members using username/password but not Google login, and temporarily disabled non-Google logins. watchdogs_1499 confirms the issue persists even after updating Discourse. Ayelen_Rives shares a similar case where their company IP was accidentally blocked after a user deletion, preventing all office logins until another admin unblocked it from home. Lilly suggests checking max_logins_per_ip_per_minute and allow-listing company IPs in admin / logs / screened_ip_addresses, which aligns with the root cause. Jagster warns against IP bans, citing past incidents where large customer groups were mistakenly blocked. The issue stems from IP-level restrictions, often triggered by admin actions or rate limits, and can be resolved by reviewing screened IPs or adjusting rate-limiting settings. No code-level fix is needed — it’s a configuration or administrative oversight.
Facing this issue too, tried updating Discourse to the latest version, but that does not seem to be working. Please share a fix if you have found one.
Google login is working fine for the same people who face an issue logging in with username password. So, I have enabled google login alone on my website for now
Are there any errors in /logs you could share?
Hi! I’m having the same issue today.
Inicially, the company’s IP was blocked, so no one in the office could log in. After approving the IP again, we’re all getting this message.
Any ideas of what causes this and how to solve it?
Thanks in advance!
Hi @Ayelen_Rives 
Maybe try allow-listing your company IP address in the screened email list at admin / logs / screened_ip_adderesses. It sounds like you are all using the company IP address and max_logins_per_ip_per_minute is being exceeded.
Thanks for your help and sorry for the delayed answer!
It was solved:
An admin deleted a user and blocked the IP… It was the company’s IP 
So everyone in the office was blocked. Another admin logged in from home and unblocked it. Fortunately it was solved quickly!
And that is very strong point against banning IPs. Last time I banned very big part of customers of Finland’s the biggest mobile ISP at capital area.