Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
After I create my droplet and the server is installed/provisioned, I can visit the ip address and see the php info page, but once I install any repository I get the dreaded "whoops, looks like something went wrong page" shows up. I've even tried to simply install the github laravel/laravel repository and I'm still getting the same issue. I've tried removing the php artisan migrate command from the deploy script to prevent any .env issues but still not working.
I can even ssh into the server and see Laravel is installed properly. I've followed this laracast video step by step https://laracasts.com/series/server-management-with-forge/episodes/3, and still can't seem to get the 4:00 mark where you can see the fresh install of Laravel. Any help would be greatly appreciated.
is there a .env file? You said it was installed properly, but sometimes it isn't 100%. If there isn't you will need to create one. touch .env, then open it and copy your settings in there.
Also, if there is a .env file, you might also look inside it and make sure an encryption keys is set. If one is not set, close the file and run php artisan key:generate
That is where I would start
Yup more then likely env or database issue. But env has the db info.
Add 'APP_DEBUG=true' to your .env - It will at the very least tell you what 'whoops...' is referencing.
I turned debug environment variable on to true and my Pages controller was giving a "view finder" error. Apparently it was looking for 'pages.home' when my repository had "Pages.home". I guess the local environment isn't case sensitive whereas production, it is?
In any case, I was able to solve the issue. Thank you all for the help.
Please or to participate in this conversation.