Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Because even paid plans in Forge don't receive replies from the support when there are problems with their PAID service I have to ask here.
Everything was working perfectly with my Laravel Forge deployment and after some updates in the Forge I was starting to receive this error after every deployment:
....................... deploy files successful DIR/.forge/provision-15538164.sh: line 48: /tmp/fpmlock: Permission denied .......................... my post-deployment scripts never run because of this error
I tried to change the folder owner to root, forge, etc., without any success. The only way is for this folder to be sent to the project owner, but I have many projects and they all try to write in this lock file.
The problem is the same even for newly installed servers via Forge.
So since there is no support, how I can fix this problem?
Hey Marty, I've checked around this forum a bit for a similar issue and a common resolution is the following: https://forge.laravel.com/docs/accounts/cookbook.html#forge-is-unable-to-access-git-repository
https://laracasts.com/discuss/channels/forge/laravel-forge-touch-cannot-touch-libfpmlock-permission-denied
@ricovzelst Nop I dont have problems with git, as I wrote in my question, my files are successfully deployed on the server the problem comes after the files are deployed
Please or to participate in this conversation.