Quick troubleshooting view
The home page works but internal articles or pages return 404 after a migration or modification of permalians.
- unregenerated rewrite rules
- wrong.htaccess file
- missing Nginx configuration
- Re-register permaleans
- Check the web server
- Test a specific page
- regenerating the rewriting rules
- restore the appropriate Apache/Nginx rules
- empty caches after correction
Contextual technician plan
Open Settings → Permalians and save without changing the structure.
“Re-register permaleans” should produce an observation that clearly confirms or rules out “unregenerated rewrite rules”.
If the observation is normal, lower “unregenerated rewrite rules” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “unregenerated rewrite rules” first. Related action: regenerating the rewriting rules.
Control.htaccess under Apache or try_files under Nginx.
“Check the web server” should produce an observation that clearly confirms or rules out “wrong.htaccess file”.
If the observation is normal, lower “wrong.htaccess file” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “wrong.htaccess file” first. Related action: restore the appropriate Apache/Nginx rules.
Compare a standard page and a CPT.
“Test a specific page” should produce an observation that clearly confirms or rules out “missing Nginx configuration”.
If the observation is normal, lower “missing Nginx configuration” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “missing Nginx configuration” first. Related action: empty caches after correction.
Check if an extension changes the re rygle rules.
“Control plugins” should produce an observation that clearly confirms or rules out “modified slug or CPT base”.
If the observation is normal, lower “modified slug or CPT base” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “modified slug or CPT base” first. Related action: avoid changing public slugs without redirection plan.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Escalader if only the roads of a personalized CPT remain in 404 despite a correct petit re petit.
The home page works but internal articles or pages return 404 after a migration or modification of permalians.
Causes probables
- unregenerated rewrite rules
- wrong.htaccess file
- missing Nginx configuration
- modified slug or CPT base
Diagnostic étape par étape
- 1
Re-register permaleans
Open Settings → Permalians and save without changing the structure.
- 2
Check the web server
Control.htaccess under Apache or try_files under Nginx.
- 3
Test a specific page
Compare a standard page and a CPT.
- 4
Control plugins
Check if an extension changes the re rygle rules.
Solutions possibles
- regenerating the rewriting rules
- restore the appropriate Apache/Nginx rules
- empty caches after correction
- avoid changing public slugs without redirection plan
Escalader if only the roads of a personalized CPT remain in 404 despite a correct petit re petit.