All artisan commands bootstrap your project. If there is an error it may not be obvious but there should be a stack trace in your log file
Is there any chance you left a dump command somewhere?
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi, I've just upgraded my Laravel app from 5.4 to 5.5 using the Laravel Shift service, after running composer update no errors found, I run php artisan serve and it prints my config/session.php file contents in the console and then it prints the usual Laravel development server started: <http://127.0.0.1:8000>
Then when I go to my http://127.0.0.1:8000 I get the error RuntimeException Session store not set on request.
I notice that this happens with any artisan command I use, it always prints my session.php contents and then it executes the command, even the php artisan --version one
I've already cleared caches, sessions, routes and created a new encryption key.
Any help is appreciated.
It turned out to be a missing <?php in my config/session.php I think I deleted it when doing manual upgrades
Please or to participate in this conversation.