CODEWITHSUNDEEP
phplaravelamazon-web-servicesamazon-elastic-beanstalk
Faisal Shani
Faisal Shani

Reputation: 810

AWS Elastic Beanstalks shows "whoops! there was an error" on its url after uploading Laravel Project

I need your help. I have created a website on Laravel and its working totally fine on my localhost but when I deploy it on AWS using Elastic Beanstalk it shows "Whoops There was an error" title page only without any error or text on the page except title.

I have tried many options like changing env file name, generating app key, changing root folder from / to /public but it just doesn't work. Below I am sharing you my folder structure that I am uploading to AWS beanstalk after zipping. Here is elastic beanstalk url. http://lessyes.us-east-1.elasticbeanstalk.com/

enter image description here

Upvotes: 0

Views: 377

Answers (2)

Qumber
Qumber

Reputation: 14559

This is for future users - if you are not seeing actual errors other than "Whoops There was an error", this probably means your app is not in debug mode. To see errors stack, you may want to enable debug temporarily: Make sure APP_DEBUG is set to TRUE (APP_DEBUG=TRUE) in your app's .env file.

Note: Making the above-mentioned change means anyone with read access to your app can see those errors and perhaps get to know more than he/she should about your business logic/data.

Upvotes: 3

Malkhazi Dartsmelidze
Malkhazi Dartsmelidze

Reputation: 4992

Probably because your file/folder permissions

How to set up file permissions for Laravel?

sudo find /path/to/your/laravel/root/directory -type f -exec chmod 664 {} \;
sudo find /path/to/your/laravel/root/directory -type d -exec chmod 775 {} \;

For your cache directory:

sudo chmod -R ug+rwx storage bootstrap/cache

Upvotes: 1

Related Questions