Level 102
How about laravel.log in the storage directory?
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
When I access one of the pages of my deployed site I get an internal server error. Nothing appears in my Laravel Forge deployment log to suggest something is wrong:
Thu Feb 13 17:46:39 UTC 2020
From github.com:greevesh/single_product_store
* branch master -> FETCH_HEAD
Already up to date.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi
Discovered Package: [32mbarryvdh/laravel-debugbar[39m
Discovered Package: [32mcartalyst/stripe-laravel[39m
Discovered Package: [32mfacade/ignition[39m
Discovered Package: [32mfideloper/proxy[39m
Discovered Package: [32mhardevine/shoppingcart[39m
Discovered Package: [32mlaravel/tinker[39m
Discovered Package: [32mlaravel/ui[39m
Discovered Package: [32mnesbot/carbon[39m
Discovered Package: [32mnunomaduro/collision[39m
Discovered Package: [32msven/artisan-view[39m
[32mPackage manifest generated successfully.[39m
Restarting FPM...
Nothing to migrate.
I've checked all the nginx log files and there were no reported errors there either. I followed this tutorial perfectly as well: https://laracasts.com/series/learn-laravel-forge/episodes/3
Why on earth am I having this problem?
How about laravel.log in the storage directory?
Please or to participate in this conversation.