How to fix WordPress 404 errors by checking permalinks from cPanel
A 404 error in this CMS appears when the server cannot find the requested URL, even if the page or post still exists in the dashboard. On shared hosting, a common cause is that permalinks or the .htaccess file became out of sync after a migration, domain change, cache plugin, or file edit from cPanel.
Before you start
- Have access to the CMS dashboard and cPanel for the affected domain.
- Confirm whether the error happens on all internal pages or only on some URLs.
- Make a copy of the
.htaccessfile before editing it from File Manager. - If you use a cache plugin, have access ready so you can clear cache after the change.
Steps
- Log in to the CMS dashboard and open Settings → Permalinks.
- Without changing the structure, save the configuration so the CMS regenerates its internal rules.
- Open a private window and test an internal page that previously showed
404 Not Found. - If the error continues, log in to cPanel and open File Manager or Administrador de archivos.
- Go to the site folder, usually
public_html, and locate the.htaccessfile. - Download a copy of the file before modifying it.
- Check that the standard CMS block is complete and is not duplicated or mixed with rules from another site.
- Save only the needed change, clear site cache if it applies, and test the affected URLs again.
What to check in .htaccess
| Signal | What it means | Safe action |
|---|---|---|
.htaccess does not exist | The CMS has no rules to resolve friendly URLs. | Save permalinks again or create the file with the standard CMS block. |
| There are several CMS blocks | A migration or plugin may have duplicated rules. | Keep a single block and back up the original file. |
| Redirect rules appear above the block | A previous rule may send the URL to another path. | Test temporarily disabling the suspicious rule after backing it up. |
| Incorrect permissions | The CMS cannot rewrite the file. | Use common permissions: 644 for files and 755 for folders. |
Final verification
- Internal pages load without showing
404 Not Found. - The CMS keeps the permalink structure you selected.
- The
.htaccessfile has a single CMS block for that site. - The private-window test works after clearing cache.
Common mistakes
- The homepage opens, but posts return 404 → Permalink rules were not regenerated → save Permalinks again and check
.htaccess. - The site changes to error 500 after editing → The
.htaccessfile has broken syntax → restore the copy and repeat the change with fewer rules. - Only some URLs fail → The page was deleted, the slug changed, or a redirect is incomplete → check the URL inside the dashboard before editing more files.
When to ask for help
Open a ticket if URLs still fail after regenerating permalinks, if .htaccess changes again by itself, or if the error appeared after a recent migration. Include the domain, affected URL, change time, and a copy of the current .htaccess so support can review the case faster.
Recommended reading
Still need help?
If this guide didn’t solve your issue, our team can help you via ticket.