大佬教程收集整理的这篇文章主要介绍了git克隆与http不工作在gitlab，大佬教程大佬觉得挺不错的，现在分享给大家，也给大家做个参考。
我有GitLab CE设置与我的域名（Ubuntu）和git克隆与http不工作，但ssh运作良好。
git clone git@gitlab.mydomain.com:anshad/test.git作品。
git clone http://gitlab.mydomain.com/anshad/test.git不工作。
@R_776_1419@ into 'test'... Username for 'http://gitlab.mydomain.com': anshad password for 'http://anshad@gitlab.mydomain.com': fatal: unable to access 'http://gitlab.mydomain.com/anshad/test.git/': The requested URL returned error: 500
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production说
将参数添加到wsgi脚本别名
如何在Apache FOP中设置默认语言
如何禁用Django / mod_WSGI页面caching
SVN错误E175002
System information System: Ubuntu 16.04 Current User: git Using RVM: no Ruby Version: 2.3.1p112 Gem Version: 2.5.1 Bundler Version:1.13.6 Rake Version: 10.5.0 Sidekiq Version:4.2.1 GitLab information Version: 8.14.0-pre Revision: 358e814 Directory: /home/git/gitlab DB Adapter: POSTGResql URL: http://gitlab.mydomain.com http Clone URL: http://gitlab.mydomain.com/some-group/some-project.git SSH Clone URL: git@gitlab.mydomain.com:some-group/some-project.git Using LDAP: no Using Omniauth: no GitLab SHell Version: 4.0.0 Repository storage paths: - default: /home/git/repositories/ Hooks: /home/git/gitlab-sHell/hooks/ Git: /usr/bin/git
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production说
checking GitLab SHell ... GitLab SHell version >= 4.0.0 ? ... OK (4.0.0) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... Anshad Vattapoyil / test ... repository is empty Running /home/git/gitlab-sHell/bin/check check GitLab API access: OK Access to /home/git/.ssh/authorized_keys: OK Send ping to redis server: OK gitlab-sHell self-check successful checking GitLab SHell ... Finished checking Sidekiq ... Running? ... yes number of Sidekiq processes ... 1 checking Sidekiq ... Finished checking Reply by email ... Reply by email is disabled in config/gitlab.yml checking Reply by email ... Finished checking LDAP ... LDAP is disabled in config/gitlab.yml checking LDAP ... Finished checking GitLab ... Git configured with autocrlf=input? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory setup correctly? ... yes Init script exists? ... yes Init script up-to-date? ... yes projects have namespace: ... Anshad Vattapoyil / test ... yes redis version >= 2.8.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.3.1) Your git bin path is "/usr/bin/git" Git version >= 2.7.3 ? ... yes (2.7.4) Active users: 1 checking GitLab ... Finished
针对域的Apache虚拟主机configuration，
<VirtualHost *:80> ServerAdmin anshad@mydomain.com ServerName gitlab.mydomain.com ServerAlias www.gitlab.mydomain.com ServerSignature Off ProxyPreserveHost On AllowEncodedSlashes NoDecode <LOCATIOn /> require all granted ProxyPassReverse http://localhost:8080 ProxyPassReverse http://gitlab.mydomain.com/ </LOCATIOn> RewriteENGIne on RewriteCond %{DOCUMENT_ROOT}/%{requEST_FILename} !-f [OR] RewriteCond %{requEST_URI} ^/uploads/.* RewriteRule .* http://127.0.0.1:8080%{requEST_URI} [P,QSA,NE] DocumentRoot /home/git/gitlab/public 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>
configuration/home/git/gitlab/config/gitlab.yml
production: &base gitlab: host: gitlab.mydomain.com port: 80 https: false trusted_proxies: email_from: noreply@mydomain.com email_display_name: GitLab email_reply_to: noreply@mydomain.com email_subject_suffix: '' default_projects_features: issues: true merge_requests: true wiki: true snippets: true builds: true container_registry: true incoming_email: enabled: false address: "gitlab-incoming+%{key}@gmail.com" user: "gitlab-incoming@gmail.com" password: "[REDACTED]" host: "imap.gmail.com" port: 993 ssl: true start_tls: false mailBox: "inBox" artifacts: enabled: true lfs: enabled: true gravatar: cron_jobs: stuck_ci_builds_worker: cron: "0 0 * * *" expire_build_artifacts_worker: cron: "50 * * * *" repository_check_worker: cron: "20 * * * *" admin_email_worker: cron: "0 0 * * 0" repository_archive_cache_worker: cron: "0 * * * *" registry: gitlab_ci: ldap: enabled: false servers: main: label: 'LDAP' host: '_your_ldap_server' port: 389 uid: 'sAMAccountName' method: 'plain' # "tls" or "ssl" or "plain" bind_dn: '_the_full_dn_of_the_user_you_will_bind_with' password: '_the_password_of_the_bind_user' timeout: 10 active_directory: true allow_username_or_email_login: false block_auto_created_users: false base: '' user_filter: '' attributes: username: ['uid','userid','sAMAccountName'] email: ['mail','email','userPrincipalName'] name: 'cn' first_name: 'givenName' last_name: 'sn' omniauth: enabled: false allow_single_sign_on: ["saml"] block_auto_created_users: true auto_link_ldap_user: false auto_link_saml_user: false external_providers: [] providers: shared: satellites: path: /home/git/gitlab-satellites/ repositories: storages: # you must have at least a `default` storage path. default: /home/git/repositories/ BACkup: path: "tmp/BACkups" gitlab_sHell: path: /home/git/gitlab-sHell/ hooks_path: /home/git/gitlab-sHell/hooks/ upload_pack: true receive_pack: true git: bin_path: /usr/bin/git max_size: 20971520 # 20.megabytes timeout: 10 extra: rack_attack: giT_Basic_auth:
在/home/git/gitlab/unicorn.rb ，我有
worker_processes 4 working_directory "/home/git/gitlab" # available in 0.94.0+ listen "/home/git/gitlab/tmp/sockets/gitlab.socket",:BACklog => 1024 listen "127.0.0.1:8080",:tcp_nopush => true
production.log只是说这个
Started POST "/ci/api/v1/builds/register.json" for 35.154.26.24 at 2016-11-19 08:16:45 +0000 Started GET "/anshad/test.git/info/refs?service=git-upload-pack" for 137.97.204.60 at 2016-11-19 08:16:47 +0000 Processing by Projects::GithttpController#info_refs as */* Parameters: {"service"=>"git-upload-pack","namespace_id"=>"anshad","project_id"=>"test.git"} Filter chain halted as :authenticate_user rendered or redirected Completed 401 Unauthorized in 23ms (Views: 0.3ms | ActiveRecord: 1.6ms) Started POST "/ci/api/v1/builds/register.json" for 35.154.26.24 at 2016-11-19 08:16:48 +0000 Started POST "/ci/api/v1/builds/register.json" for 35.154.26.24 at 2016-11-19 08:16:51 +0000 Started POST "/ci/api/v1/builds/register.json" for 35.154.26.24 at 2016-11-19 08:16:54 +0000 Started GET "/anshad/test.git/info/refs?service=git-upload-pack" for 137.97.204.60 at 2016-11-19 08:16:56 +0000 Processing by Projects::GithttpController#info_refs as */* Parameters: {"service"=>"git-upload-pack","project_id"=>"test.git"} Filter chain halted as :authenticate_user rendered or redirected Completed 401 Unauthorized in 25ms (Views: 0.3ms | ActiveRecord: 2.2ms) Started GET "/anshad/test.git/info/refs?service=git-upload-pack" for 137.97.204.60 at 2016-11-19 08:16:57 +0000 Processing by Projects::GithttpController#info_refs as */* Parameters: {"service"=>"git-upload-pack","project_id"=>"test.git"} Completed 500 Internal Server Error in 98ms (ActiveRecord: 3.1ms) JWT::DecodeError (Nil JSON web token): lib/gitlab/workhorse.rb:120:in `verify_api_request!' app/controllers/projects/git_http_client_controller.rb:154:in `verify_workhorse_api!' lib/gitlab/request_profiler/middleware.rb:15:in `call' lib/gitlab/middleware/go.rb:16:in `call' Started POST "/ci/api/v1/builds/register.json" for 35.154.26.24 at 2016-11-19 08:16:57 +0000
问题在GitLab
在离线模式下找不到服务工作者文件
PHP部门返回不同的结果（Linux / Windows）
.htaccess在根目录下的mod_rewrite，但需要它跳过所有其他目录
@H_174_0@mod_wsgi与Django应用程序的Apache错误需要注意的是，这个引用的系统是从源代码构建的，支持的Nginx被替换为Apache（没有官方的gitlab支持）。
这是交易 – 在我的系统上的标准Nginx配置我可以看到这一点
upstream gitlab-workhorse { server unix:/var/opt/gitlab/gitlab-workhorse/socket; } proxy_pass http://gitlab-workhorse;
这意味着 – 它使用套接字。 不是网络端口。 如果我试图看看主力甚至是在网络上听 – 我会看到它不是。
ps -ef|grep -i workhorse lsof -p pid
不会显示由workhorse pid打开的任何网络端口。 所以也许apache配置不正确？ 它应该使用套接字而不是端口？
首先，请仔细检查您的gitlab主版本，如果它与您当前的GitLab安装兼容。
在你提到的所有GitLab问题中， 22484的评论似乎是最有前途的：
在我的情况下，主力的日志显示访问./.gitlab_workhorse_secret错误
在一些挖掘之后，修正是将以下内容添加到/etc/systemd/system/gitlab-workhorse.service的主要启动命令行：
-secretPath /home/git/gitlab/.gitlab_workhorse_secret
作为参考，完整的ExecStart现在是：
ExecStart=/home/git/gitlab/bin/daemon_with_pidfile /home/git/gitlab/tmp/pids/gitlab-workhorse.pid /home/git/gitlab-workhorse/gitlab-workhorse -listenUmask 0 -listenNetwork unix -listenAddr /home/git/gitlab/tmp/sockets/gitlab-workhorse.socket -authBACkend http://127.0.0.1:8080 -authSocket /home/git/gitlab/tmp/sockets/gitlab.socket -documentRoot /home/git/gitlab/public -secretPath /home/git/gitlab/.gitlab_workhorse_secret >> /home/git/gitlab/log/gitlab-workhorse.log 2>&1
另一种可能性是：
在我的情况下，500错误是由/etc/gitlab/gitlab.rb错误的Nginx配置引起的。
如果我在Nginx之前有一些东西，比如在我的情况下haproxy。 我忽略了这个事实。 它在Nginx设置中进行了描述。
在我的情况下，在haproxy发送后端到8081现在正在监听Nginx（原来我设置了8080 – 默认的独角兽服务） –
我没有配置gitlab只有haproxy，没有Nginx图层。
所以在我的配置中很重要
Nginx['listen_port'] = 8081 Nginx['listen_https'] = false
请注意，这两个问题都是针对Nginx的（ 使用Apache2时有一个 ）
通过启用httpS和SSH克隆，我们能够解决403问题; 我们只启用了SSH克隆，这似乎是造成这个问题的原因。 这可以通过转到https:///admin/application_setTings和双重检查Enabled Git access protocols进行更改
这些结论在合并请求6843中进行了总结
但还有更多：
使用默认的配置文件示例（ init.d和Nginx ）， gitlab-workhorse将侦听Unix套接字而不是IP：端口。
Nginx示例配置文件对于Unix套接字确实有一些行，但代理传递到一个地址。
我想第一次设置gitlab我需要点我的Nginx配置到Unicorn端口绑定，因为它是我在开始gitlab服务时在Netstat中看到的唯一端口。
如果您将git clone请求发送给Unicorn，您将得到500错误。
我所要做的就是改变gitlab-workhorse来收听我的回头地址并指向Nginx。 这清除了我的http 500错误与克隆 。
查看更多关于GitLab Workhorse的简史
以上是大佬教程为你收集整理的git克隆与http不工作在gitlab全部内容，希望文章能够帮你解决git克隆与http不工作在gitlab所遇到的程序开发问题。
如果觉得大佬教程网站内容还不错，欢迎将大佬教程推荐给程序员好友。
本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ：384754419，请注明来意。