Gitlab CI令牌 - 带有apache的403

时间:2017-06-01 21:57:21

标签: apache continuous-integration apache2 gitlab

我在我的服务器上运行gitlab。我正在使用apache2(使用https)为网站服务。

最近我开始使用gitlab CI,但遇到了一个我无法自行解决的问题:我总是收到403错误:

remote: Access denied
fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@git.mydomain.com/group/project.git/': The requested URL returned error: 403

SSH和HTTP(S)都启用了克隆,ci可以正常使用公共项目,检查所有gitlab日志显示跑步者未经过身份验证,从而触发403。

我最好的猜测是apache配置没有将ci-token传递给gitlab,但我也不知道如何检查它,我也不相信这是真正的原因。

我的vhost:

<VirtualHost *:80>
  ServerName git.mydomain.com
  ServerSignature Off

  RewriteEngine on
  RewriteCond %{HTTPS} !=on
  RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [NE,R,L]
</VirtualHost>

<VirtualHost *:443>
  SSLEngine on

  SSLProtocol all -SSLv2
  SSLHonorCipherOrder on
  SSLCipherSuite     "ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS"
  Header add Strict-Transport-Security: "max-age=15768000;includeSubdomains"
  SSLCompression Off
  SSLCertificateFile /etc/letsencrypt/live/git.mydomain.com/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/git.mydomain.com/privkey.pem
  SSLCACertificateFile /etc/letsencrypt/live/git.mydomain.com/chain.pem

  ServerName git.mydomain.com
  ServerSignature Off

  ProxyPreserveHost On

  AllowEncodedSlashes NoDecode

  <Location />
    Require all granted
    ProxyPassReverse http://127.0.0.1:8181
    ProxyPassReverse http://git.mydomain.com/
  </Location>
  RewriteEngine on

  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f [OR]
  RewriteCond %{REQUEST_URI} ^/uploads/.*
  RewriteRule .* http://127.0.0.1:8181%{REQUEST_URI} [P,QSA,NE]

  RequestHeader set X_FORWARDED_PROTO 'https'
  RequestHeader set X-Forwarded-Ssl on

  DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public

  ErrorDocument 404 /404.html
  ErrorDocument 422 /422.html
  ErrorDocument 500 /500.html
  ErrorDocument 502 /502.html
  ErrorDocument 503 /503.html

  LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b" common_forwarded
  ErrorLog /var/log/apache2/gitlab_error.log
  CustomLog /var/log/apache2/gitlab_forwarded.log common_forwarded
  CustomLog /var/log/apache2/gitlab_access.log combined env=!dontlog
  CustomLog /var/log/apache2/gitlab.log combined

</VirtualHost>

/etc/gitlab/gitlab.rb的相关部分

external_url 'https://git.mydomain.com'

nginx['enable'] = false
web_server['external_users'] = ['www-data']
gitlab_workhorse['listen_network'] = "tcp"
gitlab_workhorse['listen_addr'] = "127.0.0.1:8181"

gitlab_rails['gitlab_email_reply_to'] = 'webmaster@mydomain.com'

Runner配置:

[[runners]]
  name = "Runner Name"
  url = "https://git.mydomain.com/ci"
  token = "Some generated token"
  executor = "shell"
  [runners.cache]

的/ etc /默认/ gitlab:

gitlab_workhorse_options="-listenUmask 0 -listenNetwork tcp -listenAddr 127.0.0.1:8181 -authBackend http://127.0.0.1:8080"

.gitlab-ci.yml:

stages:
  - compile

compilei7:
    stage: compile
    script:
        - /./home/public/folder/someScript.sh -f `$PWD`
    tags:
    - neededtag

所有的帮助表示赞赏,我在这里撞墙。 感谢。

2 个答案:

答案 0 :(得分:0)

似乎这在我发布的一个更新中已经修复了,因为我现在正在使用完全相同的服务器和配置发布这个问题。

答案 1 :(得分:0)

当GitLab Runner尝试从Git存储库中克隆项目时,就会发生这种情况。

为了解决该问题,请将您自己添加为项目的成员:

  1. 转到您在GitLab中的项目。
  2. 从左侧栏中的菜单中选择设置/成员条目。
  3. 选择要邀请的成员输入字段中,输入您的姓名(或推送其密码的成员的姓名)。
  4. 选择角色权限中,选择 Developer
  5. 点击添加到项目按钮。