We use SSO, and since a few days, some of our members are reporting being unable to access their account with the error: There is a problem with your account. Please contact the site’s administrator I thought this could be due to an issue I previously reported , so I checked if their IP address w…

[afbeelding] mentalstring: they seem to be added automatically when we close someone’s account through the API So that’s the issue you need to resolve. I’d look at How to reverse engineer the Discourse API .

The issue with IPs being added to Screened IPs is a separate one from what I’m trying to report here. We are seeing members not blocked by the Screened IPs that can’t login into their account via SSO, supposedly because IP address is blocked. Are there more places other than Screened IPs that may b…

[afbeelding] mentalstring: we never add any IPs do the Screened IPs — they seem to be added automatically when we close someone’s account through the API (see link above) It sounds like you are calling the “delete as spammer” function, which will automatically blocklist the IP and email addre…

That may be true, but how we are deleting users is being discussed here . Not sure if this is a separate issue, but I noticed that the Matches column on Screened IPs section shows 0 matches in all entries. I looked at the export of that table and it confirms that all IPs have 0 matches. Yet, every d…

I think I found the issue here (in the end the issue was on our side) but there’s some bugs to report, although this is not a stack I’m comfortable with, so hopefully someone can take a better look. First, the cause. Looking at the screened_ip_addresses database table directly, I found it was block…

[afbeelding] mentalstring: Is there any button in the Discourse admin to block an entire /16 block in one go!? Yet again, I gotta tell you that I’m pretty sure you are calling “delete as spammer” from the API. If there are enough spammer deletions from related IP addresses, the IP address ban…

The issue was not the end point used but the parameters as the API expects bools to be the strings ‘true’/‘false’ and I wasn’t aware of it. There’s still some other bugs I bumped into mentioned above that I don’t know if they are to be addressed. Otherwise, this can be closed. Thank you.

Kan niet SSO vanwege geblokkeerde IP-adressen

Ondersteuning SSO

pfaffman (Jay Pfaffman) 4 juni 2021 om 00:39 2

So that’s the issue you need to resolve. I’d look at How to reverse engineer the Discourse API.

Topic		Antwoorden	Weergaven
Does SSO make use of Screened IP Addresses to block registrations? SSO	8	903	29 oktober 2020
SSO and Screened IPs SSO rest-api	8	1669	14 juni 2021
Spammers signing up from "blocked" IP addresses Support	9	1418	27 mei 2015
Can't search blocked IPs Feature	7	1796	10 februari 2015
How to block an IP range? "Screened IPs" not being blocked Support	22	379	5 december 2025

Kan niet SSO vanwege geblokkeerde IP-adressen

Gerelateerde topics