Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting 502 Bad Gateway #9

Closed
clebio opened this issue Dec 16, 2014 · 3 comments
Closed

Getting 502 Bad Gateway #9

clebio opened this issue Dec 16, 2014 · 3 comments
Assignees

Comments

@clebio
Copy link

clebio commented Dec 16, 2014

When I first load the project (http://192.168.4.2/), and whenever attempting to add one of the blocks from the left sidebar, I get a modal error:

Bad news, everybody!
502 Bad Gateway
nginx/1.4.6 (Ubuntu)

The README is sparse on details on getting this project set up and running, but I do at least get the vUp homepage to load and vagrant status tells me:

Current machine states:

vup                       running (virtualbox)
docker1                   running (virtualbox)

So I figure I'm on the right track.

Are there dependencies on my host machine that I need to add? I'm running OSX 10.8.5, vagrant 1.7.1

Thanks!

@twoflowers
Copy link
Owner

For some reason uWsgi does start correctly upon first boot. Do the following and you should be good to go:

vagrant ssh vup

sudo su

service uwsgi restart

That should fix the issue

@twoflowers twoflowers self-assigned this Dec 16, 2014
@clebio
Copy link
Author

clebio commented Dec 16, 2014

Confirmed that fixes it! Though now I get the -- almost existential -- Bad news, everybody! [object Object]. I'll keep digging. Feel free to close this issue. Thanks for the turn-around!

@clebio
Copy link
Author

clebio commented Dec 17, 2014

#10

@clebio clebio closed this as completed Dec 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants