Vvv: Strange Error on vagrant up: nginx: [emerg] directive "set" is not terminated by ";" in /etc/nginx/custom-sites/...

Created on 20 Dec 2016  路  8Comments  路  Source: Varying-Vagrant-Vagrants/VVV

Greetings,

I am a new vagrant user. My apologies, I hope this is the place for me to ask a question.

I followed the instructions, got everything working. Was using it for a few days trying to get the hang of things. Well, today I decided to delete a site. I deleted the site and went to create a new one and I got an error on vagrant up.

Here is what i get in console...

https://gist.github.com/pierrerocket/9d2cc7e8829fa92c04662e68700dedc3

I tried my best to google around and figure this out, but I am stuck. Can anybody give any advice?

Kind Regards,

Most helpful comment

@pierrerocket @Seabastian This is due to you using the develop branch which is under very active development.

Please do a git pull on the VVV repo followed by a vagrant provision as there have been breaking changes in the last few days.

Then paste line 17 of www/wordpress-develop-provisioner/vvv-nginx.conf here for me.

All 8 comments

I had this issue today, the problem was that i didn't do vagrant halt on a computer restart.

Maybe you can try to run this at te folder where your vagrant is installed:
vagrant reload --provision

That did the trick for me.

@pierrerocket @Seabastian This is due to you using the develop branch which is under very active development.

Please do a git pull on the VVV repo followed by a vagrant provision as there have been breaking changes in the last few days.

Then paste line 17 of www/wordpress-develop-provisioner/vvv-nginx.conf here for me.

@LoreleiAurora Oke..

This is on line 15 of the file you asked about:

access_log /srv/log/wordpress-develop/src.access.log;

@Seabastian Sorry i got my line numbers wrong, i meant line 17.

That's :

set $upstream {upstream};

git pull and provision did the trick, thanks a ton @LoreleiAurora

@LoreleiAurora that did it for me, thanks a bunch!

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings