Hi @yoga8sam, thanks for getting in touch.
If Wordfence was interfering with the request to the page, I would expect a 403 or 503 along with a Wordfence-branded block page. It’s certainly interesting that a 404 is being shown when Wordfence is enabled, so another request may be getting blocked in the background or there’s a plugin conflict of some kind.
After ensuring there’s no Memberpress setting to enable/disable whether the page is publicly live, I would first try having Wordfence and Memberpress as your only enabled plugins. If the page works under these conditions, there’s something else happening, so reenable your other plugins one-by-one until the 404 behavior returns.
If you still see 404s with only Wordfence enabled on top of Memberpress, view your Live Traffic immediately after requesthing this page to see if a block is being picked up there. If so, you should be able to see which rule is causing the block by clicking that line (or “eye” icon) to expand it. Sometimes you are presented with a “ADD PARAM TO FIREWALL ALLOWLIST” button here that could solve any problems going forward.
Learning Mode while logged in as an admin may also help if you have no luck with the above. From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform or trigger the actions on the URL that have been having problems connecting. Wordfence may learn that the communications taking place at this time are normal and will allow them in the future. After you have finished testing, make sure to switch the WAF from Learning Mode back to Enabled and Protecting.
Let me know what you find out,
Peter.
