latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Sitewide-403 lockout

Home Forums Community Forum Sitewide-403 lockout

This topic contains 4 replies, has 4 voices. Last updated by  Cristián Lávaque 4 years, 2 months ago.

Topic Author Topic
Posted: Friday Oct 19th, 2012 at 3:49 pm #29062

Yesterday at about 5 PM we started having a 403 error at our site which locks out everyone. We were not doing anything unusual at the time to cause this. So far we have not found a solution. Looking in the forum here we found that Mod Security sometimes can cause 403 errors with s2Member, but our server does not have Mod Security installed, so that’s not the problem. Where do we go from here?

List Of Topic Replies

Viewing 4 replies - 1 through 4 (of 4 total)
Author Replies
Author Replies
Posted: Saturday Oct 20th, 2012 at 12:54 am #29105
Raam Dev
Username: Raam
Staff Member

Have you tried disabling s2Member to confirm that it’s actually the s2Member plugin causing the problem (make sure Deactivation Safeguards are enabled before disabling: Dashboard -› s2Member® -› General Options -› Deactivation Safeguards)? I’ve never heard of s2Member spontaneously causing a site-wide 403 lockout, so I suspect there might be something wrong on your server and if that’s the case, you should contact your web host.

Posted: Saturday Oct 20th, 2012 at 9:25 am #29140
Eduan
Username: Eduan
Moderator

Be sure to check out this article, it might help: Knowledge Base » Mod Security, Random 503/403 Errors

– Eduan

Posted: Sunday Oct 21st, 2012 at 11:37 am #29212

We have a vps with Servant, a very good company. They confirmed that we do not have Mod Security installed on our server, so we know our problem is not related to that. Fortunately, we had already enabled Deactivation Safeguards as recommended, because even admins could not access the site. Using FTP, we disabled all s2Member plugins, and that restored access to us. We then activated s2M framework and that has not caused a problem so far. Of course, we want to activate Pro features, but have waited to see what advice we get from you first, in case there is anything else we must do before reactivating Pro.

Posted: Monday Oct 22nd, 2012 at 9:29 am #29255

I’m glad you restored access to your site.

Could you please contact your hosting company asking them about their logs, to find out if they have more info on the 403s? Like what URLs were triggering them.

Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

This topic is closed to new replies. Topics with no replies for 2 weeks are closed automatically.

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.