[URGENT SUPPORT NEEDED] Public repository returning 404 due to internal account/repository name confusion

[lemira]

Select Topic Area

Question

Body

Dear GitHub Community,

I am writing to report a critical issue with my public repository. Despite being set to "Public" visibility, the repository returns a 404 error for users who are not logged into GitHub. This prevents access to the README file and the "Issues" section, which is essential for my open-source project listed on the Joomla Extension Directory.

Repository Details:

Repository URL: https://github.com/lemira/com_kunenatopic2article

Current Visibility Setting: Public (as confirmed in Settings -> Danger Zone).

Default Branch: master

Description of the Problem: All direct links (e.g., to /blob/master/README.md or /issues) result in a 404 error for unauthenticated users. The main repository page is also inaccessible from a logged-out state. Logged-in users (myself) can access everything without issues.

Important Context on Account Selection:
I only have one GitHub account: my personal account lemira. I never created a separate organization named com_kunenatopic2article. This name is solely the name of my repository. However, when I attempt to contact support via the help form, the system incorrectly prompts me to choose between my personal account and a non-existent organization with the same name as the repository (com_kunenatopic2article). I believe this confusion on GitHub's side between my account name and the repository name is the root cause of the visibility issue.

Steps I have already taken to resolve the issue:

I have confirmed multiple times that the repository visibility is set to "Public" in the Settings -> Danger Zone.

I have tried accessing the repo from different browsers and in incognito mode to rule out local caching. The 404 error is consistent and has persisted for weeks.

I created and committed an empty .refresh file to the master branch via the GitHub web interface to trigger a repository state update. Waited over 1.5 hours with no change.

I confirmed that there are no enabled security restrictions (like interaction limits or geo-blocking) that could cause this.

Discovered account confusion: The support form incorrectly lists my repository's name as a separate organization account, which I never created. This strongly suggests an internal GitHub metadata or indexing error.

Request:
Could you please investigate and repair the internal association of the repository com_kunenatopic2article with my personal account lemira? The repository needs to be fully accessible to everyone without requiring a GitHub account.

Thank you for your time and assistance in resolving this blocking issue.

Best regards,
Leon
GitHub Username: lemira

[Paraschamoli]

Hi! The 404 is happening because GitHub is confusing your repository name with an organization name. Even though your repo is public, this internal metadata issue makes it inaccessible to logged-out users.

To fix it, you’ll need GitHub Support to correct the association between your repository com_kunenatopic2article and your personal account lemira. Make sure to explain that there’s no organization with that name—just the repo.

Once GitHub fixes it, your repository will be visible to everyone.

[lemira]

Issue resolved