I currently get a 502 error when trying to access any of my Gitlab Pages links that are deployed, and the artifacts created by my runner once the pipeline is created also give this 502 error. I expect the Pages links to work and the artifacts also accessible.
We are currently implementing a self-managed Gitlab service running inside a zero-trust network. I have two instances, Instance A running Gitlab EE 16.7.3 which will be hosting my Gitlab setup, and Instance B running the same AMI which is my Gitlab Pages configuration.
Configuration
Main gitlab.rb file:
external_url ‘https://gitlab.example.ztna’
gitlab_rails[‘monitoring_whitelist’] = [‘127.0.0.0/8’, ‘10.0.0.0/8’]
postgresql[‘enable’] = false
gitlab_rails[‘db_adapter’] = “postgresql”
gitlab_rails[‘db_encoding’] = “unicode”
gitlab_rails[‘db_database’] = “DB_NAME”
gitlab_rails[‘db_username’] = “DB_USERNAME”
gitlab_rails[‘db_password’] = “DB_PASSWORD”
gitlab_rails[‘db_host’] = “DB_HOST.REGION.rds.amazonaws.com”
redis[‘enable’] = false
gitlab_rails[‘redis_host’] = “REDIS_HOST.REGION.cache.amazonaws.com”
gitlab_rails[‘redis_port’] = REDIS_PORT
git_data_dirs({
“default” => { “path” => “/mnt/nfs/gitlab-data” }
})
gitlab_pages[‘enable’] = false
gitlab_pages[‘access_control’] = true
pages_external_url “http://pages.example.ztna”
gitlab_pages[“namespace_in_path”] = true
Pages gitlab.rb file:
external_url ‘http://pages.example.ztna’
pages_external_url “http://pages.example.ztna”
gitlab_rails[‘pages_path’] = “/mnt/nfs/gitlab-data/pages”
gitlab_pages[‘gitlab_server’] = “https://gitlab.example.ztna”
gitlab_pages[‘access_control’] = true
gitlab_pages[“namespace_in_path”] = true
postgresql[‘enable’] = false
redis[‘enable’] = false
prometheus[‘enable’] = false
unicorn[‘enable’] = false
sidekiq[‘enable’] = false
gitlab_workhorse[‘enable’] = false
gitaly[‘enable’] = false
alertmanager[‘enable’] = false
node_exporter[‘enable’] = false
gitlab_rails[‘auto_migrate’] = false
Any help would be much appreciated.
