Home > The Requested > The Requested Url Returned Error 500 While Accessing

The Requested Url Returned Error 500 While Accessing

I can imagine that that limit is there to prevent flood-attacks on the webserver..?? can you explain why http URL has not worked. –John Liva Oct 13 '15 at 12:01 Can you still reproduce the previous error? Cheers, CharlesBlakeMay 16, 2013It seems like this was a git configuration issue. Username for 'https://github.xxxxxx.com': yyyyy Password for 'https://[email protected]': remote: Internal Server Error. check my blog

So the https-requests from the git-client are reaching the `gitlab-git-http-server`, since my `gitlab-git-http-server.log` file is full with lines like ``` 2015/10/01 21:40:16 GET "/omkelderman/testproject.git/info/refs?service=git-upload-pack" ``` Same goes for my access.log of uniquechao 2015-12-15 09:45:00 UTC #28 Hi @arecio ok, thx. Terms Privacy Security Status Help You can't perform that action at this time. How do I respond to the inevitable curiosity and protect my workplace reputation? http://stackoverflow.com/questions/33086132/i-am-getting-500-error-on-git-clone

As soon as the new version is ready, I'll let you know. i could not find error on production.log or Apache error log. DmitriyLyalyuev commented May 17, 2013 $ git clone https://gitlab.example.com/foo.git Cloning into 'foo'...

I am getting below error. $ git clone https://github.xxxxx.com/zzzzzz.git Cloning into 'zzzzzz'... If I am told a hard percentage and don't get it, should I look elsewhere? gitlab_url: "http://some.server:80/" http_settings: # user: someone # password: somepass self_signed_cert: false # Repositories path repos_path: "/home/git/repositories" # File used as authorized_keys for gitlab user auth_file: "/home/git/.ssh/authorized_keys" # Redis settings used for We will also fix this in our Bitnami GitLab stack as soon as possible. @TopKool, could you remove those lines, before following these instructions?

Not sure if that is already possible... Yes. Sign in GitLab.org / gitlab-git-http-server Go to a project Toggle navigation Toggle navigation pinning Projects Groups Snippets Help Project Activity Repository Pipelines Graphs Issues 0 Merge Requests 0 Wiki Network Create A reinstall of git has solved the issue.

Stash supports "smart HTTP", but will return a 501 for normal HTTP. Thanks a lot for the solution. The file you have to edit is: /opt/bitnami/apps/gitlab-workhorse/scripts/ctl.sh marcos 2015-12-31 16:09:32 UTC #39 Hi all, We have released a new revision of the Bitnami GitLab Stack that fixes this issue, the Report a bug Atlassian News Atlassian Atlassian Documentation  Log in Stash Knowledge Base Git commands return error code 501 Symptoms When pulling from, pushing or cloning to Stash, it responds

I'm getting 500 errors when I'm trying to clone repositories via https 2016-06-16T02:17:40+00:00 mahrizal ayah anam Same wiith me 2016-06-16T02:19:29+00:00 Nabil Freeman yeah unfortunately i'm having this problem too! https://confluence.atlassian.com/stashkb/git-commands-return-error-code-501-282988872.html Regards. basic HTML tags are also supported learn more about Markdown Question tags: error ×104 git ×103 http ×24 500 ×19 question asked: 06 Apr '11, 11:42 question was seen: 10,396 times Used for api calls.

I recommend contacting them and explain what the problem is. click site My colleagues here are not though 2015-10-15T03:31:26+00:00 Victor Cardins It seems to be a temporary issue. error: The requested URL returned error: 501 while accessing url fatal: HTTP request failed Or it may respond with a error code 22: $ git push url error: Cannot access URL Is it dangerous to use default router admin passwords if only trusted users are allowed on the network?

tomasp 2015-12-22 15:15:49 UTC #30 Hi , We have released a new version of GitLab that solves these issues (Version 8.2.3-0). Started GET "/foo.git/info/refs?service=git-upload-pack" for at 2013-05-17 08:11:57 -0700 Errno::EACCES (Permission denied - /scratch/git178 upload-pack --stateless-rpc --advertise-refs .): lib/gitlab/backend/grack_auth.rb:24:in `call' sroth80021 commented May 17, 2013 Diffing between the 5.0 and 5.1 Otherwise it's unreadable. news git by default user: git # Url to gitlab instance.

Not sure if that is already possible... And maybe I could tweak some nginx-settings to allow more.. Everything except public HTTP access seems to work fine. In the second case, you can just try the command again.

I have the same while push, pull, clone via HTTPS in all repos error: The requested URL returned error: 500 while accessing https://[email protected]/repo.git/info/refs?service=git-receive-pack fatal: HTTP request failed Thank you. 2013-08-27T11:32:12+00:00 Krzysiek

When the new version is ready, we will let you know. You could download at https://bitnami.com/stack/gitlab Please let us know if you have any issues with this version. Olle Kelderman @omkelderman commented 2015-10-02 16:13:17 UTC hmm, well, I kinda do not agree, but I can understand.. You signed out in another tab or window.

FWIW, for gitlab-shell config.yml, I first tried the default gitlab_url of: "http://localhost:9292/", but that had the same issue (when cloning via public HTTP -- clones over [email protected] were fine) sroth80021 commented When bitnami update and may be solve this issue. But like I said before, I don't like to use TCP-ports for things that are basically just internal connections. So yes, I am fully aware of that solution. But it is also the More about the author The reason is unclear so far.

So I need to rebuild/reinstall a newer git version in a different way than the way I had done it. Thanks! 2016-06-16T02:28:42+00:00 Philippe Theunissen fixed indeed :) 2016-06-16T02:31:22+00:00 Dominic Cerisano Fixed. This works completely fine and always has been. So when this gitlab-git-http-server thing got added to gitlab, I thought, lets do the same for this (cause obviously it didnt work since it Does anyone have a clue? (07 Apr '11, 02:45) Dominique Eav 2 Answers: active answersoldest answersnewest answerspopular answers 0 The webfaction support team found out what the problem was: blank lines

Fixed issue cloning repositories by continuous integrations runners. Yes No Thanks for your feedback!