Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GitLab HTTP: cannot access repository for push #673

Closed
panatolii opened this issue Jul 21, 2016 · 3 comments · Fixed by turnkeylinux-apps/gitlab#17
Closed

GitLab HTTP: cannot access repository for push #673

panatolii opened this issue Jul 21, 2016 · 3 comments · Fixed by turnkeylinux-apps/gitlab#17
Assignees
Milestone

Comments

@panatolii
Copy link

Hi all,
I have error on HTTP push:
error: Cannot access URL http://{git-url}/gitlab-admin/test.git/, return code 22 fatal: git-http-push failed

production.log:
ActionController::RoutingError (No route matches [PROPFIND] "/gitlab-admin/test.git"):
vendor/bundle/ruby/2.1.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' vendor/bundle/ruby/2.1.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:incall'
vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in call_app' vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:20:inblock in call'
vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.6/lib/active_support/tagged_logging.rb:68:in block in tagged' vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.6/lib/active_support/tagged_logging.rb:26:intagged'
vendor/bundle/ruby/2.1.0/gems/activesupport-4.2.6/lib/active_support/tagged_logging.rb:68:in tagged' vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:20:incall'
vendor/bundle/ruby/2.1.0/gems/request_store-1.3.0/lib/request_store/middleware.rb:9:in call' vendor/bundle/ruby/2.1.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:incall'
vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in call' vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:incall'
vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/lock.rb:17:in call' vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:incall'
vendor/bundle/ruby/2.1.0/gems/sentry-raven-0.15.6/lib/raven/integrations/rack.rb:53:in call' vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/engine.rb:518:incall'
vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/application.rb:165:in call' vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:inpublic_send'
vendor/bundle/ruby/2.1.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in method_missing' vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:inblock in call'
vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in each' vendor/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:incall'
vendor/bundle/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:580:in process_client' vendor/bundle/ruby/2.1.0/gems/unicorn-worker-killer-0.4.4/lib/unicorn/worker_killer.rb:52:inprocess_client'
vendor/bundle/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:674:in worker_loop' vendor/bundle/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:529:inspawn_missing_workers'
vendor/bundle/ruby/2.1.0/gems/unicorn-4.9.0/lib/unicorn/http_server.rb:140:in start' vendor/bundle/ruby/2.1.0/gems/unicorn-4.9.0/bin/unicorn_rails:209:in<top (required)>'
vendor/bundle/ruby/2.1.0/bin/unicorn_rails:23:in load' vendor/bundle/ruby/2.1.0/bin/unicorn_rails:23:in

'

@panatolii panatolii changed the title HTTP: cannot access repository for push GitLab HTTP: cannot access repository for push Jul 21, 2016
@JedMeister JedMeister added this to the 14.2 milestone Jul 21, 2016
@JedMeister
Copy link
Member

Thanks for your report. Can you confirm that you are using the latest (v14.1) appliance? If you're not sure, just post the output of turnkey-version

@panatolii
Copy link
Author

Yes, I confirm that use last version (v14.1)

@JedMeister
Copy link
Member

Great thanks! 👍

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants