Unable to view private GitHub Pages #23146
-
Hello, I’ve got a GitHub Enterprise Cloud account and I’m struggling to get private pages to work. In a test project in an Organisation, I’ve set the repo to private and I’ve created a docs directory with an index.html file, and then I’ve enabled Pages for the /docs directory in the master branch. Visibility of Pages is set to private as per my requirements, and ostensibly it has been built correctly. I’ve got a https://adjective-noun-randomid.pages.github.io/ address, but when I visit it I just get redirected to the GitHub settings page for my email details. Interestingly if I change visibility (of Pages, not the project) to public, then I get an address of the form https://organisation.github.io/projectname, and this displays the html fine. Changing back to private, it’s broken again. So something appears to be broken with the ‘private’ visibility functionality. Any ideas please? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
I’ve got a solution to this thanks to Allie at GitHub support. My problem, it turned out, was due to by browser cache needing to be cleared. For some reason it wasn’t properly authenticating me to access the page. First clue was that it was working from a private browser session. Hope this helps anyone that sees the same weird behaviour. Cheers. |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome! I was just looking into this when I saw the ticket was resolved. Thank you for sharing the solution - I can guarantee others will have the same question :slight_smile: |
Beta Was this translation helpful? Give feedback.
-
Hi @forky2 - thanks for letting us know on here as well for others, and please don’t hesitate to let me know if you have any other questions! |
Beta Was this translation helpful? Give feedback.
I’ve got a solution to this thanks to Allie at GitHub support.
My problem, it turned out, was due to by browser cache needing to be cleared. For some reason it wasn’t properly authenticating me to access the page. First clue was that it was working from a private browser session.
Hope this helps anyone that sees the same weird behaviour.
Cheers.