Member or group pages return 404

Community URLs such as /members/, /groups/ or a single member profile return “page not found”, while the rest of the site works.

This is nearly always WordPress rewrite rules or BuddyPress page assignment rather than the theme. Reign styles those screens, it does not create their URLs.

Work down in order.

1. Flush permalinks

The fix for most cases, and it takes seconds.

Go to Settings > Permalinks and select Save Changes. You do not need to change anything. Saving regenerates the rewrite rules, which is what community URLs depend on.

Rules go stale after activating or deactivating a community plugin, after a migration, and sometimes after an update. Do this first every time.

2. Check the pages are assigned

BuddyPress maps each component to a real WordPress page. If a page was deleted, trashed or never assigned, its URLs 404.

Go to Settings > BuddyPress > Pages and confirm every active component has a page selected. If a dropdown is empty, create a page and assign it, then flush permalinks again.

The same applies on BuddyBoss Platform, under its own settings.

3. Check the component is switched on

A URL for a disabled component 404s because nothing is registered to serve it.

Under Settings > BuddyPress > Components, confirm the component is enabled. Groups and Activity are the two most often turned off by accident.

4. Check Reign’s 404 page mapping

Specific to Reign, and worth knowing because it changes what you see.

Customize > General > Page Mapping lets you choose a custom page for login, registration and 404. When a 404 page is mapped, Reign redirects to it rather than rendering the standard 404 template.

The practical effect: if you set this, a broken community URL sends visitors to your custom page instead of showing an obvious error, which can make the problem look like a redirect rather than a 404 while you are diagnosing it.

Set it to none while you troubleshoot, so you can see the real behaviour.

Worth knowing for SEO too: redirecting all 404s to a page means search engines see a redirect and a valid page rather than a 404, which is a soft 404. Use it deliberately.

5. Check for a slug collision

If a WordPress page, post or custom post type uses the same slug as a community component, one wins and the other 404s.

The classic case is a page called “Members” sitting at /members/ while BuddyPress also wants that path. Rename or delete the conflicting content and flush permalinks.

6. Rule out the theme

Switch to a default WordPress theme and load the failing URL.

If it still 404s, the cause is in WordPress or the community plugin, not Reign. If it works on the default theme and not on Reign, that is worth reporting: send us the URL and your System status from Reign Settings > Tools.

Server-level cases

If everything above checks out and URLs still fail, the rewrite rules may not be reaching WordPress at all.

On Apache, confirm .htaccess exists in the WordPress root, is writable, and contains the standard WordPress block. On nginx, confirm the config has the usual try_files $uri $uri/ /index.php?$args; rule. A missing rule breaks every pretty permalink, so if plain posts also 404, this is where to look.

Report it

Open a ticket with the failing URL, whether it also fails on a default theme, and your System status.