Getting a 502 Bad Gateway message after reboot.

November 2, 2013 12k views
skumailrizvi
By:
skumailrizvi
After installing some new themes on a Ghost droplet, rebooting it, I get a 502 Bad Gateway message. I didn't change any other settings as far as I'm aware but I'm told this has something to do with my nginx configuration? Does anyone have any ideas on how I can fix this?
1 comment
Log In to Comment
10 Answers
pablo November 2, 2013
Check the owner:group attributes. What's the output of ls -la /path/to/Ghost/directory/? If you see root:root sprinkled in there, execute sudo chown -R www-data:www-data /path/to/Ghost/directory/.
Reply
skumailrizvi November 2, 2013
I did see root:root there, executed the command, restarted ghost but still no joy.
Reply
pablo November 2, 2013
Restart Nginx: sudo service nginx restart
Reply
roa November 2, 2013
Firts , verify your permissions in your documenroot of nginx


Which users running nginx ? nginx or apache


And verify the logs of /var/log/nginx
Reply
skumailrizvi November 3, 2013
how can I do that exactly? Sorry, I'm just new to a lot of this.
Reply
roa November 3, 2013
verify wich user running nginx

cat /etc/nginx/nginx.conf | grep user
user nginx;

and check your permission of document root chown -R nginx:nginx /var/www/site
Reply
kamaln7 MOD November 3, 2013
It means that ghost is down. Try starting ghost: 

sudo service ghost start
Reply
kpennell May 12, 2014
@Kamal, what if that gives me "ghost: unrecognized service"?

What does that mean?
Reply
kpennell May 12, 2014
npm start start Ghost but it's an unrecognized service.
Reply
superhero October 3, 2014
[deleted]
Reply
Have another answer? Share your knowledge.