Pages sites become private(require login) after enabling access control(only self-hosted)
Summary
Extracted from #32961 (closed)
Consider the scenario on self-hosted installation:
- User creates a private project with pages
- Admin enables Access Control for pages on the instance level
This change will make pages site private since the default access level is only project members
but it takes affect only of access control enabled on the instance level.
We've faced this issue on gitlab.com, and !18386 (merged) solves it there. But we currently don't have a solution for self-hosted instances and can't use the same approach.
Workaround
Visit Settings -> General -> Visibility
and change "Pages Access Control" to everyone and save changes. Changes make take up to 30 minutes to take effect.
It's also possible to execute update in the database for all existing projects.
What is the current bug behavior?
The pages website which was public before becomes private once access control is enabled.
What is the expected correct behavior?
The site should stay public.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
Not
reproduced on gitlab.com(already fixed there by !18386 (merged)).
Possible fixes
The wild idea: change access control settings for project on pages deployment: !18864 (closed)