502 Bad Gateway nginx/1.13.6

Hey all,

today I've done a vagrant reload with provision and after that I got a 502 Bad Gateway. I reverted my changes to the Homestead.yaml file, but after another provision I got the 502 Bad Gateway.

So ... turns out I ran a laravel/homestead box with version 3.1.0. I installed the latest box (5.2.0) and upgraded my virtualbox to 5.1, since 5.2 is not supported yet.

I rebooted my system. Did vagrant up with provision. This all went well without an error, but still I get the 502 Bad Gateway eventhough I haven't changed my config files. My Homestead.yaml looks like this:

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
provider: virtualbox

authorize: "c:/users/Dian Derksen/.ssh/id_rsa.pub"

keys:
    - "c:/users/Dian Derksen/.ssh/id_rsa"

folders:
    - map: c:/dev/html
      to: /home/vagrant/Code

sites:
    - map: finly.test
      to: /home/vagrant/Code/finly-next/public
    - map: phpmyadmin.test
      to: /home/vagrant/Code/phpmyadmin
    - map: consumer-join.test
      to: /home/vagrant/Code/finly-consumer-join-page
    - map: zalon.test
      to: /home/vagrant/Code/zalon/public  
    - map: moves.test
      to: /home/vagrant/Code/moves

databases:
    - homestead
    - homestead_outputeditor
    - homestead_zalon
    - moves2

My host file is referring to those domains correctly. I haven't touched it and were working for me already for months. It all started after I did a provision when I added 1 site (which is not there anymore).

Can anyone help me? I've searched by brains out, but without any result. Thanks!

I'm running on a Windows 10 Pro system.

ejdelmonico

8 years ago

Level 53

First off, virtualbox 5.2 is supported and works correctly with homestead box 5.2 on both Windows and Mac. So you upgraded the homestead box and ran vagrant provision give you? What error message did vagrant provision give you? If you can't get vagrant to run the box then do a vagrant box remove on that current box and run vagrant up again. That will work for sure and it obviously doesn't affect your projects.

Please or to participate in this conversation.