GitHub README stats images not showing

[minirang]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Markdown

Body

The problem like this picture:

Description:

Hi, the GitHub Stats image in my profile README suddenly stopped showing up.
I did update my README earlier today, but I did not modify or remove the GitHub Stats section.
It was working fine before, and I haven’t made any changes specifically to the GitHub Stats configuration.
The image is embedded using an external GitHub Stats service, but it no longer appears on my profile. And I am using the standard markdown format: ![GitHub stats](https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true), and it was correctly added, but now it does not appear.
Could you please check if this is a bug?

System Information:

OS: Windows 11 Pro 64-bit
System Model: LENOVO_MT_81SX_BU (Legion Y540-15IRH)
Browser: Chrome 146.0.7680.81 (64-bit, official build)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[itxashancode]

Why the GitHub‑Stats image may disappear from your profile README

The markdown you’re using

![GitHub stats](https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true)

is valid, but several things can stop the image from rendering after it has been working for a while.

---

1. Verify the image URL directly

1. Open the URL in a new tab:

   https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true

2. What you should see:

   • An SVG (or PNG if you added &hide_bg=true) that loads instantly.
   • HTTP status 200 and a Content-Type: image/svg+xml header.

If you get a 403, 429, 500, or the browser downloads a file instead of displaying an image, the problem is on the stats service side (see § 2‑4).

---

2. Common service‑side issues

Symptom	Likely cause	Fix / workaround
429 Too Many Requests	The Vercel endpoint enforces a per‑IP rate limit (≈100 req/h).	Add a cache‑busting query param (&cache_seconds=86400) or wait for the limit to reset.
403 Forbidden	The service blocked the request (e.g., IP reputation, bot detection).	Try from a different network or use a VPN; alternatively, host your own stats (see § 5).
500 Internal Server Error	Temporary outage on vercel.app.	Check the service status page (https://vercel.com/status) or wait a few minutes.
Image returns HTML/Text	You accidentally used http:// instead of https:// (mixed‑content block) or the URL is malformed.	Ensure the URL starts with https://.

Quick test:

curl -I "https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true"

Look for HTTP/2 200 and content-type: image/svg+xml.

---

3. GitHub‑specific caching & rendering quirks

• GitHub caches the rendered README for a few minutes. After you edit the file, the old image may still be shown until the cache expires.

• A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) forces the browser to bypass its own cache, but GitHub’s server‑side cache still applies.

• Adding a dummy query string that changes each time you push (e.g., a timestamp) forces GitHub to fetch a fresh copy:

  ![GitHub stats](https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true&v=2025-09-24T12:00:00Z)

  You can automate this with a CI workflow that updates the README on each push, but for a manual fix just edit the timestamp and commit.

---

4. Mixed‑content / HTTPS enforcement

If your README is rendered over https://github.com (which it always is) and the image URL is http://, GitHub will block the request as mixed content.
Fix: Ensure the URL begins with https://.

---

5. Long‑term, self‑hosted alternative (optional but reliable)

If you hit rate limits repeatedly or want zero‑dependency images, generate the stats yourself with a GitHub Action and commit the SVG to your repo.

Example workflow (.github/workflows/stats.yml):

name: Update GitHub‑Stats SVG
on:
  schedule:
    - cron: '0 * * * *'   # hourly
  workflow_dispatch:

jobs:
  stats:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false   # needed for push
      - name: Generate stats SVG
        run: |
          curl -s "https://github-readme-stats.vercel.app/api?username=${{ github.actor }}&show_icons=true&theme=dark" > stats.svg
      - name: Commit & push if changed
        run: |
          git config user.name "github-actions[bot]"
          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git add stats.svg
          git diff --quiet && git diff --staged --quiet || (git commit -m "Update stats SVG" && git push)

Then reference the file directly in your README:

![GitHub stats](stats.svg)

Because the image lives in the same repository, GitHub never blocks it and you avoid external rate limits.

---

6. Checklist to get the image back

1. Open the raw URL → confirm it returns an SVG with status 200.
2. Force HTTPS if you ever used http://.
3. Add a cache‑busting query (&v=<timestamp>) and commit the change to your README.
4. Hard‑refresh the profile page (Ctrl+Shift+R).
5. If step 1 fails, wait a few minutes or switch to a different network; if it persists, consider the self‑hosted Action approach.

---

References

• GitHub Docs – About profile READMEs: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
• GitHub Docs – Troubleshooting missing images: https://docs.github.com/en/get-started/quickstart/troubleshooting-common-issues#images-don-t-appear
• Vercel GitHub‑Readme‑Stats rate limits: https://github.com/anuraghazra/github-readme-stats#api-endpoint (see “Rate limiting” section)
• GitHub Actions – Creating a workflow: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions

Follow the steps above and the stats image should reappear in your profile README. If you still see a blank after verifying the URL returns a valid SVG, let me know the exact HTTP status and response headers you observe—those details will help pinpoint any remaining issue. Happy coding!

[minirang]

Why the GitHub‑Stats image may disappear from your profile README

The markdown you’re using

![GitHub stats](https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true)

is valid, but several things can stop the image from rendering after it has been working for a while.

---

1. Verify the image URL directly

1. Open the URL in a new tab:

   https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true

2. What you should see:

   • An SVG (or PNG if you added &hide_bg=true) that loads instantly.
   • HTTP status 200 and a Content-Type: image/svg+xml header.

If you get a 403, 429, 500, or the browser downloads a file instead of displaying an image, the problem is on the stats service side (see § 2‑4).

---

2. Common service‑side issues

Symptom	Likely cause	Fix / workaround
429 Too Many Requests	The Vercel endpoint enforces a per‑IP rate limit (≈100 req/h).	Add a cache‑busting query param (&cache_seconds=86400) or wait for the limit to reset.
403 Forbidden	The service blocked the request (e.g., IP reputation, bot detection).	Try from a different network or use a VPN; alternatively, host your own stats (see § 5).
500 Internal Server Error	Temporary outage on vercel.app.	Check the service status page (https://vercel.com/status) or wait a few minutes.
Image returns HTML/Text	You accidentally used http:// instead of https:// (mixed‑content block) or the URL is malformed.	Ensure the URL starts with https://.

Quick test:

curl -I "https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true"

Look for HTTP/2 200 and content-type: image/svg+xml.

---

3. GitHub‑specific caching & rendering quirks

• GitHub caches the rendered README for a few minutes. After you edit the file, the old image may still be shown until the cache expires.

• A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) forces the browser to bypass its own cache, but GitHub’s server‑side cache still applies.

• Adding a dummy query string that changes each time you push (e.g., a timestamp) forces GitHub to fetch a fresh copy:

  ![GitHub stats](https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true&v=2025-09-24T12:00:00Z)

  You can automate this with a CI workflow that updates the README on each push, but for a manual fix just edit the timestamp and commit.

---

4. Mixed‑content / HTTPS enforcement

If your README is rendered over https://github.com (which it always is) and the image URL is http://, GitHub will block the request as mixed content.
Fix: Ensure the URL begins with https://.

---

5. Long‑term, self‑hosted alternative (optional but reliable)

If you hit rate limits repeatedly or want zero‑dependency images, generate the stats yourself with a GitHub Action and commit the SVG to your repo.

Example workflow (.github/workflows/stats.yml):

name: Update GitHub‑Stats SVG
on:
  schedule:
    - cron: '0 * * * *'   # hourly
  workflow_dispatch:

jobs:
  stats:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          persist-credentials: false   # needed for push
      - name: Generate stats SVG
        run: |
          curl -s "https://github-readme-stats.vercel.app/api?username=${{ github.actor }}&show_icons=true&theme=dark" > stats.svg
      - name: Commit & push if changed
        run: |
          git config user.name "github-actions[bot]"
          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git add stats.svg
          git diff --quiet && git diff --staged --quiet || (git commit -m "Update stats SVG" && git push)

Then reference the file directly in your README:

![GitHub stats](stats.svg)

Because the image lives in the same repository, GitHub never blocks it and you avoid external rate limits.

---

6. Checklist to get the image back

1. Open the raw URL → confirm it returns an SVG with status 200.
2. Force HTTPS if you ever used http://.
3. Add a cache‑busting query (&v=<timestamp>) and commit the change to your README.
4. Hard‑refresh the profile page (Ctrl+Shift+R).
5. If step 1 fails, wait a few minutes or switch to a different network; if it persists, consider the self‑hosted Action approach.

---

References

• GitHub Docs – About profile READMEs: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
• GitHub Docs – Troubleshooting missing images: https://docs.github.com/en/get-started/quickstart/troubleshooting-common-issues#images-don-t-appear
• Vercel GitHub‑Readme‑Stats rate limits: https://github.com/anuraghazra/github-readme-stats#api-endpoint (see “Rate limiting” section)
• GitHub Actions – Creating a workflow: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions

Follow the steps above and the stats image should reappear in your profile README. If you still see a blank after verifying the URL returns a valid SVG, let me know the exact HTTP status and response headers you observe—those details will help pinpoint any remaining issue. Happy coding!

Oh I entered https://github-readme-stats.vercel.app/api?username=minirang&show_icons=true and I saw 503 SERVICE_UNVAILABLE 😭
It shows that the site deployment is paused by the owner. Thank you for answering! (The sentence's grammar may be strange because I am learning English.)