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

narayanwaraich's avatar

Laravel/Homestead : php7.0-fpm: unrecognized service

OS : Windows 10

After lots of small changes to get 'vagrant up to run', I'm again stuck on an error. Here is the error :

==> default: php7.0-fpm: unrecognized service The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.

0 likes
13 replies
06chaynes's avatar

i get this same error (although my error does not mention the version, i.e. default: php5-fpm: unrecognized service) after upgrading to homestead box version 0.4.0. Running on Mac OS X El Capitan. Homestead box version 0.3.3 was the last version I was running and it was working as expected.

TaylorOtwell's avatar

Sounds like you need to upgrade your actual Homestead installation. You only upgraded the box.

1 like
bashy's avatar

@06chaynes

Probably need all of this

cd ~/Homestead && git pull && vagrant destroy && vagrant box update && vagrant up

:)

8 likes
06chaynes's avatar

Ah makes perfect sense haha. I updated Homestead and the provisioning process completed successfully.

I did however have to remove the blackfire config options from the Homestead.yaml file. With the config in place I got the following error:

default: blackfire-agent: unrecognized service

Removing blackfire was not an issue for me but I thought I would add this as a note.

martinbean's avatar

I started getting this recently for some reason. Was resolved as soon as I updated the Homestead box from version 0.3.3 to 0.4.0, though.

luismec90's avatar

Hi @TaylorOtwell , I have installed the latest version (v0.4.0) but I am still getting this error, what am I missing?

==> default: blackfire-agent: unrecognized service
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Thanks in advance,

bluesail20's avatar

The answer provided by @bashy worked for me and got me rolling again. Much gratitude for including the code snippet. God bless Taylor's heart, but sometimes his answers lack the concreteness and specificity needed by many of us noobs. Just FYI, I also shared the answer here on StackOverflow since there seemed to be multiple posts there about this same problem.

rawfan's avatar

In case anyone else runs into the same problem I had:

~ vagrant box list
laravel/homestead (virtualbox, 0.2.7)
laravel/homestead (virtualbox, 0.3.0)
laravel/homestead (virtualbox, 3.0.0)

For whatever reason my latest box got a bad version number which resulted in no more updates. I just removed all boxes and added laravel/homestead back to get version v0.4.1.

Mattiman's avatar

What does this command mean?

cd ~/Homestead && git pull && vagrant destroy && vagrant box update && vagrant up

Is this an actual command or do I have to add something to this? I'm having the same problem as the original poster in this thread and I don't know what to do.

Zaheen's avatar

After running ~ vagrant box list, how can I delete old boxes? when I run vagrant box list, I can see all these boxes and do I need all them? laravel/homestead (virtualbox, 0.3.0) laravel/homestead (virtualbox, 0.3.3) laravel/homestead (virtualbox, 0.4.1) laravel/homestead (virtualbox, 0.4.4)

Thank you

Please or to participate in this conversation.