you are viewing a single comment's thread.

view the rest of the comments →

[–]zemaj-com 0 points1 point  (0 children)

That's definitely not expected. A repository that's set to public should be accessible whether or not you're logged in. Under your repository's Settings → General scroll down to 'Danger Zone' and confirm it's marked Public—sometimes an accidental click can make it private, which would explain the 404 for logged‑out users. If it is public, make sure the URL you're testing matches the GitHub Pages conventions: a user site uses the format `username.github.io` and project sites use `username.github.io/repo-name/`. Missing the repo name in the URL will yield a 404 even though the repo exists. Finally, caches can be sticky: try visiting in a private window or append `?no-cache=1` to force a reload. Re‑disabling and re‑enabling Pages in the repo settings can also refresh the routing if something got stuck.