Ok, before ask, look at config files, my mistake.
There is no word about enabling Gitlab Pages in /etc/gitlab/gitlab.rb (in case of omnibus installs).
Current link to pages documentation: GitLab Pages
Answer from Ellesmess Glain on Stack ExchangeGitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › settings
GitLab Pages settings | GitLab Docs
Introduced in GitLab 16.1 with a Pages flag named FF_CONFIGURABLE_ROOT_DIR. Disabled by default. Enabled on GitLab.com in GitLab 16.1.
GitLab Docs
Learn how to use and administer GitLab, the most scalable Git-based fully integrated platform for software development.
Environments
Must be enabled. ... On the page for a specific environment, on the right, select Terminal ( ).
GitLab Pages
If you’re using GitLab Pages default domain (.gitlab.io), your website is automatically secure and available under HTTPS. If you’re using your own custom domain, you can optionally secure it with SSL/TLS certificates. If you’re using GitLab.com, your website is publicly available to the internet. To restrict access to your website, enable ...
Releases
Releases, versioning, assets, tags, milestones, and evidence.
GitLab
docs.gitlab.com › gitlab docs › administer › update your settings › gitlab pages
GitLab Pages administration | GitLab Docs
To configure GitLab Pages DNS for single-domain sites without wildcard DNS: Enable the GitLab Pages flag for this feature by adding gitlab_pages['namespace_in_path'] = true to /etc/gitlab/gitlab.rb.
How to activate Gitlab Pages Properly? - Stack Overflow
I just get an blank page and it is saying that it takes too long to respond. My Gitlab CI is fine and is deploying the pages I see that in my CI job. For your perspective: I have copied the vuepress example site and added the gitlab-ci.yml. I have enabled pages as described and set the DNS. More on stackoverflow.com
Configuring GitLab Pages Help!
gitlab_pages['enable'] = true pages_nginx['redirect_http_to_https'] = true gitlab_pages["namespace_in_path"] = true More on reddit.com
1
1
January 8, 2025How to setup gitlab pages
I’m very new to the gitlab pipeline and I am trying to setup gitlab pages in my repository I followed the gitlab tutorial, plus some google searching Here is my .gitlab-ci.yml default: image: ruby:3.2 before_script: - bundle init - bundle install - gem install bundler - bundle config set ... More on forum.gitlab.com
3
0
March 30, 2025Why is "Pages" not appearing in settings?
In the help on GitLab Pages the setup sound quite easy: Fork an example project: by forking a project, you create a copy of the codebase you’re forking from to start from a template instead of starting from scratch. Change a file to trigger a GitLab CI/CD pipeline: GitLab CI/CD will build ... More on forum.gitlab.com
7
0
May 29, 201805:26
How to Host a Static Website on GitLab Pages (Beginner Tutorial ...
07:52
Enabling GitLab Pages for a Single Domain - YouTube
03:25
How to Enable GitLab Pages for GitLab CE and EE - YouTube
03:44
How to Publish a Website with GitLab Pages - YouTube
GitLab Pages without Wildcard DNS - GA Release - 17.4
01:59
GitLab Pages without Wildcard DNS - Experimental Release - 16.7 ...
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages
GitLab Pages | GitLab Docs
Run on GitLab-provided infrastructure at no additional cost. Connect with custom domains and SSL/TLS certificates. Control access through built-in authentication. Scale reliably for personal, business, or project documentation sites. To publish a website with Pages, use any static site generator like Gatsby, Jekyll, Hugo, Middleman, Harp, Hexo, or Brunch.
Top answer 1 of 4
4
Ok, before ask, look at config files, my mistake.
There is no word about enabling Gitlab Pages in /etc/gitlab/gitlab.rb (in case of omnibus installs).
Current link to pages documentation: GitLab Pages
2 of 4
2
If you run into bind mount issue when using docker volume you'll also need to set this:
gitlab_pages['inplace_chroot'] = true
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
Pages are stored by default in /home/git/gitlab/shared/pages. To use a different location, edit gitlab.yml under the pages section: pages: enabled: true # The location where pages are stored (default: shared/pages).
Reddit
reddit.com › r/gitlab › configuring gitlab pages help!
r/gitlab on Reddit: Configuring GitLab Pages Help!
January 8, 2025 - gitlab_pages['enable'] = true pages_nginx['redirect_http_to_https'] = true gitlab_pages["namespace_in_path"] = true
GitLab
forum.gitlab.com › gitlab ci/cd
How to setup gitlab pages - GitLab CI/CD - GitLab Forum
March 30, 2025 - I’m very new to the gitlab pipeline and I am trying to setup gitlab pages in my repository I followed the gitlab tutorial, plus some google searching Here is my .gitlab-ci.yml default: image: ruby:3.2 before_script: - bundle init - bundle install - gem install bundler - bundle config set path 'vendor' cache: paths: - vendor/ workflow: rules: - if: $CI_COMMIT_BRANCH create-pages: stage: deploy script: - bundle exec jekyll build -d public pages...
Erikpoehler
erikpoehler.com › home › gitlab › activating gitlab pages directly on your gitlab…
Activating Gitlab Pages directly on your Gitlab Server - Erik Pöhler's Weblog
July 30, 2025 - image: node:22 pages: needs: [] stage: deploy cache: paths: - node_modules/ script: - yarn install - yarn docs:build artifacts: paths: - public/docs expire_in: 1 week rules: - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH changes: - docs/** - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH when: manual allow_failure: true · Activating Gitlab Pages in Gitlab is pretty easy.
Creoline
help.creoline.com › en › doc › gitlab-pages-ZZtvphZJyN
GitLab Pages
Navigate to the desired repository and select the menu item Settings → Pages. From here, you can customize the pipeline configuration via the gitlab-ci.yml file to enable GitLab Pages.
GitLab
forum.gitlab.com › how to use gitlab
Why is "Pages" not appearing in settings? - How to Use GitLab - GitLab Forum
May 29, 2018 - In the help on GitLab Pages the setup sound quite easy: Fork an example project: by forking a project, you create a copy of the codebase you’re forking from to start from a template instead of starting from scratch. Change a file to trigger a GitLab CI/CD pipeline: GitLab CI/CD will build and deploy your site to GitLab Pages.
GitLab
about.gitlab.com › blog › engineering › hosting on gitlab.com with gitlab pages
Hosting on GitLab.com with GitLab Pages
April 7, 2016 - To build our Hexo site, we can start with this .gitlab-ci.yml: ... image: node:4.2.2 pages: cache: paths: - node_modules/ script: - npm install hexo-cli -g - npm install - hexo deploy artifacts: paths: - public only: - main
Wildsre
wiki.wildsre.com › gitlab › enable_gitlab_pages
Using GitLab Pages | WILD-SRE Learning Wiki
GitLab Pages is the built‑in static website hosting feature of GitLab (available on GitLab.com and Self‑Managed). It enables auto‑deployment of static sites—generated by Hugo, Jekyll, MkDocs, or plain HTML/CSS/JS—directly from Git as part of the CI/CD workflow.
Top answer 1 of 4
5
You have to activate the pages feature. In your gitlab.rb:
pages_external_url "IP_OF_YOUR_GITLAB"
gitlab_pages['enable'] = true
There is a tutorial: https://www.youtube.com/watch?v=dD8c7WNcc6s&feature=youtu.be And the complete documentation: https://docs.gitlab.com/ce/administration/pages/index.html
2 of 4
1
You'll need to ask your sysadmin under which wildcard domain Pages is served: https://docs.gitlab.com/ce/user/project/pages/getting_started_part_one.html#gitlab-pages-domain
Then you'll know where your site was deployed to.
Example: on GitLab.com, all Pages domains are served under *.gitlab.io, therefore, your website will be deployed to username.gitlab.io (user/group site) or to username.gitlab.io/project-name (project website).
You need to find out the wildcard domain of your GitLab instance and replace gitlab.io with it.
See also: Pages' limitations: https://docs.gitlab.com/ce/user/project/pages/introduction.html#limitations
OneUptime
oneuptime.com › home › blog › how to set up pages deployment in gitlab ci
How to Set Up Pages Deployment in GitLab CI
December 21, 2025 - GitLab Pages automatically provisions Let's Encrypt certificates for custom domains. # No special CI configuration needed for HTTPS # Enable in Deploy > Pages > Force HTTPS deploy_pages: stage: deploy script: - mv dist public pages: true artifacts: paths: - public rules: - if: '$CI_COMMIT_BRANCH == "main"'
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › access control
GitLab Pages access control | GitLab Docs
Ask your administrator to enable it. The Pages access control dropdown list allows you to set who can view pages hosted with GitLab Pages, depending on your project’s visibility:
GitLab
forum.gitlab.com › how to use gitlab › self-managed
Gitlab pages not getting enabled - Self-managed - GitLab Forum
June 7, 2023 - Hello I tried to enable gitlab-pages on self-hosted Omnibus GitLab instance by following GitLab Pages administration | GitLab instructions. I started with the minimal set of requirements to enable the gitlab-pages but no. lock. external_url “https://gitlab.example.com” # external_url here is only for reference pages_external_url “https://pages.example.com” # not a subdomain of external_url Even I’m not seeing any error in gitlab logs.
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › gitlab pages › create deployment for static site
Create a GitLab Pages deployment for a static site | GitLab Docs
(To enable, go to Settings > General, expand Visibility, project features, permissions, and turn on the Pages toggle.) To complete the setup and generate a GitLab Pages deployment: