GitHub Pages site not displaying

[rosebidzogoo-collab]

Select Topic Area

General

Body

Hello,

I’m having trouble publishing my site on GitHub Pages.

• My repository coursera-test is fully up to date on GitHub. I checked with git status in the terminal, and everything is correctly reflected in my coursera-test repository on GitHub.

• I have an index.html file at the root (coursera-test) and another inside the site/ folder (coursera-test/site).

• Both files work correctly locally—I verified this by running open index.html from the terminal—but neither is visible online.

• My GitHub Pages settings are: Branch main, Folder /root.

• I’m using the following URLs:
  https://rosebidzogoo-collab.github.io/coursera-test/
  https://rosebidzogoo-collab.github.io/coursera-test/site

Could you please help me understand why my site isn’t showing and how to fix it?

Thank you very much!

[sinavm]

Hi there,

Thank you for providing detailed information about the issue you're facing with publishing your site on GitHub Pages. It sounds like you’ve done a great job verifying that your repository is up to date and that your files work locally. Let’s troubleshoot why your site isn’t visible online and get it up and running!

Based on your description, here are a few potential reasons why your site might not be displaying at the URLs you provided (https://rosebidzogoo-collab.github.io/coursera-test/ and https://rosebidzogoo-collab.github.io/coursera-test/site), along with steps to fix them.

Potential Issues and Solutions

1. GitHub Pages Source Configuration
   You mentioned that your GitHub Pages settings are set to the main branch and the /root folder. This means GitHub Pages will serve the content from the root of your main branch. Therefore, the index.html file in the root of your coursera-test repository should be served at https://rosebidzogoo-collab.github.io/coursera-test/.

   However, if the index.html file in the site/ folder is intended to be the main page, you might have a configuration mismatch. GitHub Pages only serves one source folder per branch, so the site/ folder won’t automatically be accessible unless explicitly configured or referenced.

   Solution:

   • Confirm that the index.html in the root (coursera-test/index.html) is the one you want to serve. If so, keep your GitHub Pages settings as main branch and /root folder.
   • If you want the index.html inside the site/ folder to be served, update your GitHub Pages settings:
     1. Go to your repository on GitHub.
     2. Navigate to Settings > Pages.
     3. Under "Build and deployment," set the source to the main branch and change the folder to /site.
     4. Save the changes.
     5. Wait a few minutes for GitHub Pages to deploy, then check https://rosebidzogoo-collab.github.io/coursera-test/. The index.html in the site/ folder should now be served at this URL.

   Note: The URL https://rosebidzogoo-collab.github.io/coursera-test/site will only work if there’s an index.html file in the site/ folder and the root index.html contains a link to it or you’ve configured GitHub Pages to serve the site/ folder.

2. Deployment Delay
   GitHub Pages can sometimes take a few minutes to deploy changes, especially if you recently pushed updates or changed the Pages settings.

   Solution:

   • Check the Actions tab in your repository to see if there’s a GitHub Pages deployment workflow running or if it failed. If it failed, there might be an error in your repository structure or files.
   • Wait 5–10 minutes and try accessing the URLs again.

3. File and Path Issues
   If your index.html files reference other resources (e.g., CSS, JavaScript, or images), ensure that the paths are correct for the web. Local testing (open index.html) uses the file:// protocol, which resolves paths differently than GitHub Pages’ https:// protocol. For example:

   • A relative path like <img src="images/photo.jpg"> assumes images/ is in the same directory as the index.html file.
   • If you’re using absolute paths like /images/photo.jpg, the leading / refers to the root of the GitHub Pages site (https://rosebidzogoo-collab.github.io/coursera-test/).

   Solution:

   • Open your browser’s developer tools (F12) and check the Console and Network tabs when visiting your GitHub Pages URLs. Look for 404 errors indicating missing files.
   • Ensure all resource paths in your index.html files are relative to the correct base path. For example:
     • For the root index.html, a file in coursera-test/images/photo.jpg should be referenced as <img src="images/photo.jpg">.
     • For the site/index.html, a file in coursera-test/site/images/photo.jpg should be referenced as <img src="images/photo.jpg"> (relative to the site/ folder).
   • If you want https://rosebidzogoo-collab.github.io/coursera-test/site to work, ensure there’s an index.html in the site/ folder and that it’s correctly referenced or accessible.

4. Repository Permissions
   Ensure your repository is public (or private with GitHub Pages enabled for private repositories, if you have a GitHub Pro or higher plan). If the repository is private and you don’t have the appropriate plan, GitHub Pages won’t serve the site.

   Solution:

   • Go to your repository’s Settings > General.
   • Check if the repository is public. If it’s private, either make it public or verify that your GitHub account allows GitHub Pages for private repositories.

5. Case Sensitivity and File Names
   GitHub Pages is case-sensitive. If your file is named Index.html (with a capital I) but you’re referencing index.html, it may not work online, even if it works locally on a case-insensitive file system (e.g., macOS or Windows).

   Solution:

   • Verify that the file names in your repository match exactly (e.g., index.html vs. Index.html).
   • Rename files to use lowercase to avoid issues: git mv Index.html index.html, then commit and push the changes.

Steps to Verify and Fix

Here’s a step-by-step plan to resolve the issue:

1. Confirm Your Intent:

   • Decide whether you want the root index.html or the site/index.html to be the main page for https://rosebidzogoo-collab.github.io/coursera-test/.
   • If you want both to be accessible, you’ll need to configure the root index.html to link to site/index.html (e.g., <a href="/coursera-test/site">Go to site folder</a>).

2. Check GitHub Pages Settings:

   • Go to Settings > Pages in your repository.
   • Ensure the source is set to the main branch and the correct folder (/root for the root index.html, or /site for the site/index.html).
   • Save and wait for deployment.

3. Inspect Your Files:

   • Verify that index.html (in the root or site/ folder) is present and correctly formatted.
   • Check for errors in paths to resources (CSS, JS, images) using your browser’s developer tools.

4. Test the URLs:

   • Visit https://rosebidzogoo-collab.github.io/coursera-test/ after confirming the settings.
   • If you configured the site/ folder, this URL should show the site/index.html content. If you kept /root, it should show the root index.html.
   • If you want https://rosebidzogoo-collab.github.io/coursera-test/site to work, ensure there’s an index.html in the site/ folder and that it’s accessible via the root index.html or correct Pages settings.

5. Check Deployment Status:

   • Go to the Actions tab in your repository to confirm that the GitHub Pages workflow completed successfully.
   • If there’s an error, click the workflow for details and share them here if you need further help.

Additional Notes

• If you’re still seeing a 404 error or a blank page, it’s possible that the deployment hasn’t propagated yet or there’s an issue with the file paths. Let me know what you see when you visit the URLs (e.g., a 404 error, a blank page, or something else).
• If you’re using a custom domain, ensure the DNS settings are correct, as misconfigured domains can also cause issues.
• If you’d like, you can share the contents of your index.html files (or the relevant parts, like resource paths) or a screenshot of your GitHub Pages settings for more specific guidance.

I hope this helps get your site live! Let me know if you run into any issues or need clarification on any of these steps. 😊

Best regards,
@sinavm

[rosebidzogoo-collab]

Hello,

I would like to provide an update regarding my GitHub Pages issue.

I have an index.html file in the root of my repository (coursera-test) and another index.html in the subfolder coursera-test/site.

The GitHub Pages configuration is correct to serve the site from the root folder.

The index.html in the root is a basic HTML page that simply displays:

Bonjour, ceci est mon premier site ! 🚀
Despite this, the site is still not visible online at:
https://rosebidzogoo-collab.github.io/coursera-test/

Could you please help me understand why the site isn’t showing and how to fix it?

Thank you very much!
Rose Bidzogo

[shinybrightstar]

Welcome to the GitHub Community, @rosebidzogoo-collab, we're happy you're here! 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 Pages category, I've gone ahead and moved it for you. Good luck!

[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. ⭐

[rosebidzogoo-collab]

Hello, I would like to provide an update regarding my GitHub Pages issue. I have an index.html file in the *root of my repository (coursera-test)* and another index.html in the *subfolder coursera-test/site*. The GitHub Pages configuration is correct to serve the site from the *root folder*. The index.html in the root is a basic HTML page that simply displays: Bonjour, ceci est mon premier site ! 🚀 Despite this, the site is still not visible online at: https://rosebidzogoo-collab.github.io/coursera-test/ Could you please help me understand why the site isn’t showing and how to fix it? Thank you very much! *Rose Bidzogo* Le mer. 8 oct. 2025 à 04:50, sina ***@***.***> a écrit :

…

Hi there, Thank you for providing detailed information about the issue you're facing with publishing your site on GitHub Pages. It sounds like you’ve done a great job verifying that your repository is up to date and that your files work locally. Let’s troubleshoot why your site isn’t visible online and get it up and running! Based on your description, here are a few potential reasons why your site might not be displaying at the URLs you provided ( https://rosebidzogoo-collab.github.io/coursera-test/ and https://rosebidzogoo-collab.github.io/coursera-test/site), along with steps to fix them. Potential Issues and Solutions 1. *GitHub Pages Source Configuration* You mentioned that your GitHub Pages settings are set to the main branch and the /root folder. This means GitHub Pages will serve the content from the root of your main branch. Therefore, the index.html file in the root of your coursera-test repository should be served at https://rosebidzogoo-collab.github.io/coursera-test/. However, if the index.html file in the site/ folder is intended to be the main page, you might have a configuration mismatch. GitHub Pages only serves one source folder per branch, so the site/ folder won’t automatically be accessible unless explicitly configured or referenced. *Solution*: - Confirm that the index.html in the root (coursera-test/index.html) is the one you want to serve. If so, keep your GitHub Pages settings as main branch and /root folder. - If you want the index.html inside the site/ folder to be served, update your GitHub Pages settings: 1. Go to your repository on GitHub. 2. Navigate to *Settings > Pages*. 3. Under "Build and deployment," set the source to the main branch and change the folder to /site. 4. Save the changes. 5. Wait a few minutes for GitHub Pages to deploy, then check https://rosebidzogoo-collab.github.io/coursera-test/. The index.html in the site/ folder should now be served at this URL. *Note*: The URL https://rosebidzogoo-collab.github.io/coursera-test/site will only work if there’s an index.html file in the site/ folder *and* the root index.html contains a link to it or you’ve configured GitHub Pages to serve the site/ folder. 2. *Deployment Delay* GitHub Pages can sometimes take a few minutes to deploy changes, especially if you recently pushed updates or changed the Pages settings. *Solution*: - Check the *Actions* tab in your repository to see if there’s a GitHub Pages deployment workflow running or if it failed. If it failed, there might be an error in your repository structure or files. - Wait 5–10 minutes and try accessing the URLs again. 3. *File and Path Issues* If your index.html files reference other resources (e.g., CSS, JavaScript, or images), ensure that the paths are correct for the web. Local testing (open index.html) uses the file:// protocol, which resolves paths differently than GitHub Pages’ https:// protocol. For example: - A relative path like <img src="images/photo.jpg"> assumes images/ is in the same directory as the index.html file. - If you’re using absolute paths like /images/photo.jpg, the leading / refers to the root of the GitHub Pages site ( https://rosebidzogoo-collab.github.io/coursera-test/). *Solution*: - Open your browser’s developer tools (F12) and check the *Console* and *Network* tabs when visiting your GitHub Pages URLs. Look for 404 errors indicating missing files. - Ensure all resource paths in your index.html files are relative to the correct base path. For example: - For the root index.html, a file in coursera-test/images/photo.jpg should be referenced as <img src="images/photo.jpg">. - For the site/index.html, a file in coursera-test/site/images/photo.jpg should be referenced as <img src="images/photo.jpg"> (relative to the site/ folder). - If you want https://rosebidzogoo-collab.github.io/coursera-test/site to work, ensure there’s an index.html in the site/ folder and that it’s correctly referenced or accessible. 4. *Repository Permissions* Ensure your repository is public (or private with GitHub Pages enabled for private repositories, if you have a GitHub Pro or higher plan). If the repository is private and you don’t have the appropriate plan, GitHub Pages won’t serve the site. *Solution*: - Go to your repository’s *Settings > General*. - Check if the repository is public. If it’s private, either make it public or verify that your GitHub account allows GitHub Pages for private repositories. 5. *Case Sensitivity and File Names* GitHub Pages is case-sensitive. If your file is named Index.html (with a capital I) but you’re referencing index.html, it may not work online, even if it works locally on a case-insensitive file system (e.g., macOS or Windows). *Solution*: - Verify that the file names in your repository match exactly (e.g., index.html vs. Index.html). - Rename files to use lowercase to avoid issues: git mv Index.html index.html, then commit and push the changes. Steps to Verify and Fix Here’s a step-by-step plan to resolve the issue: 1. *Confirm Your Intent*: - Decide whether you want the root index.html or the site/index.html to be the main page for https://rosebidzogoo-collab.github.io/coursera-test/. - If you want both to be accessible, you’ll need to configure the root index.html to link to site/index.html (e.g., <a href="/coursera-test/site">Go to site folder</a>). 2. *Check GitHub Pages Settings*: - Go to *Settings > Pages* in your repository. - Ensure the source is set to the main branch and the correct folder (/root for the root index.html, or /site for the site/index.html). - Save and wait for deployment. 3. *Inspect Your Files*: - Verify that index.html (in the root or site/ folder) is present and correctly formatted. - Check for errors in paths to resources (CSS, JS, images) using your browser’s developer tools. 4. *Test the URLs*: - Visit https://rosebidzogoo-collab.github.io/coursera-test/ after confirming the settings. - If you configured the site/ folder, this URL should show the site/index.html content. If you kept /root, it should show the root index.html. - If you want https://rosebidzogoo-collab.github.io/coursera-test/site to work, ensure there’s an index.html in the site/ folder and that it’s accessible via the root index.html or correct Pages settings. 5. *Check Deployment Status*: - Go to the *Actions* tab in your repository to confirm that the GitHub Pages workflow completed successfully. - If there’s an error, click the workflow for details and share them here if you need further help. Additional Notes - If you’re still seeing a 404 error or a blank page, it’s possible that the deployment hasn’t propagated yet or there’s an issue with the file paths. Let me know what you see when you visit the URLs (e.g., a 404 error, a blank page, or something else). - If you’re using a custom domain, ensure the DNS settings are correct, as misconfigured domains can also cause issues. - If you’d like, you can share the contents of your index.html files (or the relevant parts, like resource paths) or a screenshot of your GitHub Pages settings for more specific guidance. I hope this helps get your site live! Let me know if you run into any issues or need clarification on any of these steps. 😊 Best regards, @sinavm <https://github.com/sinavm> — Reply to this email directly, view it on GitHub <#176175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYE27ASIJQJUBQABV4ETXYL3WT3CDAVCNFSM6AAAAACITCTRWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRSGUZTSNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Yajat047]

Hi There,
I checked your repository, and it seems there’s currently no index.html file visible in the repository. GitHub Pages requires an index.html at the root of the selected publishing folder (in your case, /root) to load the site correctly.

Please make sure that:

The index.html file is committed and pushed to your GitHub repository (not just on your local machine).

It’s located at the root of your publishing branch (main), not inside another subfolder.

Once the file appears in your repository on GitHub, Pages should automatically redeploy and your site should load normally.

[rosebidzogoo-collab]

Hi there,

The index.html file was actually present in the repository, as shown in my screenshots. I deleted everything to start over from scratch, but I’m still facing the same issue.

Could you please check again on your end to see if anything might still be preventing the site from loading correctly?

Thank you for your help!

[Yajat047]

I believe it's working now

[rosebidzogoo-collab]

No, it’s still not working on my end.

Have you tested the links on your side? Because neither
👉 https://rosebidzogoo-collab.github.io/coursera-test/

nor
👉 https://rosebidzogoo-collab.github.io/coursera-test/index.html

seem to load the index.html file properly.

[Yajat047]

Then I would suggest that you try to clear cookies for the website and then reload it

[rosebidzogoo-collab]

Hi there, The *index.html* file was actually present in the repository, as shown in my screenshots. I deleted everything to start over from scratch, but I’m still facing the same issue. Could you please check again on your end to see if anything might still be preventing the site from loading correctly? Thank you for your help! Le mer. 15 oct. 2025 à 20:46, Yajat Dureja ***@***.***> a écrit :

…

Hi There, I checked your repository, and it seems there’s currently no index.html file visible in the repository. GitHub Pages requires an index.html at the root of the selected publishing folder (in your case, /root) to load the site correctly. Please make sure that: The index.html file is committed and pushed to your GitHub repository (not just on your local machine). It’s located at the root of your publishing branch (main), not inside another subfolder. Once the file appears in your repository on GitHub, Pages should automatically redeploy and your site should load normally. — Reply to this email directly, view it on GitHub <#176175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYE27AQW76QEHJGACYXG4KT3X2QCVAVCNFSM6AAAAACITCTRWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZGA4TSNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rosebidzogoo-collab]

No, it’s still not working on my end. Have you tested the links on your side? Because neither 👉 https://rosebidzogoo-collab.github.io/coursera-test/ nor 👉 https://rosebidzogoo-collab.github.io/coursera-test/index.html seem to load the index.html file properly. Le jeu. 16 oct. 2025 à 12:21, Yajat Dureja ***@***.***> a écrit :

…

I believe it's working now — Reply to this email directly, view it on GitHub <#176175 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYE27AVWKS4HIN7OTFQRERL3X55S5AVCNFSM6AAAAACITCTRWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZG43TOMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rosebidzogoo-collab]

I’ve already tried clearing the cookies for the website, but it still doesn’t work.

Is it working on your side?

[Yajat047]

Yes, both the links are working on my end

[rosebidzogoo-collab]

I’ve already tried clearing the cookies for the website, but it still doesn’t work. Is it working on your side? Le jeu. 16 oct. 2025 à 12:34, Yajat Dureja ***@***.***> a écrit :

…

Then I would suggest that you try to clear cookies for the website and then reload it — Reply to this email directly, view it on GitHub <#176175 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BYE27AT4TYATJXZURVN2DOD3X57F7AVCNFSM6AAAAACITCTRWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZG44TEMA> . You are receiving this because you were mentioned.Message ID: ***@***.***>