GitHub Pages stopped working after renaming my HTML file

[resianej]

Hi everyone, I need some help with my GitHub Pages website and GitHub account.

My website was originally working normally on GitHub Pages. The problem started after I renamed my main HTML file from the old filename to a new filename in my repository.

After renaming the file, my website stopped working properly and eventually became unavailable. I have already tried:

Changing the GitHub Pages settings
Unpublishing and publishing GitHub Pages again
Checking the Actions tab
Trying to redeploy the website

However, the website is still not live, and I also cannot see the latest deployment history in the Actions tab.

Another issue is that my GitHub account does not appear when I search for it on GitHub, even though I can still log in to the account and access my repository.

GitHub Pages URL:
https://resianej.github.io/SilentPartyDjSON/

Could this be related to my account visibility, repository settings, or GitHub Pages deployment?

Does anyone know what might be causing these issues or what I should do to get my GitHub Pages website working again?

Thank you for any help!

[Armannss]

I checked the public repository and Pages site today (20 October 2026). The site still returns a 404, but main already contains an index.html file.

The strongest clue is in your latest listed Pages run, #32: the build was cancelled and its annotations say owner marked spammy. That points to an account-level restriction at the time of that build, rather than just an HTML filename problem. It may also relate to the search-visibility symptom you described, although I cannot confirm your account's current internal status.

Please contact GitHub Support and include that run URL, the exact annotation, your username, and the Pages URL. If you believe an account restriction was applied incorrectly, GitHub documents the review route here: GitHub Appeal and Reinstatement. Only GitHub can review that restriction.

Once Support confirms the account is clear, check Settings → Pages: if publishing from the current main branch, select the folder containing index.html (/ for its current location), then let a new Pages build and deployment complete. GitHub's 404 troubleshooting guide explains the entry-file location and filename requirements. If it still fails, share the new run link and its first error so the remaining deployment issue can be diagnosed.