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

dylanh's avatar

Composer not found on new Forge server

I've been trying to deploy a new server through Forge on DO. I've done this a dozen times before and never had this issue before.

When trying to deploy the code, I get an error saying

"/home/forge/.forge/provision-5556824.sh: line 29: composer: command not found"

If I ssh into the server and run "composer -v" I get "The program 'composer' is currently not installed. You can install it by typing:"

Is anyone else having issues deploying new servers this afternoon? Pretty sure it worked fine this morning!

0 likes
14 replies
dylanh's avatar

Thanks @tomo_pongrac .

Any idea why this has suddenly changed? I've deployed more than a dozen servers before and never had to worry about it.

One of the beauties of Forge was that you didn't need to worry about things like dependencies unless you were really going off the path of best practices.

dylanh's avatar

Thanks, I've mailed Taylor. Maybe he can clear this up.

dylanh's avatar

Taylor just responded with

"It's a DigitalOcean issue. I've reported it to them."

Will update here if I hear anything further.

2 likes
dylanh's avatar

Just in case anyone else is trying to get a fix for this, I've managed to go 2 steps backwards:

The sudo password that forge mails you is incorrect and doesn't work, so you're not able to manually install composer and other dependencies.

From what I've gathered it seems the DO delay in processing events has caused the server to deploy without the follow up events of installing/updating/setting up being executed. Basically causing forge and DO to be out of sync with the real status of your server.

Thinking it may be time to add another cloud provider onto my forge account.

:(

maisnamraju's avatar

So do I spin up a new server or install the repo as usual ?

ryanebbers's avatar

DigitalOcean is reporting that the mirror issues were fixed, so I just tried to spin up a new server via Forge. Got that update from Laravel's Twitter page.

Still receiving the same error 'composer: command not found' when trying to setup quick deploy from my GitHub repository.

Hopefully this is fixed soon.

https://twitter.com/laravelphp

maisnamraju's avatar

@ryanebbers Saw your post earlier and did the same and ran into the same will. Looks like this will have to wait till tomorrow.

dylanh's avatar

Took me all of 5 minutes to add my AWS credentials to forge.

I'll jump ship to Amazon until DO sorts this out. (Still prefer DO but I really need to get this server running already!)

I understand things fall down sometimes, but that's what a status page is for. P*sses me off that they claim everything is fine when things are clearly not working somewhere.

dylanh's avatar

Oh, and AWS instance is flying. So its clearly an issue limited to DO through Forge not a general forge issue.

ryanebbers's avatar

@maisnamraju keeping my fingers crossed it is able to get resolved this afternoon.

@dylanh thanks for the update about AWS still working with Forge. I also need to get a server up and running ASAP, so probably going to follow in your footsteps in the meantime. Definitely prefer DigitalOcean also, but things happen.

1 like
dylanh's avatar

Just FYI, this morning I've managed to boot up a new DO droplet through forge. All seems to be working well so far.

Hopefully this issue is sorted now.

1 like

Please or to participate in this conversation.