GitHub Pages Builds Fail

I’m trying to create a website using Github Pages. The website has been building fine in the past. Today I updated some of the html and the website wouldn’t build anymore. I tried reverting to the previous commit, but it wouldn’t build either. I read the troubleshooting page, to no avail. I don’t have any idea of what to do anymore, please help.

The error:

Your site is having problems building: Unable to build page. Please try again later.

My repository: 

Hello @carterchannui,

If you’re not using Jekyll to build your website, sometimes GitHub pages will mistake certain characters, specifically curly braces, as jekyll objects, tags, etc. causing your page build to fail. If you’re just using static HTML pages (which is what it looks like to me), the easiest and quickest fix would be to disable Jekyll processing, which can be done by creating a file named .nojekyll in the root of your pages repository.


Hi @sethclydesdale

If by static you mean without animations, I don’t believe my website is just static HTML. This is what the website looks like: Also, why has it just started failing? It wasn’t doing this before. 


By static, I meant a website that’s created with HTML (no back-end coding). This has a pretty good explanation. Anyway, checking your repo, I’m seeing errors like the one below.

The variable `{{a}` on line 50 in `materialize-admin-template/node_modules/balanced-match/` was not properly closed with `}}`.

I’m assuming it may be mistaken for Jekyll liquid code. If you’re not using Jekyll, I would suggest creating a file named  .nojekyll (it doesn’t need any contents) in the root of your repository to see if it resolves the errors. If you are using Jekyll, then handling the file in the error above should resolve the issue as well.


Thank you @sethclydesdale, creating the  .nojekyll file effectively worked. The website has updated and was built successfully. GitHub did send me an email that I would like understand:

The page build completed successfully, but returned the following warning for the `master` branch:

It looks like you're using GitHub Pages to distribute binary files. We strongly suggest that you use releases to ship projects on GitHub. Releases are GitHub's way of packaging and providing software to your users. You can think of it as a replacement to using downloads to provide software. We found the following file(s) which may be a good candidate for releases: materialize-admin-template/node_modules/gifsicle/vendor/gifsicle.exe, materialize-admin-template/node_modules/jpegtran-bin/vendor/jpegtran.exe, materialize-admin-template/node_modules/node-notifier/vendor/notifu/notifu.exe, materialize-admin-template/node_modules/node-notifier/vendor/notifu/notifu64.exe, materialize-admin-template/node_modules/node-notifier/vendor/snoreToast/SnoreToast.exe, and materialize-admin-template/node_modules/optipng-bin/vendor/optipng.exe. For more information, see

For information on troubleshooting Jekyll see:

If you have any questions you can contact us by replying to this email.

What does this mean? Is it telling me to switch to a different program? 

1 Like

Good to hear!

No, it’s more of a suggestion to keep large binary files (.exe, for example) to the releases section, since they can go towards the recommended 1GB limit for repositories. If the files are necessary for your website to function then you can keep them as is. If not, then you can always remove them to keep your repo’s size down.


The documentation of this feature is a bit missleading.  Is the .nojekyll file supposed to be in the root of the gh-pages branch, or in the root of the repository master branch?

If in the master branch, it seems to me that it should also be possiable to put it in the root of whereever the pages is served from.  But that is just my opinion :slight_smile:

I had that problim too, and this solution solved it … thanks alot

I had the same problem and was glad that the suggestion creating a .nojekyll file solved the problem and my site was successfully published.