My profile and gists are returning a 404 when shared #180770
Replies: 4 comments
-
|
👋 Welcome to the GitHub Community, @salidaespinoza88-cmd! Congratulations on your first post! 🎉 You are more likely to get a useful response if you are posting your question(s) in the applicable category. Check out this Guide on how to post in the right category. It'll ensure your questions and discussions reach the right people faster! This particular discussion belongs in the |
Beta Was this translation helpful? Give feedback.
-
|
Hi and welcome to GitHub! 👋 A 404 on a public gist usually means that something about the URL or visibility is off, not that you did anything wrong. Here are a few things you can check:
If you share a link like: https://gist.github.com/salidaespinoza88-cmd that’s only your gist profile page. Instead, open the specific gist and share the URL that looks like: https://gist.github.com/salidaespinoza88-cmd/xxxxxxxxxxxxxxxxxxxx (there should be a long ID at the end)
Open the gist and look in the top-right area: It should say Public If it’s a secret gist or you’re logged in while viewing it, it might look fine for you but still not be accessible in the way you expect. You can also try creating a brand new test gist with a simple file (for example test.txt) and set it to Public, then share that link.
If your GitHub account is very new or your email isn’t verified yet, sometimes content can be limited until you finish setup. You can check this under: Settings → Emails → Verify Once your email is verified and your account is fully active, public content should be visible to others. If you’re comfortable sharing one example gist URL, people here can test it and tell you exactly what they see on their side. That will make it much easier to pinpoint what’s going on. |
Beta Was this translation helpful? Give feedback.
-
|
If your public gists are returning a 404 to other people, here are the most common causes and how to fix them: ✅ 1. Make sure you’re sharing the correct URLA public gist should look like: ✅ 2. Confirm that the gist is actually Public, not SecretOpen the gist → look at the top-right corner. ✅ 3. Check if you’re sharing a forked gistIf you forked someone else’s gist and then deleted your own fork, the link you shared may no longer exist. ✅ 4. Make sure the account or gist wasn’t deleted or renamedIf you recently renamed your GitHub username, old gist URLs may break. ✅ 5. Try opening the link in an incognito/private browser windowIf you can open it but others can’t, this test will show whether the gist is actually public. If none of that works… Post one of the failing gist URLs (if you’re comfortable sharing it), and people can help verify whether the link itself is valid. |
Beta Was this translation helpful? Give feedback.
-
Why Your Public Gists Might Be Showing 404It’s likely that your gists are not actually visible to the public even though they appear “public” to you. Here are the most common causes and how to fix them: 1. Make sure the link is correctA valid public gist URL must look like this: 2. The gist might actually be secretSecret gists look normal when you’re logged in, but they are invisible to everyone else. GitHub also does not allow turning a secret gist into a public one. Fix: 3. Test while logged outOpen the gist link in an incognito/private window. 4. If you changed your GitHub usernameOld links that contain your previous username will stop working. 5. If none of this helpsContact GitHub Support and include:
They can confirm if there is an account or visibility issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am completely new to github, I hope this is the right place to ask for help.
I am trying to share my gists, but when people view them, they say they get a 404. even tho they are set to public.
I do not know what to do to allow people to see them
Beta Was this translation helpful? Give feedback.
All reactions