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

nowhere's avatar

Error provisioning Custom VPS server on Laravel Forge

Hi, I'm trying to provision a Custom VPS server on Laravel Forge but it keeps failing at last step (Finishing UP)

The process does create forge user and install all services but then it ends saying "We were unable to finish provisioning your server (xxxxx). Please delete the server in the server provider's dashboard and re-create the server with the help of the debugging solutions provided by Forge."

I've already provisioned custom server as well as DigitalOcean server without issue

I just noticed that it doesn't add personal ssh key to authorized_keys and it returns an error about Redis-server failed to start

I've opened a support request but I'm still waiting for a reply

Did anybody face a similar situation?

Regards, Nowhere

0 likes
2 replies
luke___'s avatar

I'm just googling the same problem and came across this post.

I'm trying to create a custom VPS using Google Cloud VM and have the same problem.

Just waiting to here back from Forge support and wondering if you found a fix?

nowhere's avatar

Hi Luke, at the end it was a mix of closed ports and services not fully removed during reinstallation. First I was able to to finish installation opening ports 80 and 443 which were closed as server was behind a firewall not allowing that traffic (it was a development server so I thought it would be enough to have ssh port open for installation purpose ) . After that I noticed some errors during installation: to capture all the output of running the forge.sh script by redirecting it to forge.log, i.e. bash forge.sh > forge.log 2>&1. You can open a second terminal window, to login and tail -f forge.sh.

Logs told me that redis service was not installed correctly so i removed it manually and reinstalled it without any issue. Probably my bad was to keep trying to remove and reinstall all on the same server instead of creating a new one as support suggested me. It looked like disinstallation process wasn't able to clean old redis installation.

I hope it helps, Nowhere

Please or to participate in this conversation.