I am trying to run my Ghost Droplet and made a few modifications to the config file to change the image storage system, but I’m getting a 502 Bad Gateway Error nginx/1.4.6 (Ubuntu) when I navigate to my IP address and when I run npm start via ssh method on my local terminal, it indicates that the local server is running. I’m confused as to where to start to debug this 502 Bad Gateway Error. What is possibly causing this to happen and what files should I look at?
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.
This question was answered by @BrookDO:
Hi Connord,
It looks like the section
production: { url: 'http://www.testsite.com',
is your culprit. When I tested my ghost install and changed to a URL that wasn’t resolving to the proper IP, I also got a 502. Try replacing that URL with either a URL that is pointed at your Droplet’s IP, or use the IP itself. Save, restart Ghost, and test again.
Hi Connord,
It looks like the section
is your culprit. When I tested my ghost install and changed to a URL that wasn’t resolving to the proper IP, I also got a 502. Try replacing that URL with either a URL that is pointed at your Droplet’s IP, or use the IP itself. Save, restart Ghost, and test again.
Hey @BrookDO
sudo service ghost status
returnsghost start/running, process 1755
. Here is my config file.Hi Connord,
Can you share what you changed in the config file? Also, what does
sudo service ghost status
return?