Internal Error 500: Hosting our latest Laravel 5.1 site on good working Vagrant/Homestead environment
Configuration Development system
- Laravel 5.1
- Good working Vagrant/homestead on windows 10.
- V1 Production Laravel site working on Vagrant/homestead (non-responsive)
- V2 production Laravel NOT working on Vagrant/homestead (responsive)
The Steps to narrow the problem:
Part 1 – The basics
- Import SQL file with PhpMyAdmin
- I have added or changed all the necessary steps (URL, homestead.yaml, hostfile ect)
- I have a Working fresh Laravel 5.1 installation
Part – 2 The Migration
- Imported a new database with phpMyAdmin
- Removed the fresh installation
- Copy the new “production environment”
- Changed the .env file with the required database information
- Load site and BAM an Laravel error “Houston we have got a problem Internal 500 message”
Part – 3 Done so far fixing the problem
- Artisan clear cache will make it worse
- Removed everything and installed a fresh 5.1 Laravel environment
- Copy the folders 1 by one and when I copy the APP directory it will result in an “Internal error 500”
Part – 4 Conclusion
We have a good working vagrant/homestead environment and it goes wrong when I am migrating the new production site to this configuration. The difference between V1 and V2 is that V1 (working on vagrant/homestead) is a non-responsive site and V2 is the same site but completely responsive.
Any tips on how to solve this issue
from Laravel Questions and Answers https://laravelquestions.com/php/internal-error-500-hosting-our-latest-laravel-5-1-site-on-good-working-vagrant-homestead-environment/
via Lzo Media
No comments:
Post a Comment