Thread

This question is an UPDATE to resolved thread.

For some reason the last thread was closed ...

UPDATE: No - adding an IP address to the whitelist module does NOT stop it from being added to the config.php when you ban a member via the discussion forum and also choose all their associated IP addresses.

We need a more robust “whitelist” solution inside the config.php I think that overrides the module.

Any ideas?

Thanks,

Robert

Please feel free to make any feature requests in the appropriate forum.

Why would that be a “feature request” when in the other thread both Sue & Greg say that the blacklist module should do it? Sounds like a failure of the module to work correctly if you ask me.

Hi Robert,

No, these are two separate items - one server-based (the Blacklist module) using the .htaccess file and one EE-based (the member banning process). These are unconnected. As Ingmar says, if you wish to see these features work in a different way then please do submit a feature request. However, it’s an odd situation if you find yourself banning your own IP addresses. Do you have some kind of proxy server setup that is not forwarding remote IPs properly?

Cheers

Greg

Thanks for clarifying how they work Greg - it’s not obvious actually!

Yes it’s not smart to ban your own IPs ... we worked it out since we’re using a custom module to create members inside EE when they are created inside Infusionsoft (under specific conditions) and the http post we were using contained the Infusionsoft IP address that got added to the member record. Once we took that away, then it’s only IP addresses used by the new member themselves that are recorded and we can ban members fearlessly.

Thanks for your help!

Robert

Glad Greg was able to help. Are we good to close this particular thread?

Yes Sue - and thanks for asking!

(I can get cranky if they are closed too early haha - on our site we tend to leave all of them open forever as a useful resource that folks can still extend questions for - but I guess you guys get too much confusion since some things could come up in a search when they are clearly solved in later builds/new features or customer self-solving)

Hi, Robert - sometimes we do close the thread early, which is why I asked. 😊 We try not to, though. Usually we close each post with a bit of chatter that goes like this:

Don’t hesitate to post again as needed.
-or-
Feel free to start a new thread if you have any more questions.

You then can take a closed thread like you did, and that way we have a pointer back to the original post for reference.

Often times someone will try and be helpful by posting a similar question on a very old thread, and we have to split out the question to its own thread. One of the reasons we started closing threads a while back.

But I’ve yattered on long enough. 😊 We appreciate your feedback..

Feel free to start a new thread if you have any more questions.