500 internal server error

my website just keep throwing me error

500 Internal Server Error

Something on the website crashed!

when i open the website

its a laravel website by the way, i’m using free account to host it

Please open a new topic rather then posting your problem in someone else their thread.

6 Likes

my website keep throwing me this error when i try to opened it

okey

I receive 404 error, What is that? The server tried to find a page that doesn’t or didn’t exist.
Keep in mind that as far as I know InfinityFree does not support Laravel.

Please read

Do note that posting the same thing will not get you a different answer

7 Likes

Infinity free does support Laravel. Afterall its just a framework that uses html and PHP. but you have to be a bit clever with your .htaccess:

5 Likes

i already did that, but they automaticly change my .htaccess file

i already try that to, its still not working :downcast_face_with_sweat:

Ok, so have you turned on the full errors in the client area? that should let you see what’s causing the error?

If its still showing as an error 500 with no more details after that, its probably an error in the .htaccess file.

wait, where could i turn on the errors?

Its in the article above. but if you go to your account dashboard:


click manage:

Select PHP options:

and turn on “Display errors”

5 Likes

okey, i just turned on the display errors, then when refresh the page, its still giving me the same error which is the

500 Internal Server Error
Something on the website crashed!

Right, so thats most likely a .htaccess issue.

can you share your .htaccess file so we can help check for errors

1 Like

of course

Options -MultiViews -Indexes
RewriteEngine On

# Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

# Handle X-XSRF-Token Header
RewriteCond %{HTTP:x-xsrf-token} .
RewriteRule .* - [E=HTTP_X_XSRF_TOKEN:%{HTTP:X-XSRF-Token}]

# Redirect Trailing Slashes If Not A Folder...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} (.+)/$
RewriteRule ^ %1 [L,R=301]

# Send Requests To Front Controller...
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

Laravel has its own error handling system, so the display_error setting doesn’t work.

Instead, you could be able to get more information by setting APP_DEBUG=true in the .env file, or set the debug option to true in the config/app.php file.

6 Likes

Oh I didn’t know that…

I’ve also checked the .htaccess and it looks good, so try what Admin has suggested there to see if you can get more info :slight_smile:

1 Like

image

i already turned it on