500 ошибка сервера laravel

I have installed Laravel many times on Windows OS but never had this problem.

However, on Ubuntu 14.04 I am getting a 500 Internal Server Error, and messages like this in my logs:

[Wed Jul 22 10:20:19.569063 2015] [:error] [pid 1376] [client 127.0.0.1:52636] PHP Fatal error: require(): Failed opening required ‘/var/www/html/laravel_blog/../bootstrap/autoload.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) in /var/www/html/laravel_blog/index.php on line 22

Previously I’ve had problems when mod_rewrite was not installed or set up properly, but I have installed it and it is not working. Changed .htaccess as well from original to this.

    +FollowSymLinks
RewriteEngine On

RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^ index.php [L]

I’ve given access to all my folders and files inside i.e.

/var/www/html/laravel_project

I have all the necessary extensions needed for Laravel 5+ as well. Is there something left that I didn’t do?

IMSoP's user avatar

IMSoP

88.1k13 gold badges115 silver badges168 bronze badges

asked Jul 21, 2015 at 15:18

DpEN's user avatar

9

Finally Overcame the problem

  • It was not the .htaccess file that was the problem nor the index.php. The problem was on accessing the files and requiring permissions.

For solving the problem i ran the following commands through terminal.

sudo chmod -R 755 laravel_blog

and then type below to allow laravel to write file to storage folder

chmod -R o+w laravel_blog/storage

This two commands solved the problem.

C.Liddell's user avatar

C.Liddell

1,08410 silver badges19 bronze badges

answered Jul 22, 2015 at 11:06

DpEN's user avatar

DpENDpEN

4,2063 gold badges17 silver badges26 bronze badges

12

Create the .env file and also run :

php artisan key:generate

This worked for me after pulling a git project.

After creating .env file and generating the key, run the code below:

php artisan cache:clear 
php artisan config:clear

tchap's user avatar

tchap

3,4123 gold badges29 silver badges46 bronze badges

answered May 3, 2017 at 14:23

Goodlife's user avatar

GoodlifeGoodlife

3,7822 gold badges23 silver badges23 bronze badges

5

Try to check if you have .env file.

Mostly this thing can cause something like that. Try to create a file then copy everything from .env.example, paste it to your created file and name it .env. or jsut simply rename the .env.example file to .env and run php artisan key:generate

Unheilig's user avatar

Unheilig

16.2k193 gold badges68 silver badges98 bronze badges

answered Sep 27, 2018 at 5:40

Lesther's user avatar

LestherLesther

4915 silver badges5 bronze badges

2

After installing run below command

sudo chmod 755 -R laravel
chmod -R o+w laravel/storage

here «laravel» is the name of directory where laravel installed

answered Mar 8, 2016 at 5:58

Sujendra Kumar's user avatar

2

Make sure a .env file, containing an APP_KEY, exists in root.

What should be in the .env hasn’t been explicitly stated in other solutions, and thought I’d boil it down to the sentence above.

This fixed my 500 error on a fresh install of Laravel.

Steps:

  1. Create a .env file in root (e.g. touch .env)
  2. Make sure it contains at least one line: APP_KEY=
  3. Generate an app key in terminal: php artisan key:generate

More .env paramaters:

As a reference, here’s the official .env with useful baseline parameters. Copy-paste what you need:

https://github.com/laravel/laravel/blob/master/.env.example

Notes:

  • My particular installation didn’t include any .env whatsoever (example or otherwise)

  • Simply having a blank .env does not work.

  • A .env containing parameters, but no APP_KEY parameter, does not work.

Bug?: When generating an app key in terminal, it seems to falsely report success, however no key will actually get placed in the .env if the file is missing a line starting with APP_KEY=.

answered Apr 10, 2020 at 16:06

Kalnode's user avatar

KalnodeKalnode

9,1783 gold badges33 silver badges61 bronze badges

I fixed with this Command:

   rm -rf app/storage/logs/laravel.logs
   chmod -R 777 app/storage,
   php artisan cache:clear,
   php artisan dump-autoload OR composer dump-autoload

Than restart a server eather XAMPP ore another one and that should be working.

Khushal's user avatar

Khushal

2414 silver badges19 bronze badges

answered Feb 8, 2017 at 20:03

Atdhe Kurteshi's user avatar

1

I have faced a similar error. I checked the log in /var/log/apache2/error.log and found an UnexpectedValueException

I changed the owner to my apache user of the storage folder under the project dir.

sudo chown -R www-data:www-data ./storage

In my case apache2 process owner is www-data, so change this to yours, this can be found in apache2 config file. Hope this is useful to you.

Naman's user avatar

Naman

27k26 gold badges218 silver badges350 bronze badges

answered Jun 1, 2016 at 7:07

Snriud's user avatar

SnriudSnriud

1432 silver badges7 bronze badges

0

May another solution to this problem:

Install the required packages by running the composer command from the the root of the project:

sudo composer install

UPDATE:

  • You should not run this command on a production server, but some issues with composer can be resolved with this on local envs.

EDIT:

  • take a look at https://getcomposer.org/doc/faqs/how-to-install-untrusted-packages-safely.md to see why running composer install as root is not a good idea
  • If you need to run it as root, provide the following flags, to block third-party code from executing durin the install —no-plugins —no-scripts

LeonTheProfessional's user avatar

answered Nov 23, 2015 at 18:58

Christos Papoulas's user avatar

3

run these commands

1. composer install 
2. mv .env.example .env 
3. php artisan cache:clear 
4. composer dump-autoload 
5. php artisan key:generate

I had this problem …

answered Feb 5, 2022 at 11:58

Saeid's user avatar

SaeidSaeid

3623 silver badges9 bronze badges

Create .env file with the below cmd command:

cp .env-example .env

Then generate a key for your project:

php artisan key:generate

After that clear your caches using the below commands:

//---Delete Configuration Cahce
php artisan config:cache
//---Clear Application Cache
php artisan cache:clear

answered Jul 5, 2021 at 3:39

Hedayatullah Sarwary's user avatar

I read all the comments and suggestions. 500 — HTTP ERROR CODE represents internal server error.

Reasons for this error:

  • These mainly cause due to permission issues
  • Environment variables not found or .env file not found on your root directory
  • PHP extensions problem
  • Database problem

Fix:

  • Set the correct permissions:
  • Run these commands (Ubuntu/Debian)
find /path/to/your/root/dir/ -type f -exec chmod 644 {} ;
find /path/to/your/root/dir/ -type d -exec chmod 755 {} ;

chown -R www-data:www-data /path/to/your/root/dir/

chgrp -R www-data storage bootstrap/cache
chmod -R ug+rwx storage bootstrap/cache
  • If .env file doesn’t exist, create one by touch .env and paste your environment variables and then run
   php artisan key:generate
   php artisan cache:clear
   php artisan config:clear
   composer dump-autoload
  • Check your php.ini file and uncomment the extensions you need (In some case you have to install the extension by running this command apt-get install php7.2-[extension-name]
  • Check your database credentials and values in .env file. And grant permissions to the database user for that database.

These are some common problem you likely going to face when deploying your laravel app and once you start getting all these commands, I suggest you to make a script which will save your time.

answered Jun 30, 2019 at 7:11

Smit Patel's user avatar

Smit PatelSmit Patel

1,66017 silver badges21 bronze badges

I had PHP 7.0 and PHP 7.1 installed and I was using PHP 7.1 on command line and PHP 7.0 was enabled on Apache, that messy can bring problems when you are using Laravel Framework and localhost Apache2 with laravel.

Check your composer file first to see your PHP version.

"php": "^7.1.3",
"laravel/framework": "5.6.*",

Check your currently php version on command line

php -v

Check your currently php version enabled on Apache, I did using browser.

http://localhost

If it’s not the same disable the current version and enable the newest one.

sudo a2dismod php7.2

sudo a2enmod php7.1

sudo service apache2 restart

After that change folder permissions

sudo chmod 755 -R blog

for storage folder

chmod -R o+w blog/storage

answered Aug 31, 2018 at 20:58

Saulo Campos's user avatar

0

A frequent issue when using git:

Laravel's .gitignore ignores the .env file which when missing generates this error

Solved this by manually adding an .env file on the server or uploading it through FTP

answered Dec 31, 2018 at 17:05

Maroun Melhem's user avatar

Maroun MelhemMaroun Melhem

2,9701 gold badge19 silver badges22 bronze badges

First, if there is not .env file in your Laravel repository. Copy the .env.example file using the following cmd command cp .env.example .env and open .env file and apply your configuration if needed.

Run these commands:

//---Generate Key in your project
php artisan key:generate
//---Flush the application cache
php artisan cache:clear
//---Remove the configuration cache file
php artisan config:cache
php artisan config:clear
//---Regenerates the list of all classes that need to be included in the project
composer dump-autoload
//---Restart your Server
php artisan serve

answered May 13, 2020 at 6:10

Hedayatullah Sarwary's user avatar

Sometimes there is problem with php version. We need to change php version from server. Just write down below string in .htaccess file:

AddHandler application/x-httpd-php5 .php

Alexander Farber's user avatar

answered Oct 5, 2016 at 9:24

Riyan Sheikh's user avatar

0

First allow all permissions for your project folder (let say it’s called laravel), for the storage subfolder and its logs subsubfolder and for the vendor subfolder (laravel/storage, laravel/storage/logs and laravel/vendor).

Then check if your have .env file — if not you can run:

$ mv .env.example .env

to rename your build-in .env.example to the needed .env.

Otherwise turn on the debug mode — open .env and set

APP_DEBUG=true

and open laravel/config/app.php and change

'debug' => env('APP_DEBUG', false), 

to

'debug' => env('APP_DEBUG', true),

so you can find out what is the reason for your error.

answered Nov 29, 2016 at 15:03

tsveti_iko's user avatar

tsveti_ikotsveti_iko

6,6263 gold badges46 silver badges37 bronze badges

2

Run these two commands in the directory where Laravel is installed:

sudo chmod 755 -R DIRECTORY_NAME
chmod -R o+w DIRECTORY_NAME/storage

Then clear the cache and dump the auto load:

php artisan cache:clear
composer dump-autoload

zx485's user avatar

zx485

28.3k28 gold badges50 silver badges59 bronze badges

answered Mar 13, 2017 at 16:23

Ayman's user avatar

AymanAyman

313 bronze badges

I have faced this problem many times. Try one of these steps it helped me a lot. Maybe it will also help you.

  1. First of all check your file permissions.
  2. To fix file permissions sudo chmod 755 -R your_project
  3. Then chmod -R o+w your_project/storage to write file to storage folder.
  4. php artisan cache:clear
    composer dump-autoload
  5. php artisan key:generate
  6. Then check server requirements as per the laravel requirement.
  7. Many times you got this error because of the php version. Try changing your php version in cpanel.
  8. Then configure your .htaccess file properly

answered Jan 13, 2019 at 13:00

Anand Mainali's user avatar

Anand MainaliAnand Mainali

9731 gold badge13 silver badges23 bronze badges

If you use vagrant, try this:

First remove config.php in current/vendor.

Run these command:

php artisan config:clear
php artisan clear-compiled
php artisan optimize

NOT RUN php artisan config:cache.

Hope this help.

answered Feb 10, 2020 at 9:32

Hanh Nguyen's user avatar

Hanh NguyenHanh Nguyen

1251 silver badge12 bronze badges

if its on a live server try this

<IfModule mod_rewrite.c>
<IfModule mod_negotiation.c>
    Options -MultiViews -Indexes
</IfModule>
Options +FollowSymLinks
RewriteEngine On
RewriteBase /


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

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

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

then also make sure that the php version in your composer.json is the same as that of your server.

Check your php version in your terminal using php -v

answered May 13, 2019 at 20:26

The Billionaire Guy's user avatar

Check if your .env file is present or not in file structure.
if not, follow the procedures:

  1. run command cp .env.example .env from projects root directory.
  2. run command php artisan key:generate
  3. refresh the browser.

Thanks.

answered May 4, 2022 at 6:53

Mehraab Hossain's user avatar

0

Run these two commands on root of laravel

find * -type d -print0 | xargs -0 chmod 0755 # for directories

find . -type f -print0 | xargs -0 chmod 0644 # for files

answered Jun 7, 2016 at 17:43

Davinder Singh's user avatar

I have a similar issue with a share Host. I was having 500 error. I just fixed by checking the Laravel version and PHP version. The error was because Laravel 5.6 doesn’t run on PHP 7.0.x Once I know this I just reconfigure the project to Laravel 5.5 that is compatible with PHP 7.0.x now everything is right. Another reason I have issues sometimes is the FTP I get corrupted Files and have to upload the project more than once.
Hope this help in the future I don’t found so many information in this topic.

answered Feb 21, 2018 at 13:07

Josean Maya's user avatar

0

For those of you who like me still got errors after trying all the other answers :

Check the version of php apache uses, latest laravel only works with php7.1.
So you have to :

sudo a2dismod php[yourversion]
sudo a2enmod php7.1
sudo systemctl restart apache2

hope this helps

answered Apr 26, 2018 at 12:06

Ika's user avatar

Make sure, you’ve run composer update on your server instance.

answered Jan 2, 2020 at 7:22

Usama Munir's user avatar

Usama MunirUsama Munir

5899 silver badges11 bronze badges

I fixed this problem by this commands:

mv .env.example .env
php artisan cache:clear
composer dump-autoload
php artisan key:generate

then

php artisan serve

Dharman's user avatar

Dharman

30.5k22 gold badges84 silver badges133 bronze badges

answered Feb 24, 2021 at 19:55

Adam's user avatar

AdamAdam

3093 silver badges8 bronze badges

0

php artisan require APP_KEY in .env file.
So firstly create .env file in root,

sudo nano .env

and add APP_KEY= in first line,
save the file and run

sudo php artisan key:generate

answered Jan 18 at 14:51

Ahsan Khan's user avatar

Ahsan KhanAhsan Khan

1492 silver badges3 bronze badges

According to the logs :

[06-Feb-2016 22:38:48 Europe/Berlin] PHP Warning:  require(/Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in /Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/autoload.php on line 17
[06-Feb-2016 22:38:48 Europe/Berlin] PHP Fatal error:  require(): Failed opening required '/Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/../vendor/autoload.php' (include_path='.:/Applications/MAMP/bin/php/php7.0.0/lib/php') in /Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/autoload.php on line 17
[06-Feb-2016 22:43:37 Europe/Berlin] PHP Warning:  require(/Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in /Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/autoload.php on line 17
[06-Feb-2016 22:43:37 Europe/Berlin] PHP Fatal error:  require(): Failed opening required '/Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/../vendor/autoload.php' (include_path='.:/Applications/MAMP/bin/php/php7.0.0/lib/php') in /Users/tomsihap/Documents/Development/mamp/partie_1_exo/bootstrap/autoload.php on line 17

There are some failures opening files into the /vendor folder.

By installing and updating via composer, I was able to finally solve the issue.

sudo composer install
sudo composer update

answered Feb 6, 2016 at 23:46

tomsihap's user avatar

tomsihaptomsihap

1,70218 silver badges29 bronze badges

Make sure storage folder with write previlege (chmod o+w), work for me like a charm.

answered Sep 21, 2016 at 1:32

user3619249's user avatar

0

Because of no right to write the log’s directory.
chmod 755 storage -R

answered Nov 10, 2016 at 22:11

George Peter's user avatar

George PeterGeorge Peter

691 gold badge1 silver badge6 bronze badges

1

Всем доброго времени суток!
Ребят, тут дело такое.. перестало заходить в админку по ссылке site.com/admin после того как я дома ОС переустановил =) выдает ошибку 500. До этого все работало.
В логах по адресу /storage/logs/laravel.log ошибки нет; права выставлял 777 — все впустую; все файлы с бекапом сверял — все в порядке; и перезагружал тоже. Пытался с разных браузеров заходить результат тот же.
Позже додумался зайти поглубже site.com/admin/pages или site.com/admin/all и т.д. по этим ссылкам переходит и все нормально работает, а вот site.com/admin никак не хочет. Чудеса.
До этого раньше бывало, браузер хром в админке ломался и ошибки выдавал. Вроде все.

Спасибо!


  • Вопрос задан

    более трёх лет назад

  • 11048 просмотров

1) Включите в .env
APP_DEBUG=true
Должно выводить подробности ошибки на экран (500 — ни о чем не говорит).

2) Если нет, то это может быть ошибка веб-сервера. (например, некорректный htaccess).

>>В логах по адресу /storage/logs/laravel.log ошибки нет;

скорее всего до ларавеля не доходит, либо не может его запустить.

для начала посмотри логи веб-сервера,
.htaccess
версию php
сделайте файл <?php phpinfo(); и посмотрите срабатывает ли он

Пригласить эксперта

Ну здесь телепатов нет, поэтому включайте debug режим и смотрите, в чем проблемы.

Ребят, все же проблема была как мне кажется в htaccess, сейчас еще разок решил установить разрешения 755 на все файлы, но только через ftp и все заработало, до этого менял через терминал.
А вообще какое должно быть разрешение на файлах и на каталогах?
до этого всегда ставил на каталоги 755, на файлы 644.


  • Показать ещё
    Загружается…

21 июн. 2023, в 15:55

3000 руб./за проект

21 июн. 2023, в 15:40

5000 руб./за проект

21 июн. 2023, в 15:31

400 руб./за проект

Минуточку внимания

Начнём с того, что 500 —
это код ответа сервера ,
который является обобщённым и говорит только о том, что произошла ошибка, но не говорит о самой ошибке.

Поэтому, первое что необходимо сделать — найти ошибку в логах,
смотри «Где найти логи?»

Обрати внимание что возвращает 500 ошибку, Laravel или web-сервер (nginx, apache):

  • если фреймворк, тогда смотри логи лары или включи debug mode
  • если web-сервер, тогда смотри логи web-сервера, скорей всего проблема с конфигураций,
    а в случае с apache проблема чаще всего в .htaccess

Фреймворк возвращает 500 ошибку при любом исключении, кроме 404 (не найдено),
419 (неверный CSRF-токен), 422 (ошибка валидации),
401 (авторизация) и 403 (отказано в доступе).

Также вызов dd() вернёт 500 код.

Если ошибка произошла с AJAX-запросом,
то в DevTools ,
на вкладке network, при условии что включён debug mode,
также можно найти полное описание ошибки и стектрейс.

Рекомендую воспользоваться инструментом Telescope ,
для более удобного мониторинга запросов в процессе разработки.
А для мониторинга ошибок в production —
Sentry

  • Dec-23-2022
  • Techsolutionstuff

  • Laravel
    PHP
    jQuery

In this article, we will see 500 internal server errors in laravel 9 ajax. Also, we can see how to solve or fixed laravel 9 500 internal server error ajax. If you are fetching 500 internal server errors in jquery ajax post request in laravel 9. Here we will let you know how to fix the ajax post 500 (Internal Server Error) request in laravel 9.

Laravel provides the best security using the csrf token. So, you have each time pass csrf_token when you fire ajax in the post, delete or put a request. You can generate csrf token using the csrf_token() helper of laravel 9. we will see you how to generate csrf_token and pass on each ajax request of jquery. 

Also, you can add below meta tag and then you have to simply pass headers. It will automatically pass a token on each post request.

Add Meta tag:

<meta name="csrf-token" content="{{ csrf_token() }}">

Add JS Code:

$.ajaxSetup({

headers: {

'X-CSRF-TOKEN': $('meta[name="csrf-token"]').attr('content')

}

});

As above both codes, you have to write on each page. So, you can simply put it on the layout page or common header page.


You might also like :

  • Read Also: Order By Query In Laravel 9 Example
  • Read Also: Socialite Login with Facebook Account In Laravel 9
  • Read Also: How To Solve The Page Expired 419 Error In Laravel
  • Read Also: User Roles And Permissions Without Package Laravel 9

RECOMMENDED POSTS

FEATURE POSTS

HTTP status code 500 means there’s something wrong with the server. It could be an error in your PHP app, an error in the webserver config file, or a module that is missing from your server.

Causes of 500 error

  1. Something is wrong in the PHP code: Sometimes the code has some sort of error eg: you might have a syntax error, a runtime error, etc. In order to check what’s wrong with your Laravel (PHP) app, you need to add the following lines in the PHP script from which the execution starts.
    ini_set('display_errors', 1);
    ini_set('display_startup_errors', 1);
    error_reporting(E_ALL);

For Laravel, you need to add the above three lines in public/index.php, for WordPress, it is index.php and for a core PHP website, it will be the name of the PHP script mentioned at end of the URL.

After adding the above three lines. Reload the page and you will see an error message. Search for that error message and you will surely get a solution for it. If you don’t see an error message then follow the next step.

2. Something is wrong with Web Server configuration: If you don’t get any error message in the browser after adding the above code. Then the issue is not the web app itself. It could be the webserver you are using the services of the app. So check the access logs and error logs of that webserver. For Apache its at /var/log/apache2/ or at `/var/log/httpd/`. For Nginx its at /var/log/nginx/.

In these files search for the path (part of the URL after domain) at which you are getting an error. Look at the last entry for that path in the file and search on Google for the error mentioned in that line.

Возможно, вам также будет интересно:

  • 500 ошибка выполнения операции барс
  • 500 непредвиденная ошибка произошла ошибка выполнить запрос не удалось повторите попытку
  • 500 неизвестная ошибка сервера
  • 500 на сервере произошла ошибка пока ее исправляют можете взглянуть на наше особенное предложение
  • 500 к сожалению во время обработки запрашиваемой страницы произошла ошибка повторите попытку позже

  • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии