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

curiosity's avatar

Envoyer setting current correctly - still using old version.

Hello,

I'm having a very bothersome problem where Envoyer is using the previous commit (this can be seen if looking at an error in the logs), or by looking at the page output. It is output of the old commit, but current is set correctly and contains the correct blade code.

This is in Laravel 5.5. Envoyer deploys with no errors. I fixed it previously by deleting the old referenced commit folder (in releases) it gets stuck on (you could keep deploying many times but it's still stuck), and then having to restart the entire server (otherwise, the app doesn't show the page, it shows multiple errors pointing to the nonexistent (old release) folder for Laravel vendor packages).

I tried composer dumpautoload php artisan config:clear php artisan cache:clear php artisan route:clear php artisan view:clear

But nothing. Now it's happening again, stuck on previous commit, though the current commit is correctly set as current.

Very confused as to how to fix this.

0 likes
1 reply
curiosity's avatar
curiosity
OP
Best Answer
Level 1

The solution to this problem was that the PHP version had not been updated in the Envoyer server's settings. Updating to 5.5 required updated PHP and with that, it was seemingly using the old PHP-FPM version.

1 like

Please or to participate in this conversation.