# Cannot see errors in Codeigniter project **URL:** \ **Category:** Hosting Support\ **Created:** [July 9, 2023, 7:01am UTC](https://forum.infinityfree.com/t/cannot-see-errors-in-codeigniter-project/78720 "2023-07-09T07:01:53Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\ **Post date:** [July 9, 2023, 11:54am UTC](https://forum.infinityfree.com/t/cannot-see-errors-in-codeigniter-project/78720/6 "2023-07-09T11:54:05Z")
I see the HTTP ERROR 500 too, but just on the page itself, not with a redirect. This gives me the idea that the .htaccess rules are now working, and this is a PHP code crash. Usually, the place to start with these issues is to enable error messages so you can see why the PHP code crashed: > [@Http error 500](https://forum.infinityfree.com/t/http-error-500/49352): > > When trying to access your website, you may see a page which returns the status code “500”. In Google Chrome, you’ll see a page with the error code HTTP ERROR 500. There are typically two reasons which can cause this error: The PHP code has crashed. The .htaccess file contains invalid rules. Here are some things you can try to debug and fix this. Fixing crashing PHP code A HTTP ERROR 500 simply tells you that the PHP code has crashed, but gives no information as to why it has crashed. Gett… I did go ahead and test this for you. It seems that there is some configuration in your site that uses file paths that uses backslashes instead of forward slashes. If you developed the site on Windows, that would be the way to do it. But our servers run Linux, which uses forward slashes for directories, not backslashes, so the paths do note work. Please update your site’s configuration to use forward slashes, not backslashes, in file paths. --- _[View the full topic](https://forum.infinityfree.com/t/cannot-see-errors-in-codeigniter-project/78720)._