Article version: Enterprise Server 2.16

Page build failed: Invalid post date

If your GitHub Pages repository contains a post with an invalid date, your GitHub Pages site will not build.

If your GitHub Pages site fails to build because of a post with an invalid date in the filename, you'll get an email that looks like this:

Subject: Page build failed

The page build failed with the following error:

"The post `2012-02-30-time-is-an-illusion.md` does not have a valid date in the filename."

And if your GitHub Pages site fails to build because of a post with an invalid date in the YAML front matter, you'll get an email that looks like this:

Subject: Page build failed

The page build failed with the following error:

"The post `2012-02-30-time-is-an-illusion.md` does not have a valid date in the YAML front matter."

You will only receive an email if outbound email support is enabled on your Enterprise instance. For more information, contact your site administrator.

Troubleshooting post date errors

Tip: We strongly recommend running Jekyll locally so you can easily debug and fix build errors before pushing to your GitHub Enterprise Server instance. To learn more about troubleshooting options, see "Troubleshooting GitHub Pages builds."

Once you've fixed all post date errors, you will need to commit your changes and push to your GitHub Pages repository again to trigger another build on the server.

Ask a human

Can't find what you're looking for?

Contact us