Troubleshoot 404 errors
Updated
❓
File Not Found.
A 404 means the environment answered, but found no file and no route for the address. On fortrabbit the cause is almost always the code or the root path, rarely the platform.
Common causes
| Cause | Check |
|---|---|
| No code deployed | Log in with SSH or SFTP and look into the www folder |
| Wrong root path | Compare the root path setting with the folder that holds index.php, such as public or web |
| Files in an extra folder | Upload into www directly, not into www/my-project |
.htaccess missing | Only the homepage works, every other page is a 404. The hidden file was left out of an SFTP upload or the git repository |
| Typo in the address | Check the URL in the address bar |
A framework or CMS answers its own 404 for routes it does not know. That page has the app's design; the fortrabbit 404 page means Apache found no file and no rewrite rule sent the request to index.php.
Apache error log
The Apache error log in the logs names the cause with an AHxxxxx code. Behind a 404, look for AH00128: no file at the requested path under the root path. See Apache error codes for the full list. The 404 errors chart counts them per hour or day.
Platform status
When the code and the root path are right, check the fortrabbit status page for incidents.