Question

502 Bad Gateway after Ghost restart

Posted December 15, 2014 14.6k views

I’ve recently been playing around with Ghost as a possible blogging platform and attempted to install a theme I found. I put the files into the ghost/content/themes folder and extracted the zip (that all went just fine). I then went to restart ghost as is suggested on the guide I was following and I’m now getting a 502 error from nginx.

See http://elliotblackburn.com/

The only command I tried to restart with was sudo service ghost restart.

I then found https://www.digitalocean.com/community/questions/502-bad-gateway-after-ghost-upgrade?comment=24356 and attempted to do the same but to nginx and it said it restarted just fine but I’m still getting a 502 error.

Here is a copy of my /var/log/nginx/error.log - http://pastebin.com/TLNHP5VU

Add a comment
BlueHat
By:
BlueHat
Add a comment
1 comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
4 answers
arunprasadr July 5, 2019

I ran into the same problem after upgrading ghost.

Make sure the port number configured in your ghost’s config file and the proxy_pass in your ghost site’s nginx configuration files match.

Check the port number in
/var/www/ghost/config.production.json matches the proxy_pass port in the nginx config files. 

/var/www/ghost/system/files/<yourDomainName>.<extension>.conf
/var/www/ghost/system/files/<yourDomainName>.<extension>-ssl.conf

In my case I had to change 2368 to 2369 in the nginx config files to fix the issue.

Make sure you restart your ghost and nginx after you make the changes.

# restart your ghost site
cd /var/www/ghost/
ghost restart 
# restart nginx
sudo systemctl restart nginx

Hope this helps someone.

Reply Report
  • oolism August 14, 2019

    Thanks so much @arunprasadr,

    These things are strange as today after a maintenance restart i got the Bad Gateway but your were totally right on the fix, changed the ports from 2368 to 2369 for the proxy upstream in my .conf files, restarted Ghost and Nginx and all is well :)

    Thanks my friend!

    Reply Report
  • talnacisergiu September 29, 2019

    Thanks a lot, I had the same problem, and the fix worked great.

    I think the breaking part is, once we start up ghost, in the command line it suggested I run an update, which probably ended up with the miss match in the port numbers.

    Reply Report
aguilar1181 December 16, 2014

Hi,

By looking at your error.log it looks like you might have a looping problem and haven’t configure your blog url. Open config.js in your root directory and enter your domain name instead of my-ghost-blog.com

I would also restart nginx and ghost after that.

Reply Report
  • BlueHat December 16, 2014

    Hi aguilar1181, thanks for your answer. But sadly I’ve already done that when I first set everything up. My production url is set to ’http://www.elliotblackburn.com’.

    Any other ideas would be much appreciated!

    Reply Report
  • aguilar1181 December 16, 2014

    I think I might have a solution. Try this to restart ghost

    npm start --production

    People have complaint that using this code to restart it always give them that 502 error and more specifically the complaint was use on another forum and they said it was in a DO server

    sudo service ghost restart
    Reply Report
  • asb December 16, 2014

    @aguilar1181 That’s exactly what the Upstart script should be doing when you run
    sudo service ghost restart 

    description "Ghost: Just a blogging platform"

start on (local-filesystems and net-device-up IFACE=eth0)
stop on runlevel [!12345]

# If the process quits unexpectedly trigger a respawn
respawn

setuid ghost
setgid ghost
env NODE_ENV=production
chdir /var/www/ghost

exec /usr/local/bin/npm start --production

pre-stop exec /usr/local/bin/npm stop --production

    Though running it directly might show us what’s going on here. I’d also check the contents of /var/log/upstart/ghost.log

    Reply Report
shaunik September 23, 2015

I am getting similar error after ghost restart and log file suggest:
verbose stack Error: ENOENT, open ’/var/www/package.json’
this persist after cache clean.

Reply Report
aguilar1181 December 16, 2014
[deleted]
Reply Report
Stat1k August 13, 2016

I know it’s an old thread and I apologize for reviving but this thread just helped me get my ghost app back up and running after restoring a failed upgrade attempt. I’d like to point out that you should “cd” to your ghost installation folder before running npm –start production.. like this:

cd /var/www/ghost

This is an example of the ghost installation folder, YMMV.

After CD'ing to it, run the following:

npm start --production
Reply Report
diversityboxonl January 5, 2017
[deleted]
Reply Report
Submit an Answer

Looking for something else?

Ask a new question Search for more help