Ghost Blog Upgrade Issues


Ghost Blog

I have ghost blog upgrade issues every single time I upgrade.  I can’t say that I am repeating the same mistakes over and over because I am not.  I can generalize and say when ghost blog was released my problems leaned toward permission issues.  I have those straighten out now but I still seem to continue to have issues.

Today I was upgrading from Ghost 0.7.0 to Ghost 0.7.8.  My issues was a version NPM that was extremely old, I missed copying over some json files and I had to run npm-install –production multiple times.

It’s back up and I understand they are not even at 1.0 yet but I wish the upgrade process could be smoother.  I am extremely comfortable with Linux and use it on a daily basis but for some reason I can’t ever get it work on the first try.

I also see that they removed the forums.  I’m all for change and making things easier but I can’t use google to find my answer.  I will have to read up on why they decided to make the change.

Received an Email from Ghost Blog Today saying I am in

Updated: I was confused and for a good reason.  Finally logged in and it said they sent the wrong email and that beta testing is over.  Which makes sense but what do I know.  In either event I will eagerly look forward to updates to the self-hosted platform.  That’s what I really am interested in.

I received this from Ghost Blog today:

Hey buecker,

Boom! You’re in. We’re rolling out beta (actually, alpha) access of the new Ghost Hosted Platform to a few select Kickstarter backers, and you’re one of them.

Let’s not beat around the bush about this: We’re calling this alpha for a reason. We don’t know if things might explode (it’s possible) – but we very much hope that following a couple of weeks of rigorous testing, we’ll start to be able to call it beta… then stable.

Most importantly – we need your help for this! The alpha/beta preview is completely free of charge and without restrictions. If you have time, please set up a blog or two and let us know how you get on. If you run into any problems with the hosted platform, drop us a line on [email protected].

Have fun, and try to break stuff!

Looks like the changes haven’t been made yet because it is all grayed out.  I don’t remember being a kickstarter backer either but I am active on the forums.  I also have my ghost blog setup at  I look forward to the day of replacing some of my wordpress installs.

Ghost Blog giving me node.js errors in Production


Ghost Blog has been giving me lots of node.js errors and page cannot be display errors.  I should have tracked the hours of testing but it was way too many hours devoted to a beta platform.  I have finally solved my issue and have a lot more than I would have if I had not gone through this exercise.

As I mentioned above I was getting a Page Cannot Be Displayed error.  This is when I actually got ghost to start.  When I couldn’t get ghost to start I was getting Node.js errors.  I think error 72 was the most popular.  Basically the problem was that ghost wouldn’t run on the ports I was picking.

The final result is that I got it fixed by editing the config.js file.  In the production section I needed to change the server IP and port numbers.  The server IP ended up being my local IP (192,168.x.x) and the port is port 80.  Originally it listed it as  This worked the first time and I am unsure why it didn’t work the second time or thereafter.

I am going to start from the beginning with a little background on my server.  This is a small atom server running Ubuntu 13.10 sitting on my local network. It’s used for a few things. I have a static IP and a domain name assigned.  The domain name is  I have it setup this way because points to my EC2 server.

It originally had a LAMP setup but I uninstalled Apache and installed nginx for this project.  I followed instructions located at Gregg Housh’s blog.  The first time I ran through his instructions I ran into a 502 gateway issue.  Starting npm with Sudo fixed that issue.  Ofcourse, when I had a server reboot I couldn’t get ghost to run at all.

I thought my issue was related to a syntax error in config.js.  I am still not sure what happened because no where on the web do I see that I was suppose to change the IP to the local IP address.  I tried my static IP and the domain name.  Neither of them worked for me.

My node.js errors meant that something else was running on the ports I was trying to use.  When I checked the list of ports in use it didn’t say that.  I think even uninstalled nginx and node.js a few times.

I have learned a lot from this experience and while it was more time than I should have spent on it I am glad I went through this exercise.  I wanted to use another blog platform to write about other things that aren’t tech.