Outbound Proxy Settings for GitLab's Packaged Services

Set the Linux package's service environment in gitlab.rb and apply it through reconfiguration.

For the self-managed GitLab Linux package, choose the service making the outbound request. gitlab_rails['env'] supplies Puma, Sidekiq, Rails and Rake; the package separately documents gitaly['env'] for Git-clone proxying and gitlab_workhorse['env'] for Workhorse.

For the Rails-related path, merge these values into /etc/gitlab/gitlab.rb:

gitlab_rails['env'] = {
  'http_proxy' => 'http://proxy.example.net:8080',
  'https_proxy' => 'http://proxy.example.net:8080',
  'no_proxy' => 'localhost,127.0.0.1,::1'
}

Use the deployment's endpoint and bypasses. A separate public-service check may use an HTTP endpoint from the HTTP proxy list when the deployment permits that route and the selected service has no configured proxy credentials. Keep its required internal bypasses. Preserve existing entries: another assignment to the same environment hash replaces the earlier hash.

Apply the declared package configuration:

sudo gitlab-ctl reconfigure

A shell export does not render these managed-service settings. The reconfiguration step applies the environment declared for the selected component.

Аффингæй хæстæг статьялтæ