Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

Gbever's avatar

Laravel Forge Deployment Reports Failed, but Succeeds

I have 2 sites that are virtually the same hosted on Digital Ocean with forge. Recently I ran into composer 2.0 issues that caused my deployments to spit out a bunch of warnings, along with upgrading the nexmo library which created duplicate classes.

Long story short, I resolved those issues and expected the messages to go away. When pushing to the staging site, I still get an email after each push letting me know my deployment failed, but the deployment does not fail and I dont see any warnings or issues.

The other identical site does not have this issue, pushing works as it usually does with no error.

Im a bit uneasy with always getting a message, if an error does occur I may not see it.

See the result of the email I get below. Any ideas?

Whoops!
We were unable to successfully deploy to your site: xxxxxx

Fri Feb 12 22:14:25 UTC 2021
From github.com:xxxxxx
 * branch            master     -> FETCH_HEAD
   42b0339..bf42a8e  master     -> origin/master
Updating 42b0339..bf42a8e
Fast-forward
 resources/views/pages/offshore-hiring.blade.php | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Package davejamesmiller/laravel-breadcrumbs is abandoned, you should avoid using it. No replacement was suggested.
Package fzaninotto/faker is abandoned, you should avoid using it. No replacement was suggested.
Package phpunit/php-token-stream is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
composer/package-versions-deprecated: Generating version class...
composer/package-versions-deprecated: ...done generating version class
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi
Discovered Package: [32malbertcht/invisible-recaptcha[39m
Discovered Package: [32mbarryvdh/laravel-debugbar[39m
Discovered Package: [32mbeyondcode/laravel-dump-server[39m
Discovered Package: [32mdavejamesmiller/laravel-breadcrumbs[39m
Discovered Package: [32mfacade/ignition[39m
Discovered Package: [32mfideloper/proxy[39m
Discovered Package: [32mfruitcake/laravel-cors[39m
Discovered Package: [32mintervention/image[39m
Discovered Package: [32mjeroenzwart/laravel-csv-seeder[39m
Discovered Package: [32mlaravel/cashier[39m
Discovered Package: [32mlaravel/nexmo-notification-channel[39m
Discovered Package: [32mlaravel/socialite[39m
Discovered Package: [32mlaravel/tinker[39m
Discovered Package: [32mlaravel/ui[39m
Discovered Package: [32mlaravelista/comments[39m
Discovered Package: [32mnesbot/carbon[39m
Discovered Package: [32mnexmo/laravel[39m
Discovered Package: [32mnunomaduro/collision[39m
Discovered Package: [32mspatie/laravel-honeypot[39m
[32mPackage manifest generated successfully.[39m
75 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
Nothing to migrate.
Application cache cleared!
Route cache cleared!
Route cache cleared!
Routes cached successfully!
Configuration cache cleared!
Configuration cache cleared!
Configuration cached successfully!
Application is already up.
0 likes
1 reply
Gbever's avatar
Gbever
OP
Best Answer
Level 1

Discovered that after my deployment failed, I had removed php artisan down as the server was already in maintenance mode. I never added that back, so calling the server back up without ever brining it down causes a failed deployment notice.

Please or to participate in this conversation.