Nginx 的client_max_body_size设置:Nginx 是 GitLab 的反向代理服务器,它负责处理所有传入的 HTTP 请求。在默认情况下,Nginx 会限制上传文件的大小为 1MB。 GitLab 的gitlab_rails['max_attachment_size']设置:这是 GitLab 本身的配置项,用于限制上传文件的大小。默认情况下,这个值也是 1MB。 如果要上传大于这...
打开这几个的限制,当然了client_max_body_size还是看个人需求了,我就搞了一个250m。然后保存 root@gitlab-77d7878db-zknvb:/# gitlab-ctl reconfigureroot@gitlab-77d7878db-zknvb:/# gitlab-ctl restart 退出容器进行验证上传大文件(还是要小于你的nginx配置的client_max_body_size和web中的设置两个参数的...
server_name gitlab.example.com; client_max_body_size 30M; index index.php index.html index.htm default.php default.htm default.html; root /www/webRoot/gitlab.example.com; #SSL-START SSL相关配置,请勿删除或修改下一行带注释的404规则 #error_page 404/404.html; #HTTP_TO_HTTPS_START if ($se...
#启用Nginx服务 nginx['client_max_body_size'] = '250m' #设置客户端最大文件上传大小 nginx['redirect_http_to_https'] = true #设置开启自动将HTTP跳转到HTTPS nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.xxx.cn.pem" #设置HTTPS所使用的证书 nginx['ssl_certificate_key'] = "/etc/git...
client_max_body_size 0; 如下: server {listen80; server_name git.pauledenburg.com; client_max_body_size0; location / { proxy_pass http://localhost:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for...
client_max_body_size 250m; ssl_certificate /etc/letsencrypt/live/hub.gitlab.myteam . com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/hub.gitlab.myteam . com/privkey.pem; location / { proxy_pass http : // hub_gitlab_myteam_com; ...
{client_max_body_size0;gzip off;proxy_read_timeout300;proxy_connect_timeout300;proxy_redirect off;proxy_http_version1.1;proxy_set_header Host $http_host;proxy_set_headerX-Real-IP$remote_addr;proxy_set_headerX-Forwarded-For $proxy_add_x_forwarded_for;proxy_set_headerX-Forwarded-Proto $...
client_max_body_size 1024m; # 让后端获取真实的client IP proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } gitlab-runner 升级完 GitLab 后,旧的版本的 runner 会无法连接,需要更新 runn...
{ client_max_body_size 0; # 'Error' 418 is a hack to re-use the @gitlab-workhorse block error_page 418 = @gitlab-workhorse; return 418; } # Build artifacts should be submitted to this location location ~ /ci/api/v1/builds/[0-9]+/artifacts { client_max_body_size 0; # '...
Bringing this back because it appears that error_page 418 hack that we use to reuse the gitlab-workhorse block is not using the client_max_body_size within that block.