Github Pages files give 404 >50% of the time

I have a Github Pages project site at https://github.com/liveahero-wiki/cdn/tree/gh-pages .

However, the files (especially the JSON files) give 404 errors most of the time. Yes, you hear me right, most of the time, but sometime it does return the file content.

PNG files seem to have higher probability of returning successfully: like https://liveahero-wiki.github.io/cdn/Texture2D/fg_rakta_h01_Atlas0.png

JSON files fail most of the time, like https://liveahero-wiki.github.io/cdn/MonoBehaviour/fg_huckle_s01.json and https://liveahero-wiki.github.io/cdn/Monobehaviour/fg_mokdai_h01_skin1.json

It was deployed more than 10 hours ago, I don’t know how much longer should I wait if Github wants to call it a caching issue.

Hi @rongjie-alter, welcome to the GitHub Support Community! I’m not seeing any issues with your Pages site on our side—everything seems to be normal so your pages site should be available.

It could be something to do with your local network, or the network route used to reach the Pages servers, that are causing the issue. Would you be able to give some more specific information on how exactly this is happening, on what devices, on what networks, and when?

An important note: I notice the name of this repository is cdn and it appears to be filled with image assets and configuration files. GitHub Pages is intended to be a free web host for static sites for personal and organization projects only. It is against the GitHub Pages terms of service to use Pages as a CDN. If you need a service to host assets for an external project then I’d recommend moving your project to a dedicated CDN or static file hosting service such as Azure Storage or AWS S3. If you are using Pages as a CDN for an external project your repository may be disabled among other things.

The issue was sorted out the other day, sorry for not updating it here. Basically I used “Monobehaviour” instead of “MonoBehaviour” in the url, that was why it wasn’t working.

The project name /cdn may be misleading, they are static files that the org project site (https://github.com/liveahero-wiki/liveahero-wiki.github.io) will need.

The reason why we decouple it into a separate project is because putting them in org project make the Jekyll building slower (since our Github actions step will need to pull more files (directly commit into org project or as submodule)) and org project site (which is a game wiki) updates in a much faster pace (a few times a day) than these static files (about one or twice a month).

This does not count as violating Github’s ToS right?

Ah, good to hear you’ve figured it out already!

And thanks for the clarification! Yes, using it as a source for another site hosted on GitHub Pages should be fine. It’s only really an issue if you’re using it for an externally-hosted project like an app, browser extension, etc. :sweat_smile:

1 Like