Hi all, i have upload à software gnu unlicenced public licence on github but people who are trying tio acces have a 404 error not found

[RoyA1948]

Select Topic Area

Question

Body

Hi all, i have upload à software gnu unlicenced public licence on github but people who are trying tio acces have a 404 error not found

[Mykal-Steele]

the repository might be private, deleted, or the link you're sharing is incorrect.

[mecodeatlas]

Welcome to the GitHub Community, @RoyA1948, we're happy you're here! You are more likely to get a useful response if you are posting your question in the applicable category and are explicit about what your project entails--giving a few more details might help someone give you a nudge in the right direction. I've gone ahead and moved it for you. Good luck!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[bepoooe]

This 404 error typically happens for a few reasons:

Repository visibility settings: The repository might be set to private instead of public.
URL issues: There could be a typo in the URL being shared.
Repository deletion or rename: The repository might have been renamed or deleted.
Access permissions: Even in public repositories, specific access settings might be restricting visibility.

For the repository owner, I'd recommend checking:

The repository visibility settings under Settings > General > Danger Zone
That the correct URL is being shared
That the repository hasn't been accidentally deleted
Any branch protection rules that might be affecting access

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[UtkarshTrivedi2934]

Hi! A 404 error on GitHub when trying to access your repository usually means one of the following is happening:

🔍 Possible Reasons for 404

1. The Repository is Private
   If your repo is private, others won’t be able to access it, and they’ll see a 404.

Fix: Go to your repository settings → Under "Danger Zone" → Click "Change visibility" → Set it to Public.

2. The Repository URL is Wrong
   Double-check the URL you’re sharing. It should look like this:
   https://github.com/<your-username>/<repo-name>
   Visit it while logged out or in incognito mode to test if others can access it.

3. The Repository Doesn’t Exist (or Was Deleted/Renamed)
   If the repo was renamed or deleted recently, old links will show 404.

✅ What You Should Do
Log into GitHub and open the repository yourself.

Check if it says “Private” under the repo name.

If it’s private and you want to share it:

Change visibility to Public in repo settings.

If it’s public and still 404 for others:

Double-check the exact URL you're sharing.

Make sure the repo is not in a personal/private fork or an organization that restricts access.

ℹ️ Reminder About Licensing
If you're using the GNU Public License (GPL), make sure:

You’ve added a LICENSE file to your repo.

You’ve mentioned the license in the README.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬