The discussion revolves around whitelisting domains to prevent users from being banned due to excessive external links. GrahameGrieve initially inquired about whitelisting a domain to avoid users being flagged as spammers for linking to hl7.org/fhir on the community.fhir.org Discourse site. pfaffman suggested using the “whitelisted link domains” feature, which GrahameGrieve successfully implemented.
tkearsley then asked about whitelisting a domain to bypass IP limits, specifically to allow multiple users from the same domain (@sony.com) to post from the same IP without being blocked. pfaffman suggested modifying the Nginx config or adjusting the Discourse rate limits. pfaffman also provided a line of code from discourse.conf that could be used as a starting point for exempting specific IPs from rate limits.
tkearsley clarified that the issue was related to Discourse’s rate limits, which resulted in users seeing a “Login Error” message (“There is a problem with your account. Please contact the site’s administrator.”).
community.fhir.org is a discourse site for asking questions about Index - FHIR v5.0.0. As such, most questions refer directly to the site. Users are often banned as spammers for excessive external links because of their links to that site, or a couple of others.
Is there a way to whitelist a domain so that users don’t get banned?
see: My questions are being banned - #2 by lloyd - FHIR Community
Have you tried whitelisted link domains: Domains that users may link to even if they don’t have the appropriate trust level to post links
We have now - thanks.
I don’t see this option in my settings. Did something change?
I found it. With the current IP limits, some of our customers will be blocked from posting. Can I use this to whitelist a domain? For example, allow anyone from @sony.com to post from the same IP.
I don’t know of a good solution. For a client that had many of his users all attend the same conference on the same NAT network, we just upped the rate limits. I imagine if you’re clever you could modify the nginx config inside the container to exempt that IP from the rate limits.
I have no idea how to do that, just a good imagination. 
But. . . .here’s this in teh discourse.conf. I guess you’d Google Nginx and figure out how to add a line like that for the other address.
limit_req_zone $binary_remote_addr zone=flood:10m rate=12r/s;
If you do figure it out, please post. They’ll have a conference again one day.
Oh. I’m not sure if you’re referring to limits established by Discourse or nginx. What error are they seeing?
It would be the rate limit set by Discourse.
This is the message they see: Login Error
There is a problem with your account. Please contact the site’s administrator.