HTTP 500 Internal Server Error for both the home page (/) and Laravel health endpoint (/up). No detailed error message is shown; APP_DEBUG is disabled for production.
Other Information
Hello InfinityFree Support,
Please help identify the server-side cause of HTTP 500 on my Laravel employee portal at https://ideonhrms.infinityfree.me/ . Both the home page and /up return HTTP 500. The site is configured for production with debug disabled, so it does not expose an error message. The Laravel storage/logs folder appears empty.
My hosting account shows Active with no deactivation history. The MySQL database exists in the account and the displayed database hostname is sql202.infinityfree.com. The deployed layout is a private sibling folder /ideon_app beside /htdocs; htdocs contains index.php and .htaccess, and index.php loads the sibling Laravel app. Static files such as robots.txt can be served, but PHP routes fail.
Could you please check the PHP error log for this domain and tell me the exact error? Please also confirm the PHP version and required extensions used by the website runtime, especially pdo_mysql, mbstring, openssl, fileinfo, xml, and dom, and whether there is any account-specific limitation affecting the request.
I have not enabled public error display and will not post credentials or .env contents. Thank you.
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
I can’t see the PHP error log for your domain, and I couldn’t find a source for the PHP version or extension list, so I can’t confirm those. But a 500 here has two causes, and you can tell them apart yourself.
The knowledge base article on HTTP 500 says it’s either crashed PHP code or an invalid .htaccess rule. It gives two ways to check:
To get the real PHP error: in the control panel, open Alter PHP Config and pick your domain. Click Alter PHP Directives, set “Display Errors” to “On”, and save. Then reload the page. This is a host-level setting, so it should work even with APP_DEBUG off. If nothing shows, the article says the application is probably suppressing errors in its own code, for example with ini_set('display_errors', 0) or error_reporting(0).
To rule out .htaccess: rename it to something like .htaccess.backup and reload. The article says .htaccess errors never produce a message, so this is the only way to test it. If the 500 disappears, the problem is in that file.
An empty storage/logs folder fits a crash before Laravel starts logging, or a permissions problem. For example, index.php might not be finding vendor/autoload.php in /ideon_app. That’s only a guess from what you described, though. The error message from the first check would settle it.
If you post the exact error text (leave out any credentials) and say whether renaming .htaccess changed anything, someone can narrow it down from there.
I checked your site and it seems to be working fine now. But I still wanted to reply to some of your requests.
We don’t store error logs on free hosting. If we did, we’d give you access to them by default, because having logs that we don’t care about and you don’t have access to is pointless. And a setup where staff has to get log data for you is a setup nobody would be happy with.
You can use a PHP info to confirm the PHP settings of your account. But we run PHP 8.4 using all the common extensions, including everything needed by Laravel.
Free hosting is a commodity service, every account should be the same. So no, account specific limitations are not a thing.
Good. This is a public forum so you shouldn’t do that.