Laravel ошибка 500 после установки

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

84.5k12 gold badges110 silver badges163 bronze badges

asked Jul 21, 2015 at 15:18

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

1,08410 silver badges19 bronze badges

answered Jul 22, 2015 at 11:06

DpENDpEN

4,1263 gold badges17 silver badges25 bronze badges

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

3,4123 gold badges28 silver badges46 bronze badges

answered May 3, 2017 at 14:23

GoodlifeGoodlife

3,7122 gold badges23 silver badges23 bronze badges

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

16.1k193 gold badges67 silver badges96 bronze badges

answered Sep 27, 2018 at 5:40

LestherLesther

4615 silver badges5 bronze badges

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

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:

Create a .env file in root (e.g. touch .env)
Make sure it contains at least one line: APP_KEY=
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

MarsAndBackMarsAndBack

8,7263 gold badges31 silver badges54 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

2373 silver badges19 bronze badges

answered Feb 8, 2017 at 20:03

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

25.2k26 gold badges212 silver badges345 bronze badges

answered Jun 1, 2016 at 7:07

SnriudSnriud

1432 silver badges7 bronze badges

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

answered Nov 23, 2015 at 18:58

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

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

SaeidSaeid

1801 silver badge7 bronze badges

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 PatelSmit Patel

1,63817 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

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 MelhemMaroun Melhem

2,7601 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

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

answered Oct 5, 2016 at 9:24

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),

'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_ikotsveti_iko

6,1783 gold badges43 silver badges37 bronze badges

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

27.8k28 gold badges54 silver badges59 bronze badges

answered Mar 13, 2017 at 16:23

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.

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

answered Jan 13, 2019 at 13:00

Anand MainaliAnand Mainali

9231 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 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

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

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

Thanks.

answered May 4, 2022 at 6:53

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

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

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

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

answered Jan 2, 2020 at 7:22

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♦

29.2k21 gold badges79 silver badges131 bronze badges

answered Feb 24, 2021 at 19:55

AdamAdam

3093 silver badges8 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

tomsihaptomsihap

1,69218 silver badges27 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

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

answered Nov 10, 2016 at 22:11

George PeterGeorge Peter

691 gold badge1 silver badge6 bronze badges

I faced this issue and fixed by upgrade my php version in apache up to 5.6.x

answered Jul 22, 2017 at 21:50

Mahmoud NiypooMahmoud Niypoo

1,4883 gold badges23 silver badges39 bronze badges

Источник

#1 26.03.2018 10:14:58

Загрузка Laravel на хостинг (HTTP ERROR 500)

Подскажите, как исправить ошибку. Загрузил проект laravel на хостинг. При загрузке в браузере отображается HTTP ERROR 500. На локальном веб-сервере все работает. Использую Open Server на Windows.

#2 26.03.2018 10:56:09

Re: Загрузка Laravel на хостинг (HTTP ERROR 500)

mod_rewrite включен.
права доступа к storage и bootstrap/cache установил 777

#3 26.03.2018 13:19:13

Re: Загрузка Laravel на хостинг (HTTP ERROR 500)

права доступа к storage и bootstrap/cache установил 777 — это не безопасно.. у вас чето с пользователем и группой напутано или не доступно… их настраивайте. а права должны быть типа sudo chmod -R 2775 *
короче 775, а не 777. я тоже на это напарывался. только у меня линукс с нгинксом. к сисадмину обратитесь за помощью

#4 26.03.2018 15:09:57

Re: Загрузка Laravel на хостинг (HTTP ERROR 500)

хорошо, на счет прав доступа понял. Пробовал запустить проект на Open Server с версией php 7.0 появляется аналогичная 500-я ошибка, как и на хостинге. На хостинге тоже версия php 7.0. Работает только с версией 7.1.7 локально. Проект только создан (laravel new blog), ничего в нем не изменял. Может проблема в версии php на хостинге или версии apache.

#6 27.03.2018 12:40:57

Re: Загрузка Laravel на хостинг (HTTP ERROR 500)

версия пхп низкая слишком.
на официальном сайте же написано
requirements:

PHP >= 7.1.3
OpenSSL PHP Extension
PDO PHP Extension
Mbstring PHP Extension
Tokenizer PHP Extension
XML PHP Extension
Ctype PHP Extension
JSON PHP Extension

#7 27.03.2018 13:28:59

Re: Загрузка Laravel на хостинг (HTTP ERROR 500)

Да, проблема была именно в версии. Спасибо!

Изменено sergeyruban (27.03.2018 13:29:10)

Источник

Содержание

Laravel ошибка 500 server error
Getting 500 server error with Laravel 5.7 #29112
Comments
Footer

Laravel ошибка 500 server error

I have an laravel app working fine on my local machine. I have just transferred it to my server ( Shared hosting ) and put everything on public folder in public_html and everything else in one step above public_html. The problem is now it shows 500 internal error on every route. I have changed .htaccess code to given code on documentation, folder rights to storage and bootstrap is set to 777. Nothing in error logs and also nothing in laravel log files. when I installed fresh laravel installation it worked on server as well. Tried updated code with my project but still 500 internal error. n

Its .htaccess code n

n n Options -MultiViewsn nn RewriteEngine Onnn # Redirect Trailing Slashes If Not A Folder. n RewriteCond % !-dn RewriteRule ^(.*)/$ /$1 [L,R=301]nn # Handle Front Controller. n RewriteCond % !-dn RewriteCond % !-fn RewriteRule ^ /index.php [L]n n n

Code in my composer.json file n

1.4″,n «mockery/mockery»: «0.9.*»,n «phpunit/phpunit»: «

Searching from 3 days found no solution yet. n»,»body_in_markdown»:»Hello guys rnrnI have an laravel app working fine on my local machine. I have just transferred it to my server ( Shared hosting ) and put everything on public folder in public_html and everything else in one step above public_html. The problem is now it shows 500 internal error on every route. I have changed .htaccess code to given code on documentation, folder rights to storage and bootstrap is set to 777. Nothing in error logs and also nothing in laravel log files. when I installed fresh laravel installation it worked on server as well. Tried updated code with my project but still 500 internal error.rnrnIts .htaccess code rn«`rn rn rn Options -MultiViewsrn rnrn RewriteEngine Onrnrn # Redirect Trailing Slashes If Not A Folder. rn RewriteCond % !-drn RewriteRule ^(.*)/$ /$1 [L,R=301]rnrn # Handle Front Controller. rn RewriteCond % !-drn RewriteCond % !-frn RewriteRule ^ /index.php [L]rn rn«`rnCode in my composer.json filernrn«`rn<rn «name»: «laravel/laravel»,rn «description»: «The Laravel Framework.»,rn «keywords»: [«framework», «laravel»],rn «license»: «MIT»,rn «type»: «project»,rn «require»: <rn «php»: «>=5.5.9»,rn »laravel/framework»: »5.1.*»,rn »illuminate/html»: »^5.0»,rn »laravel/socialite»: »^2.0»rn >,rn »require-dev»: <rn «fzaninotto/faker»: «

1.4»,rn »mockery/mockery»: »0.9.*»,rn »phpunit/phpunit»: »

Laravel expects to find your public files in the /public folder. Every request gets routed through /public/index.php . Laravel cannot find this file, hence the error. n

You have a few options, depending on your hosting: n

Rename the /public_html folder to /public . But then you will need to configure your server to use this directory. n
. or create a symlink that points /public to /public_html . n
. or configure Laravel to look in /public_html instead. n n

I can use 3rd option only which I used and still 500 internal error. n

I have installed fresh copy of laravel 5.1 on this same server which worked. But when I deploy my laravel app code it shows 500 internal error. n

total 1256 ndrwxr-xr-x 13 nicolas admin 442 Mar 6 10:34 appn-rw-r—r— 1 nicolas admin 8519 Mar 6 10:34 app.phpn-rw-r—r— 1 nicolas admin 1646 Mar 6 10:34 artisanndrwxr-xr-x 5 nicolas admin 170 Mar 6 10:34 bootstrapn-rw-r—r— 1 nicolas admin 1433 Mar 6 10:34 composer.jsonn-rw-r—r— 1 nicolas admin 121719 Mar 6 10:34 composer.lockndrwxr-xr-x 16 nicolas admin 544 Mar 6 10:34 configndrwxr-xr-x 6 nicolas admin 204 Mar 6 10:34 databasen-rw-r—r— 1 nicolas admin 530 Mar 6 10:34 gulpfile.jsn-rw-r—r— 1 nicolas admin 212 Mar 6 10:34 package.jsonn-rw-r—r— 1 nicolas admin 1026 Mar 6 10:34 phpunit.xmlndrwxr-xr-x 11 nicolas admin 374 Mar 6 10:34 publicn-rw-r—r— 1 nicolas admin 1918 Mar 6 10:34 readme.mdndrwxr-xr-x 6 nicolas admin 204 Mar 6 10:36 resourcesn-rw-r—r— 1 nicolas admin 567 Mar 6 10:34 server.phpndrwxr-xr-x 5 nicolas admin 170 Mar 6 10:34 storagendrwxr-xr-x 4 nicolas admin 136 Mar 6 10:34 testsn n»,»bodyInMarkdown»:»@kocoten1992 I am having the same issue. blank screen and error 500. Yet I think I have the correct permissions set. rn«`rntotal 1256 rndrwxr-xr-x 13 nicolas admin 442 Mar 6 10:34 apprn-rw-r—r— 1 nicolas admin 8519 Mar 6 10:34 app.phprn-rw-r—r— 1 nicolas admin 1646 Mar 6 10:34 artisanrndrwxr-xr-x 5 nicolas admin 170 Mar 6 10:34 bootstraprn-rw-r—r— 1 nicolas admin 1433 Mar 6 10:34 composer.jsonrn-rw-r—r— 1 nicolas admin 121719 Mar 6 10:34 composer.lockrndrwxr-xr-x 16 nicolas admin 544 Mar 6 10:34 configrndrwxr-xr-x 6 nicolas admin 204 Mar 6 10:34 databasern-rw-r—r— 1 nicolas admin 530 Mar 6 10:34 gulpfile.jsrn-rw-r—r— 1 nicolas admin 212 Mar 6 10:34 package.jsonrn-rw-r—r— 1 nicolas admin 1026 Mar 6 10:34 phpunit.xmlrndrwxr-xr-x 11 nicolas admin 374 Mar 6 10:34 publicrn-rw-r—r— 1 nicolas admin 1918 Mar 6 10:34 readme.mdrndrwxr-xr-x 6 nicolas admin 204 Mar 6 10:36 resourcesrn-rw-r—r— 1 nicolas admin 567 Mar 6 10:34 server.phprndrwxr-xr-x 5 nicolas admin 170 Mar 6 10:34 storagerndrwxr-xr-x 4 nicolas admin 136 Mar 6 10:34 testsrn«`»,»replies»:[],»user»:<«id»:1117,»username»:»Ncls»,»avatar»:»//www.gravatar.com/avatar/38f57dbbecbc78eaad243aa537594915?s=100&d=https%3A%2F%2Fs3.amazonaws.com%2Flaracasts%2Fimages%2Fforum%2Favatars%2Fdefault-avatar-2.png»,»experience»:<«award_count»:»0″,»level»:3,»points»:»12,755″,»pointsUntilNextLevel»:»2,245″>,»achievements»:[<«id»:16,»name»:»Ten Thousand Strong»,»description»:»Earned once your experience points hits 10,000.»,»level»:»intermediate»,»icon»:»ten-thousand-strong.svg»>],»reported»:null,»staff»:false,»subscribed»:false,»profile»:<«full_name»:null,»bio»:null,»twitter»:»»,»github»:»»,»website»:»»,»employment»:»Ghent»,»job_title»:»Developer»,»location»:»Ghent»,»flag»:»be»,»available_for_hire»:0>,»dateSegments»:<«created_diff»:»9 years ago»>,»settings»:<«show_profile»:true>,»links»:<«profile»:»https://laracasts.com/@Ncls»>>,»likes»:[],»created_at»:»2017-03-06T06:26:04.000000Z»,»links»:<«delete»:»/discuss/replies/322796″,»like»:»/discuss/replies/322796/likes»,»best_answer»:»/discuss/conversations/16344/best»>,»best_answer»:false,»dateSegments»:<«createdDiff»:»5 years ago»>>,<«id»:322926,»conversation_id»:16344,»body»:»

Permissions is not everything — if your php.ini is not set to display_errors, then you can still get the blank white screen. n

Related to permissions: Showing the permissions of the storage directory doesn’t give us enough information to see if it’s just a permissions issue because: n

The storage/logs , and other subdirectories, may have other permissions set n
We don’t know what user PHP is being run as, which determines if it can write to the storage directory (and its subdirectories). If user www-data is trying to write to directories owned by user nicolas , and user nicolas is the only user that can write to the directories (as permissions drwxr-xr-x is set), then the app won’t be able to write to that location n n»,»bodyInMarkdown»:»Permissions is not everything — if your php.ini is not set to display_errors, then you can still get the blank white screen.rnrnRelated to permissions: Showing the permissions of the `storage` directory doesn’t give us enough information to see if it’s just a permissions issue because:rnrn1. The `storage/logs`, and other subdirectories, may have other permissions setrn2. We don’t know what user PHP is being run as, which determines if it can write to the storage directory (and its subdirectories). If user `www-data` is trying to write to directories owned by user `nicolas`, and user `nicolas` is the only user that can write to the directories (as permissions `drwxr-xr-x` is set), then the app won’t be able to write to that location»,»replies»:[],»user»:<«id»:1966,»username»:»fideloper»,»avatar»:»//unavatar.io/github/fideloper»,»experience»:<«award_count»:»52″,»level»:11,»points»:»50,445″,»pointsUntilNextLevel»:»4,555″>,»achievements»:[<«id»:16,»name»:»Ten Thousand Strong»,»description»:»Earned once your experience points hits 10,000.»,»level»:»intermediate»,»icon»:»ten-thousand-strong.svg»>,<«id»:20,»name»:»Lifer»,»description»:»Earned if you have a lifetime subscription to Laracasts.»,»level»:»beginner»,»icon»:»lifer.svg»>],»reported»:null,»staff»:false,»subscribed»:true,»profile»:<«full_name»:null,»bio»:null,»twitter»:»fideloper»,»github»:»fideloper»,»website»:»http://fideloper.com»,»employment»:»UserScape»,»job_title»:»Product Engineer»,»location»:»San Antonio»,»flag»:»us»,»available_for_hire»:0>,»dateSegments»:<«created_diff»:»9 years ago»>,»settings»:<«show_profile»:true>,»links»:<«profile»:»https://laracasts.com/@fideloper»>>,»likes»:[],»created_at»:»2017-03-06T15:30:28.000000Z»,»links»:<«delete»:»/discuss/replies/322926″,»like»:»/discuss/replies/322926/likes»,»best_answer»:»/discuss/conversations/16344/best»>,»best_answer»:false,»dateSegments»:<«createdDiff»:»5 years ago»>>,<«id»:323378,»conversation_id»:16344,»body»:»

If the server have a multiple laravel projects in shared hosting, you can try this for fixing error 500. n

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

Reasons for this error: n

n

There mainly cause due to permission issues n

Environment variables not found or .env file not found on your root directory n

PHP extensions problem n

Database problem n n

Fix: n

n
Set the correct permissions: n n

n
Run these commands (Ubuntu/Debian) n n

find /path/to/your/root/dir/ -type f -exec chmod 644 <> \;nfind /path/to/your/root/dir/ -type d -exec chmod 755 <> \;nnchown -R www-data:www-data /path/to/your/root/dir/nnchgrp -R www-data storage bootstrap/cachenchmod -R ug+rwx storage bootstrap/cachen n

n
If .env file doesn’t exist, create one by touch .env and paste your environment variables and then run n n

php artisan key:generaten php artisan cache:clearn php artisan config:clearn composer dump-autoloadn n

n

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] n n

Check your database credentials and values in .env file. And grant permissions to the database user for that database. n n

These are some common problem you likely going to face when deploying your laravel app and one you start getting all these commands, I suggest you to make a script which will save your time. n»,»bodyInMarkdown»:»I read all the comments and suggestions. 500 — HTTP ERROR CODE represents internal server error.rnrn**Reasons for this error:**rnrn* There mainly cause due to permission issuesrn* Environment variables not found or `.env` file not found on your root directoryrn* PHP extensions problemrn* Database problemrnrn**Fix:**rnrn* Set the correct permissions:rn — Run these commands (Ubuntu/Debian) rn«`rnfind /path/to/your/root/dir/ -type f -exec chmod 644 <> \;rnfind /path/to/your/root/dir/ -type d -exec chmod 755 <> \;rnrnchown -R www-data:www-data /path/to/your/root/dir/rnrnchgrp -R www-data storage bootstrap/cachernchmod -R ug+rwx storage bootstrap/cachern«`rn — If **.env** file doesn’t exist, create one by `touch .env` and paste your environment variables and then run rnrn«`rn php artisan key:generatern php artisan cache:clearrn php artisan config:clearrn composer dump-autoloadrn«`rn — 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]`rn — Check your database credentials and values in `.env` file. And grant permissions to the database user for that database.rnrnThese are some common problem you likely going to face when deploying your laravel app and one you start getting all these commands, I suggest you to make a script which will save your time.»,»replies»:[<«id»:675758,»conversation_id»:16344,»body»:»

This isn’t a proper solution but, this was my case.nI had a prepared folder for the new Laravel application, but accidentally i installed into a sub folder within the main one. So i moved all the code one level above. n

I had error 500 and couldn’t load the page. n

I deleted the whole folder and installed again (composer/laravel) correctly into the main folder, this helped me. n

Create the .env file and also run : n

php artisan key:generaten n

This worked for me after pulling a git project. n

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

There are so many reasons the 500 error may occur. For me, it was a missing .env file. I cloned my own repo and set up everything, but I forgot to create the .env file. n

GraphQL is often looked at as the successor to REST APIs. It provides a powerful query language and allows you to make requests for exactly the information you want, nothing more and nothing less.

Источник

Getting 500 server error with Laravel 5.7 #29112

PHP: 7.2
Laravel: 5.7

Some requests failed with below error(Http 500- Server error), while other requests along the same request are successful. Passport is used to authenticate api request. api auth middleware is used.

production.ERROR: No application encryption key has been specified. <«exception»:»[object] (RuntimeException(code: 0): No application encryption key has been specified. at F:wamp64wwwservicevendorlaravelframeworksrcIlluminateEncryptionEncryptionServiceProvider.php:42)
[stacktrace]
#0 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateSupporthelpers.php(1041): IlluminateEncryptionEncryptionServiceProvider->IlluminateEncryption(NULL)
#1 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateEncryptionEncryptionServiceProvider.php(46): tap(NULL, Object(Closure))
#2 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateEncryptionEncryptionServiceProvider.php(24): IlluminateEncryptionEncryptionServiceProvider->key(Array)
#3 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateContainerContainer.php(764): IlluminateEncryptionEncryptionServiceProvider->IlluminateEncryption(Object(IlluminateFoundationApplication), Array)
#4 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateContainerContainer.php(646): IlluminateContainerContainer->build(Object(Closure))
#5 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateContainerContainer.php(601): IlluminateContainerContainer->resolve(‘encrypter’, Array)
#6 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationApplication.php(734): IlluminateContainerContainer->make(‘encrypter’, Array)
#7 F:wamp64wwwservicevendorlaravelpassportsrcPassportServiceProvider.php(271): IlluminateFoundationApplication->make(‘encrypter’)
#8 [internal function]: LaravelPassportPassportServiceProvider->LaravelPassport(Object(IlluminateHttpRequest), NULL)
#9 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateAuthRequestGuard.php(58): call_user_func(Object(Closure), Object(IlluminateHttpRequest), NULL)
#10 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateAuthGuardHelpers.php(60): IlluminateAuthRequestGuard->user()
#11 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateAuthMiddlewareAuthenticate.php(61): IlluminateAuthRequestGuard->check()
#12 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateAuthMiddlewareAuthenticate.php(41): IlluminateAuthMiddlewareAuthenticate->authenticate(Array)
#13 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateAuthMiddlewareAuthenticate->handle(Object(IlluminateHttpRequest), Object(Closure), ‘api’)
#14 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#15 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingMiddlewareThrottleRequests.php(57): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#16 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateRoutingMiddlewareThrottleRequests->handle(Object(IlluminateHttpRequest), Object(Closure), 120, ‘1’)
#17 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#18 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(104): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#19 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingRouter.php(667): IlluminatePipelinePipeline->then(Object(Closure))
#20 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingRouter.php(642): IlluminateRoutingRouter->runRouteWithinStack(Object(IlluminateRoutingRoute), Object(IlluminateHttpRequest))
#21 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingRouter.php(608): IlluminateRoutingRouter->runRoute(Object(IlluminateHttpRequest), Object(IlluminateRoutingRoute))
#22 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingRouter.php(597): IlluminateRoutingRouter->dispatchToRoute(Object(IlluminateHttpRequest))
#23 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpKernel.php(176): IlluminateRoutingRouter->dispatch(Object(IlluminateHttpRequest))
#24 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(30): IlluminateFoundationHttpKernel->IlluminateFoundationHttp(Object(IlluminateHttpRequest))
#25 F:wamp64wwwservicevendorspatielaravel-corssrcCors.php(28): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#26 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): SpatieCorsCors->handle(Object(IlluminateHttpRequest), Object(Closure))
#27 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#28 F:wamp64wwwservicevendorfideloperproxysrcTrustProxies.php(57): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#29 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): FideloperProxyTrustProxies->handle(Object(IlluminateHttpRequest), Object(Closure))
#30 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#31 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpMiddlewareTransformsRequest.php(31): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#32 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateFoundationHttpMiddlewareTransformsRequest->handle(Object(IlluminateHttpRequest), Object(Closure))
#33 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#34 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpMiddlewareTransformsRequest.php(31): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#35 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateFoundationHttpMiddlewareTransformsRequest->handle(Object(IlluminateHttpRequest), Object(Closure))
#36 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#37 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpMiddlewareValidatePostSize.php(27): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#38 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateFoundationHttpMiddlewareValidatePostSize->handle(Object(IlluminateHttpRequest), Object(Closure))
#39 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#40 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpMiddlewareCheckForMaintenanceMode.php(62): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#41 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(151): IlluminateFoundationHttpMiddlewareCheckForMaintenanceMode->handle(Object(IlluminateHttpRequest), Object(Closure))
#42 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateRoutingPipeline.php(53): IlluminatePipelinePipeline->IlluminatePipeline(Object(IlluminateHttpRequest))
#43 F:wamp64wwwservicevendorlaravelframeworksrcIlluminatePipelinePipeline.php(104): IlluminateRoutingPipeline->IlluminateRouting(Object(IlluminateHttpRequest))
#44 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpKernel.php(151): IlluminatePipelinePipeline->then(Object(Closure))
#45 F:wamp64wwwservicevendorlaravelframeworksrcIlluminateFoundationHttpKernel.php(116): IlluminateFoundationHttpKernel->sendRequestThroughRouter(Object(IlluminateHttpRequest))
#46 F:wamp64wwwservicepublicindex.php(55): IlluminateFoundationHttpKernel->handle(Object(IlluminateHttpRequest))
#47

«>

The text was updated successfully, but these errors were encountered:

No application encryption key has been specified.

Please setup app.key configuration before you run application. You can run php artisan key:generate to generate new app key.

I have already regenerated key and it didn’t help! In addition, I have run all the following commands:

composer dump-autoload
php artisan clear-compiled
php artisan config:clear
php artisan route:clear
php artisan view:clear

php artisan optimize
php artisan config:cache
php artisan route:cache
php artisan view:cache
php artisan cache:clear

These didn’t helped me either.

Unfortunately we don’t support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? We’ll help you out and re-open this issue if so.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Источник

Cover image for Laravel Internal Server Error 500 (solution)

Osman Forhad

Posted on Jan 20, 2021

• Updated on Mar 12, 2022

Basically, internal server error 500 is Laravel errors it’s not related to javascript or any other, to check this error go to chrome inspect->network and see the response.
it would be looks like the below screenshot.
Alt Text
This type of issue must be in controller related issue to solve this you have to check your controller function is written well,
.
and then you should check your router file whether (web.php or api.php) where you mention your controller file is properly.
.
If you are confused about why it’s happened and it too much worries you.
.
Here is another easy method to find out what is happening wrong. And this is your Laravel log file. Please check your Laravel log file. Hope you will find out your issue and solve it properly.
.
Happy Coding.
osman forhad
Mobile & Web Application Developer💻