0

我已經從源代碼安裝gitlab安裝,使用letsencrypt對其進行了安全保護,並將其部署在https://gitlab.mydomain.com下。我可以訪問網站並創建存儲庫等,但我找不到一種方法來註冊安裝的gitlab ci runner。Gitlab CI - 未能註冊跑步者

Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com/ci): 
https://gitlab.mydomain.com/ci 
Please enter the gitlab-ci token for this runner: 
xxxxxxxx-xxxxxxxx 
Please enter the gitlab-ci description for this runner: 
[server]: test 
Please enter the gitlab-ci tags for this runner (comma separated): 
test 
ERROR: Registering runner... failed  runner=xxxxxxx 
status=couldn't execute POST against https://gitlab.mydomain.com/ci/api/v1/runners/register.json: 
Post https://gitlab.mydomain.com/ci/api/v1/runners/register.json: 
read tcp [ipv6address]:33518->[ipv6address]:443: read: connection reset by peer 
PANIC: Failed to register this runner. Perhaps you are having network problems 

我gitlab系統工作正常,我真的跑出來解釋爲什麼會有connection reset by peer。當我嘗試直接從錯誤消息中調出地址時,它會返回正確的響應。

curl -v https://gitlab.mydomain.com/ci/api/v1/runners/register.json 
* Trying ipv6address... 
* Connected to gitlab.mydomain.com (ipv6address) port 443 (#0) 
* found 174 certificates in /etc/ssl/certs/ca-certificates.crt 
* found 700 certificates in /etc/ssl/certs 
* ALPN, offering h2 
* ALPN, offering http/1.1 
* SSL connection using TLS1.2/ECDHE_RSA_AES_256_GCM_SHA384 
*  server certificate verification OK 
*  server certificate status verification SKIPPED 
*  common name: mydomain.com (matched) 
*  server certificate expiration date OK 
*  server certificate activation date OK 
*  certificate public key: RSA 
*  certificate version: #3 
*  subject: CN=mydomain.com 
*  start date: Wed, 18 May 2016 14:35:00 GMT 
*  expire date: Tue, 16 Aug 2016 14:35:00 GMT 
*   issuer: C=US,O=Let's Encrypt,CN=Let's Encrypt Authority X3 
*  compression: NULL 
* ALPN, server did not agree to a protocol 
> GET /ci/api/v1/runners/register.json HTTP/1.1 
> Host: gitlab.mydomain.com 
> User-Agent: curl/7.47.0 
> Accept: */* 
> 
< HTTP/1.1 405 Method Not Allowed 
< Server: nginx 
< Date: Sun, 29 May 2016 09:14:09 GMT 
< Content-Type: application/json 
< Content-Length: 2 
< Connection: keep-alive 
< Allow: OPTIONS, POST 
< Cache-Control: no-cache 
< Status: 405 Method Not Allowed 
+0

難道您發佈亞軍的配置? –

+0

@HuiWang - 它只有1行'concurrent = 1'。我認爲這是因爲創建配置的過程因上述錯誤而失敗。 – Jonas

+0

請看看這個鏈接https://gitlab.com/wiget/gitlab-ci-multi-runner/blob/master/docs/configuration/tls-self-signed.md –

回答

0

問題更新gitlab到8.8.3gitlab-multi-ci-runner到最新版本後,就走開了。

我也從頭開始我的gitlab nginx配置文件。

最後,我不知道哪個改變確實解決了問題。

0

我到目前爲止有很多錯誤和問題,以錯誤404,403開頭,並帶有發佈請求問題的結尾。

對我來說,問題似乎是incompatibility between GitLab and ci-runner

解決方案,在發行後相同,是安裝舊版本的C亞軍:

sudo apt install gitlab-ci-multi-runner=1.11.1