For anyone here arriving late, like me… gitlab-org/omnibus-gitlab: Merge Request: Support for pages authentication switches (Merged) gitlab-org/gitlab-ce: Merge Request: Make GitLab pages support access control (Merged) gitlab-org/gitlab-pages: Merge Request: Make GitLab pages support access cont… Answer from tyler-in on forum.gitlab.com
🌐
GitLab
forum.gitlab.com › how to use gitlab
Can I make gitlab pages private? - How to Use GitLab - GitLab Forum
March 5, 2016 - I just started using gitlab pages on gitlab.com for a public project. I also have a private repository I would like to restrict access to the generated pages to only those with access to the repository. Is that possible? If not, are there any other supported authentication methods?
🌐
Reddit
reddit.com › r/gitlab › does gitlab pages access control not work anymore?
r/gitlab on Reddit: Does GitLab Pages Access Control not work anymore?
July 17, 2021 -

Hi everyone. Lately I've been wanting to publish a public static website that's in a private repository of mine (hosted on gitlab.com). I already did that in the past once and supposed that it wouldn't be a problem for me.

However, now, GitLab keeps telling me "Access Control is enabled for this Pages website; only authorized users will be able to access it. To make your website publicly available, navigate to your project's Settings > General > Visibility and select Everyone in pages section", and when I do these exact steps, nothing changes and the message keeps showing up for some reason. I tried waiting a few hours and fiddling with the visibility fields but nothing works.

When I checked on my older project to compare fields, I noticed that the pages' visibility was "Only Project Members" though it was still accessible on other computers and on a private window without logging in, but I once miss-clicked on "Save" and now the message above keeps popping up on this repository too, and, of course, the previously-public pages are now private, even though I checked "Everyone" on "Pages Visibility" there.

The documentation also shares this YouTube video and I noticed the subcategories on Visibility was "Pages access control" here while it is "Pages" on my computer. I wonder if the name change broke something but I can't tell much about it. I tried to check on the issues list and haven't seen anyone talk about that.

Is there anything I can do to make my pages public?

Thanks a lot.

🌐
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › access control
GitLab Pages access control | GitLab Docs
The Pages access control dropdown list allows you to set who can view pages hosted with GitLab Pages, depending on your project’s visibility: If your project is private: Only project members: Only project members can browse the website. Everyone: Everyone, both logged into and logged out ...
🌐
GitLab
docs.gitlab.com › gitlab docs › administer › update your settings › gitlab pages
GitLab Pages administration | GitLab Docs
If your GitLab instance and the Pages daemon are deployed in a private network or behind a firewall, your GitLab Pages websites are only accessible to devices and users with access to the private network.
🌐
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › settings
GitLab Pages settings | GitLab Docs
April 25, 2022 - When you try to access a private Pages URL in two different tabs simultaneously without prior authentication, two different state values are returned for each tab. However, in the Pages session, only the most recent state value is stored for the given client. As a result, after submitting credentials, one of the tabs returns a 401 Unauthorized error. To resolve the 401 error, refresh the page. To deploy with GitLab Pages, the root content directory must contain a non-empty index.html file, or the pages:deploy job fails.
🌐
GitLab
gitlab.com › gitlab.org › gitlab-pages › #388
Programmatic access to private pages (#388) · Issues · GitLab.org / gitlab-pages · GitLab
Is it possible to access files hosted via GitLab Pages programmatically (e.g. using cURL from a CI job) when only project members are allowed to access Pages? When...
🌐
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages
GitLab Pages | GitLab Docs
To use GitLab Pages, you must create a project in GitLab to upload your website’s files to. These projects can be either public, internal, or private.
Find elsewhere
🌐
Reddit
reddit.com › r/gitlab › gitlab pages stuck in private?
r/gitlab on Reddit: Gitlab pages stuck in Private?
September 29, 2024 -

So I'm trying to host a webpage using gitlab pages and a domain i puchased, but no one can access it unless the have gitlab and when I went in to change the settings to public assuming that was the issue. Its stuck in private and I'm not sure how to get it so people can access it. I need help.

🌐
GitLab
about.gitlab.com › blog › engineering › hosting on gitlab.com with gitlab pages
Hosting on GitLab.com with GitLab Pages
April 7, 2016 - ... Privacy - choose if you want your project to be visible and accessible just for you (private), just for GitLab.com users (internal) or free to anyone to view, clone, fork and download it (public)
🌐
GitLab
docs.gitlab.com › gitlab docs › administer › update your settings › gitlab pages › gitlab pages for source installations
GitLab Pages administration for self-compiled installations | GitLab Docs
Access control works by registering the Pages daemon as an OAuth application with GitLab. Whenever an unauthenticated user requests access to a private Pages site, the Pages daemon redirects the user to GitLab. If authentication is successful, the user is redirected back to Pages with a token, ...
🌐
University of Toronto
microfluidics.utoronto.ca › help › help
Pages access control · Pages · Project · User · Help · GitLab
The Pages access control dropdown list allows you to set who can view pages hosted with GitLab Pages, depending on your project's visibility: If your project is private: Only project members: Only project members are able to browse the website.
🌐
Reddit
reddit.com › r/gitlab › how can i have a private page of my gitbook on gitlab?
r/gitlab on Reddit: How can I have a private page of my gitbook on gitlab?
January 4, 2022 -

I have used gitbook template to create a gitbook on gitlab, everything is fine.

I can see the content on my desktop with local server by using command:

gitbook serve

And the page can be visited at http://localhost:4000

My question is:

How can I make the page be hosted on gitlab and only visited by myself or people granted by me? Is that possible? Cause github explicitly stated the repository have to be public to use the function of page. How about gitlab? Thanks.

🌐
GitLab
gitlab.lcqb.upmc.fr › help › user › project › pages › introduction.md
Introduction · Pages · Project · User · Help · GitLab
Yes. GitLab Pages doesn't care whether you set your project's visibility level to private, internal or public.
🌐
GitLab
gitlab.com › gitlab.org › gitlab-pages › #259
GitLab Pages Private Repository Issue (#259) · Issues · GitLab.org / gitlab-pages · GitLab
I have a private repository. This repository is for GitLab Pages. The page appears when I log in, but the login page is displayed when I do not...
🌐
Nira
nira.com › home › the ultimate manual to gitlab pages
The Ultimate Manual To GitLab Pages - Nira
May 3, 2022 - To use GitLab Pages, you have to first create a project, regardless of whether it’s public, private, or internal, in GitLab to upload your website files. GitLab Pages will always deploy your website from a specific folder called public in your repository.
🌐
Evidence
docs.evidence.dev › deployment › self-host › gitlab-pages
GitLab Pages
Deploy Evidence to GitLab Pages from a GitLab repo. GitLab Pages can be private to your org, support custom domains, and GitLab CI/CD for data refresh.
🌐
PRACE
repository.prace-ri.eu › help
Index · Pages · Project · User · Help · GitLab
To use GitLab Pages, you must create a project in GitLab to upload your website's files to. These projects can be either public, internal, or private.