XiphInfra:GitLab VM: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== IP blocks == We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance. The IP blocks are configured in <code>/etc/gitlab/gitlab.rb</cod...") |
No edit summary |
||
| Line 3: | Line 3: | ||
The IP blocks are configured in <code>/etc/gitlab/gitlab.rb</code> in the <code>nginx['custom_gitlab_server_config']</code> option. Additionally there is a custom error page for when the IP is blocked, which is stored at <code>/var/www/html/gitlab-ipblock.html</code>. | The IP blocks are configured in <code>/etc/gitlab/gitlab.rb</code> in the <code>nginx['custom_gitlab_server_config']</code> option. Additionally there is a custom error page for when the IP is blocked, which is stored at <code>/var/www/html/gitlab-ipblock.html</code>. | ||
After making changes to the <code>gitlab.rb</code>, you need to run <code>sudo gitlab-ctl reconfigure</code> for the changes to be applied to the actual config files. '''Under no circumstances edit the generated config files directly''', always use the <code>gitlab.rb</code> config. | |||
Revision as of 05:13, 28 May 2021
IP blocks
We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance.
The IP blocks are configured in /etc/gitlab/gitlab.rb in the nginx['custom_gitlab_server_config'] option. Additionally there is a custom error page for when the IP is blocked, which is stored at /var/www/html/gitlab-ipblock.html.
After making changes to the gitlab.rb, you need to run sudo gitlab-ctl reconfigure for the changes to be applied to the actual config files. Under no circumstances edit the generated config files directly, always use the gitlab.rb config.