503: Service Temporarily Unavailable

[danisrael]

Have a site with around 500 users that is just reaching 30 days old. Now I'm starting to have users receiving this error:

503: Service Temporarily Unavailable
Too many IP addresses accessing one secure area!
Please contact Support if you require assistance.

Not sure whether the 30 days old is an issue or whether there is Link Sharing taking place.

Can you advise?

[volcano]

I am having the same error for one user. I only have 10 users. This error comes up for this user no matter what IP address or computer is used. So far it is only affecting one user. Anyone know a fix.

[taragentile]

I'm having the same exact problem. 2 users out of 200.

I'm currently running s2member with Buddypress and everything is up to date.

[Nemrod Kedem]

Hi,

I had that same problem and it seems that cron was not running on the hosting server and IP punishments were not cleared. Enabling cron tab on the server removed the problem.
Just consult your WP hosting...

Good luck,
Nemrod Kedem

[frost]

I am getting the same message:

503: Service Temporarily Unavailable
Too many IP addresses accessing one secure area!
Please contact Support if you require assistance.

I even move the ips up to 20 allowed and still get the message.

[danisrael]

Nemrod,

Using dreamhost. How can I test to see if this job is running?

[Jason Caldwell]

Hi all. Thanks for reporting this important issue.

We've just released s2Member v3.2.5 early to address this concern:
http://wordpress.org/extend/plugins/s2member/download/

-- IP Restrictions ( reset ).
Several site owners have reported issues with s2Member's IP Restrictions. A full investigation has been performed. Although no bugs were found, we suspect that recent reports on this topic are related to a combination of:

a.) improvements in recent versions of s2Member,
with respect to IP Restrictions ( adaptive concurrency limits );

b.) lack of support ( on the part of s2Member ) for resetting
IP Restriction Logs after changes in configuration.

In this release of s2Member, we've introduced a new tool for site owners, which allows you to Reset IP Restriction Logs manually, at anytime you like. For further details, please see: `s2Member -> General Options -> IP Restrictions` ( look for the new button titled: `Reset IP Restriction Logs`. ).

As always, please let us know if you have any questions/concerns.

[markelshark]

Jason, I have users who are still getting 503 errors AFTER I reset the logs! Please help. How can I disable this feature, or delete/view IPs in the database?

[danisrael]

markelshark, Any luck viewing the IPs?

[markelshark]

No, I dug around in the DB and couldn't find them anywhere.

[markelshark]

The problem with this feature is that it punishes users who, for example, use coffee shops a lot. I would much rather have a feature that allows only 1 or 2 concurrent logins, rather than a feature that counts IPs

[markelshark]

*bump* Jason, this feature still continues to haunt me and I still am waiting a response from you from September 13th post! My questions/feedback were:

1) How can I view the IP addresses a user has connected from? This way I could determine if it is legitimate usage or credential-sharing.

2) It would be best if I could reset just a single user - that way as I keep having this issue I'm not resetting the IPs for EVERYONE. If I keep doing that what is the point of the feature?

[markelshark]

And a big 3) resetting the logs does not work on my server for some reason. S2 says logs have been reset in an alert window but users still get the 503 error. I am having to tell them to signup for a new account and then transfer their PayPal profile ID over.

Jason, if I could please get some help from you on these issues......

[MikeL]

Is there a way to turn this feature off entirely?

[mercure]

I have been experiencing the same issue. I tried to reset the IP logs, but I get the same error 503 again.

What to do?

[drcoach]

Now having this issue as well. I can log in as admin but can't log in as user even when I have formerly logged out as admin.

[Jason Caldwell]

Thanks for all these reports guys. Much appreciated!
~ Apologies for my delay on this topic.

s2Member v3.2.8 has just been released to address your concerns.
http://www.primothemes.com/post/product ... th-paypal/
As always, your feedback is welcomed.

== Changelog ==

= 3.2.8 =
* Unique IP Restrictions. There is a new option under: `s2Member -> General Options -> IP Restrictions` which allows a site owner to effectively disable IP Restrictions if they'd prefer. On some hosting platforms, the `$_SERVER["REMOTE_ADDR"]` variable ( i.e. a Users IP address ) is incorrectly set to the exact same thing for all visitors; which WILL prevent s2Member's IP Restrictions from working as intended. If you're on a hosting platform that has this bug, you may wish to disable IP Restrictions completely using s2Member v3.2.8+. Otherwise, under most circumstances we recommend that you leave IP Restrictions on.

[humanityhealing]

Hi All,

I am still getting the 503 Error. I have spoken with the individuals, and the individual with the most unique computers our site was accessed from was 3. Most just logged in from their home computer.

This has moved beyond an inconvenience to a credibility issue for our website and will only get worse as we expand.

Clicking the IP Reset button does not work. How do I address this besides deleting the account and re-entering the data and does the new different sign-up date conflict with the Paypal reoccurring payment date???

Regards,
Christopher Buck

[Lange]

I am also still having issues with users getting permanently 503'd. Resetting the logs does not fix the issue, and manually altering the database entries does work either (they simply aren't there after resetting the logs, or I'm looking in the wrong place. What table are they contained in?). The penalty should only be 60 minutes for my site, but any user who trips the IP limit is never allowed to log in again. This is a serious issue and I would appreciate it if it could be quickly addressed.

I am running s2member 3.3.2 + Pro Module 1.3.2.

[Lange]

Update: I have managed to locate the entires in the wp_options table and manually edit them to allow users to log in again, but this obviously is not the best way to go about this and I still need some assistance.

[bmiles]

I was having this problem as well for a few select users (even after reseting the IP restriction logs). Unfortunately the only way I was able to resolve the problem was by changing max allowed to infinite. I think I'll leave it off until things get ironed out.

[Jason Caldwell]

Thanks for reporting this important issue:

I was having this problem as well for a few select users (even after reseting the IP restriction logs). Unfortunately the only way I was able to resolve the problem was by changing max allowed to infinite. I think I'll leave it off until things get ironed out.

This bug was found in s2Member's "Reset IP Restrictions" button,
and corrected in the release of s2Member v3.5+.

In addition, it is now possible to reset IP Restrictions on a per-User basis in your Dashboard. Click [Edit] next to any User account, and you will find a checkbox with details regarding any existing IP Restrictions that exist for the account. If any exist, checking the box and clicking Save will remove the temporary ban for that particular account. This allows you to Reset IP Restrictions, but only for a specific User.

[rodrico101]

I am starting to havesimilar issues with my site....I would like to change the time period from 30 days to 24 hours. (yes..that would be practical for my site).

The default period of "30 days" could be modified through this WordPress® Filter:
ws_plugin__s2member_ip_restrictions__concurrency_time_per_ip

Where do I find this filter?? File, folder etc.

Thanks,
Rod

[Jason Caldwell]

Thanks for the excellent question.

Create this directory and file:
/wp-content/mu-plugins/s2-hacks.php

Inside the file, add the following code:

Code: Select all

<?php
add_filter ("ws_plugin__s2member_ip_restrictions__concurrency_time_per_ip", "s2_concurrency_time_per_ip");
function s2_concurrency_time_per_ip ()
    {
        return "24 hours";
    }
?>

[rodrico101]

Jason,

Thanks for the speedy reply.
I tried adding the folder and file into my wp directory and got a huge line of php errors when trying to log in:

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 693

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 694

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 695

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 897

and these when I added the folder after already being logged in and trying to log out:

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-login.php on line 354

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-login.php on line 366

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 720

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 721

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 722

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 723

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 724

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 725

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 728

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 729

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 730

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 731

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 734

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 735

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 736

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 737

Warning: Cannot modify header information - headers already sent by (output started at /home/rodrico1/public_html/washinflorida11.com/wp-content/mu-plugins/s2-hacks.php:1) in /home/rodrico1/public_html/washinflorida11.com/wp-includes/pluggable.php on line 897

Is this conflicting with another plugin ?? I also noticed that it changed the look of my "General Options" page and I no longer had the drop downs for each option. (ie clickable fields)

I am using WP version 3.1 and just updated S2 to Version 3.5.4 before adding the hack.

Thanks,

Rod