# Default maximum of only 3 new users allowed from the same IP address

**URL:** https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611
**Category:** Support
**Created:** [2월 15, 2018, 8:57오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611 "2018-02-15T08:57:27Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 15, 2018, 8:57오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/1 "2018-02-15T08:57:28Z")

</div>

![13](https://global.discourse-cdn.com/meta/original/3X/1/f/1f6c2479e990d625de6ff85fee4d619cf3a1a0df.png)  
This setting is way too low by default if you are using Discourse in a large organisation.

One of our clients hit the limit within days of launch, 3 users is way too low.

I completely missed this setting (we have a closed forum, users are moderated after signup, so I completely skipped the “Spam” part of the settings) when setting up. I only found out by chance, when someone reported via our support-desk.

I suggest to up this to something higher (e.g. 25) by default, if spam turns out to be a problem, users will find this setting and can consciously set it lower.

---

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [2월 15, 2018, 9:07오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/2 "2018-02-15T09:07:07Z")

</div>

I don’t see how this can catch many users.

- If Discourse is hosted on the internet, and you have a diverse user base, you’re fine.
- If Discourse is hosted internally, and your users are on your intranet, you’re also fine, as Discourse will still see all users coming from their own IP addresses.
- If Discourse is hosted externally, _and_ a large portion of your users are behind NAT and therefore share an IP address, you could run into this – but only if no user from that IP address is a staff member or has earned trust level 2, which seems very unlikely if your whole user base is basically coming from a single IP address.

How did you run into this, exactly?

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2월 15, 2018, 9:14오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/3 "2018-02-15T09:14:38Z")

</div>

> [@Bas](#):
>
> This setting is way too low by default if you are using Discourse in a large organisation.

This is an incorrect characterisation of the situation. It would be more accurate to say, “if you are using Discourse, hosted on in the Internet, in a large organisation which is all stuck behind a NAT gateway that only has a single IP address, which hasn’t been whitelisted, and isn’t using a proxy capable of setting `X-Forwarded-For` and being trusted, and doesn’t have IPv6, and somehow hasn’t managed to trip any of the auto-whitelisting functionality designed to avoid this particular scenario”. But that’s less catchy.

> [@Bas](#):
>
> if spam turns out to be a problem, users will find this setting and can consciously set it lower.

Conversely, if your NAT turns out to be a problem, users will find this setting and can consciously set it higher. Or deploy IPv6.

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 15, 2018, 9:22오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/4 "2018-02-15T09:22:43Z")

</div>

> [@fefrei](#):
>
> How did you run into this, exactly?

By inviting 4 people from a single company to join my community. They all joined within a few hours, the fourth was denied.

Note: we only started a few weeks ago, currently have some 100 members in total

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 15, 2018, 9:23오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/5 "2018-02-15T09:23:36Z")

</div>

> [@mpalmer](#):
>
> if you are using Discourse, hosted on in the Internet, in a large organisation which is all stuck behind a NAT gateway that only has a single IP address, which hasn’t been whitelisted, and isn’t using a proxy capable of setting X-Forwarded-For and being trusted, and doesn’t have IPv6, and somehow hasn’t managed to trip any of the auto-whitelisting functionality designed to avoid this particular scenario

Or in my case “if you are using Discourse, hosted on the internet, and invite a couple people at a client to join your new community” ← not a very strange usecase, is it?

---

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2월 15, 2018, 9:26오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/6 "2018-02-15T09:26:27Z")

</div>

> [@Bas](#):
>
> Or in my case “if you are using Discourse, hosted on the internet, and invite a couple people at a client to join your new community” ← not a very strange usecase, is it?

Sure, which is why it’s a site setting, and not a hard-coded value buried deep in the code. It’s also quite different from the scenario you described originally.

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 15, 2018, 9:28오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/7 "2018-02-15T09:28:07Z")

</div>

> [@mpalmer](#):
>
> Sure, which is why it’s a site setting, and not a hard-coded value buried deep in the code.

Fine, don’t change it, it’s indeed no longer a problem for me now that I know about it, just thought I’d help with a (in my opinion) useful tweak of the default setting 🙂

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 15, 2018, 11:28오후 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/8 "2018-02-15T23:28:00Z")

</div>

> [@Bas](#):
>
> Fine, don’t change it, it’s indeed no longer a problem for me now that I know about it, just thought I’d help with a (in my opinion) useful tweak of the default setting

It comes at a cost though, cause now you have a single IP able to spam lots of registrations.

It’s a ⚖ between convenience and security.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 15, 2018, 11:30오후 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/9 "2018-02-15T23:30:57Z")

</div>

Did you pay attention to the help text here? I think you are missing something rather critical. I’ve highlighted the relevant part.

 ![image](https://global.discourse-cdn.com/meta/original/3X/d/0/d0d371f759565cd39b857ca72cf614c37d56ca3e.png)

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 16, 2018, 9:16오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/10 "2018-02-16T09:16:04Z")

</div>

> [@codinghorror](#):
>
> Did you pay attention to the help text here? I think you are missing something rather critical. I’ve highlighted the relevant part.

I saw that and I think the intent behind this was quite elegant.

That said, I reported to you that there is a blind spot in the reasoning: if more than three people from a new company (same location, same IP-address, not seen before) sign up in a short time, then the default value prevents them from doing so. This is a bad first impression to your new members.

> [@sam](#):
>
> It’s a ⚖ between convenience and security.

I understand this, I am (trying to) arguing that the tradeoff-point needs tweaking 🙂

---

<div class="post-metadata">

### Author: ![Ivan\_Rapekas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ivan_rapekas/32/248924_2.png) [@Ivan\_Rapekas](https://meta.discourse.org/u/Ivan_Rapekas)
#### Post date: [2월 16, 2018, 9:53오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/11 "2018-02-16T09:53:18Z")

</div>

As an admin of my forum, I’ve never recieved any notifications about exceeding any limits on default settings for versions 1.8.x-1.9.x. And I’ve never seen any mentions in admin panel. May it indicate that all 1500 users were registered smoothly and nobody was banned?

I have some reasonable questions on it:

1. Do users receive a notification in case of exceeding the limit for their IP address?
2. Do admins receive a notification in case of exceeding the limit by some users attempts to register?
3. Is anywhere logged blocked IPs due to exceeding the limit?
4. In case of incorrect configured external proxy Discourse may get always 127.0.0.1 as an IP for all users. My forum had been working with bad configured nginx for months until I fixed it.
5. In some cases of SSO, there is no registration IP address passed by SSO-host to Discourse. Is it possible a hole for spammers?

 ![image](https://global.discourse-cdn.com/meta/original/3X/f/d/fd1845ed043a31b58f0efce3b0bee1db66552d8b.png)

---

<div class="post-metadata">

### Author: ![Bas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bas/32/294929_2.png) [@Bas](https://meta.discourse.org/u/Bas)
#### Post date: [2월 16, 2018, 10:26오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/12 "2018-02-16T10:26:12Z")

</div>

> [@Ivan\_Rapekas](#):
>
> 1. Do users receive a notification in case of exceeding the limit for their IP address?
> 2. Do admins receive a notification in case of exceeding the limit by some users attempts to register?
> 3. Is anywhere logged blocked IPs due to exceeding the limit?
> 4. In case of incorrect configured external proxy Discourse may get always 127.0.0.1 as an IP for all users. My forum had been working with bad configured nginx for months until I fixed it.
> 5. In some cases of SSO, there is no registration IP address passed by SSO-host to Discourse. Is it possible a hole for spammers?

1. Yes  

2. No ☹

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 16, 2018, 11:54오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/13 "2018-02-16T11:54:50Z")

</div>

> [@Ivan\_Rapekas](#):
>
> In some cases of SSO, there is no registration IP address passed by SSO-host to Discourse. Is it possible a hole for spammers?

In SSO 100% of the responsibility for vetting users is with the SSO parent, not us. That’s how SSO works.

> [@Ivan\_Rapekas](#):
>
> In case of incorrect configured external proxy Discourse may get always 127.0.0.1 as an IP for all users. My forum had been working with bad configured nginx for months until I fixed it.

Many, _many_ things will be broken if this is the case..

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [2월 17, 2018, 1:00오전 UTC](https://meta.discourse.org/t/default-maximum-of-only-3-new-users-allowed-from-the-same-ip-address/80611/14 "2018-02-17T01:00:19Z")

</div>

This topic was automatically closed after 34 hours. New replies are no longer allowed.
