Problem with IP restrictions

We’ve got several users complaining that they’re receiving 503 errors and notices about too many IP addresses. I know this can be caused by mobile devices, and we don’t think there’s anything odd going on here. I will look at the solutions proposed elsewhere, such as whitelisting certain users.

However, my question is around resetting these users restrictions – all of those who have complained so far, when I edit their profile, have the following label next to the Reset IP checkbox:

*Note* this User is NOT currently banned by any of your IP Restrictions.

??? Is it possible the error they’re seeing isn’t connected to IP restrictions after all, but some other problem? Would you expect this label to be 100% accurate, or is it possible they are banned on IP but the label is wrong?

I will reset them anyway, and ask them to try again, but I was expecting to see an indication here that resetting would have some effect – just for the admins peace of mind!

Many thanks.

Maybe the restriction had timed out before you got to the profile and that’s why you didn’t see a warning about it. Are you sure he was still having the trouble the moment you went to reset the restriction? I’d like to confirm this before asking Jason about it.

Well, it’s a little confusing – I don’t think it had timed out, as the user was still having problems, and when a colleague of mine went in to view the user’s record a while later, the warning was there. When this subsequently happened to 2 other users, I also didn’t see the warning in their profiles, but resetting their IP ban fixed it for them.

Perhaps it isn’t being updated instantly, or some other caching effect?

Thanks for the feedback. I’ll forward it to Jason so he can take a look.

Cache could affect this, I guess. Make sure you don’t have database or object caching enabled, they’re known to cause random problems.

A new version of s2Member was released earlier today, and it includes some improvements to the IP restriction. Please try updating s2Member to benefit from this and let us know if you see the problem happening again. Thanks! :)