Server timezone causing post dates to be incorrect

[juniorRubyist]

Last night, I published something on my Ghost-powered blog, and I noticed the published time was 14 hours off. (My timezone is America/Los_Angeles, which is UTC-7:00/8:00.) I knew it had something to do with the timezone, but I couldn’t tell what was wrong. I first thought it had to do with my MySQL timezone, and so I manually set that to UTC, which then made the publish times only 7 hours off. I then realized that perhaps the date that Ghost was using to calculate the local time was not UTC, rather it was my local time (the server’s time zone), and it was converting the already local time to “local time.” So, I then tried setting my server timezone to UTC, which fixed the problem.

It would be nice if this was mentioned in the docs.

[Kevin]

@juniorRubyist are you on Ghost 3.19.0? If so that release has a timezone bug that matches exactly what you describe and I suggest upgrading

[juniorRubyist]

Ahhhh. That explains things. I’ll go ahead and do that. Thanks!

[Hannah]

This is also a duplicate of:

Ghost adding 12 hours to publish date

Hi all, I have a strange corner case which I haven’t encountered before. I have ghost installed in a docker installed on my unraid box, which is then connected to via a reverse proxy. Every time I schedule a post, it adds twelve hours to the scheduled time. So 7:00 becomes 17:00, etc. If I try to reschedule it from the time it gets adjusted to, it adds another twelve hours - so 17:00 becomes 03:00 the next day. It becomes a loop. I can see for a split second it sets the time and date correctl…

Any further discussion needed can go on the original.