ironlion37

Thanks Steven. I’ve isolated the issue to Paid Memberships Pro and will follow up with them.

Just a follow up here: this was an error my part. This thread can be deleted.

Also, FYI, this is listed as an active integration available on the Buddyboss site: https://www.buddyboss.com/integrations/buddypress-registration-options/

Ok, thanks for the clarity. That was really confusing me. Knowing about the security/all traffic toggle is a big help!

Thank you for the reply. I think I may have figured out what is happening. I have a system on my site where newly registered users are automatically logged in when they click on an activation link that is emailed to them at registration.

That must be why there is no record of them under Wordfence’s “security only” live traffic monitoring. That auto-login must not be picked up by Wordfence. Does that sound right?

Thanks!

Thank you!

Hi Andrea, circling back around to implement this. I don’t have any file in my installation called: bp-custom.php…

Yes, it is checked.

To be clear, I have solved the issue. People are now able to register on my site without getting a 403. I just don’t know how I solved the problem. I removed all plugin settings and started adding them in one at a time and testing each one. I got the “Strength” back up to 350 and figured that’s pretty good and stopped there. I guess it’s a moot point now. But all Firewall settings are on and there’s no 403. So I’m wondering if there’s any other setting that can generate that during a registration process? How about if “Enable manual approval of new registrations” is turned on? That seems like it might throw a 403 during a registration process. I did have that on and have left it off….

Thanks for the reply. I ended up disabling all rules and adding them back in one at a time. I added all the firewall rules (on each tab) and they did not cause the problem.

I have both of these checked:
Completely Block Access To XMLRPC
Disable Pingback Functionality From XMLRPC

I seem to have fixed the problem, but I’m still wondering what was causing the 403 forbidden. Is there any other setting in the plugin that can cause that error? (And it seems like the plugin has its own 403 graphic that it uses.)

Thanks again!

Following up on this, apparently it’s not the Rename Login Page setting that is causing this. Which feature in AIOWPS throws the 403 three forbidden graphic?

I’m running into this problem too, just uploading a tiny logo png (87k).

Oof. This is disconcerting. Thinking about using this plugin till I read this.

Thanks Bianca. I don’t think that’s quite the solution I’m looking for though.

The behavior I’m looking for is that when an image is uploaded via the media uploader, only one file is saved in /content/uploads and that file is 350px or less.

Thank you Jarret! Solved ??

They are uploading to posts via the “featured image” widget on the posts page. So, using the WordPress media uploader.