I am unable to clone a newly created repository. I am getting below error.
$ git clone https://github.xxxxx.com/zzzzzz.git
Cloning into 'zzzzzz'...
Username for 'https://github.xxxxxx.com': yyyyy
Password for 'https://yyyyy@github.xxxxxx.com':
remote: Internal Server Error.
remote:
fatal: unable to access 'https://github.xxxxxx.com/zzzzz.git/': The requested URL returned error: 500
I have successfully generated ssh keys and updated the key in github settings as per the instructions in the below URL
https://help.github.com/articles/generating-ssh-keys/
authentication was success when I executed the command:
git -T git@github.xxx.com
Also as per my understanding if we setup the ssh the git clone command should not ask for username and password. But it still asking for them.
debug1: Authentication succeeded (publickey).
Authenticated to github.xxxxx.com ([10.28.22.44]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Hi xxxx! You've successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3880, received 1696 bytes, in 0.2 seconds
Bytes per second: sent 19132.2, received 8363.0
debug1: Exit status 1
asked Oct 12, 2015 at 16:39
Rob WilkinsonRob Wilkinson
1,1214 gold badges18 silver badges32 bronze badges
6
This is most probably a problem with GitHub service. I recommend contacting them and explain what the problem is.
This is how Wikipedia explains the 500 response code:
500 Internal Server Error
A generic error message, given when an unexpected condition was
encountered and no more specific message is suitable.
Basically, something went wrong on the GitHub endpoint.
But, since you already have set your SSH keys, you can use the ssh url to clone your repository:
git clone git@github.com:owner/repo.git
answered Oct 13, 2015 at 12:05
Ionică BizăuIonică Bizău
108k87 gold badges284 silver badges468 bronze badges
I have the same problem, but in GitLab, and the answer to the problem is that GitLabis make a deploy.
Deploy in progress
Please try again in a few minutes.
Please contact your GitLab administrator if this problem persists.
So I was connected in a some hours and it is works.
Muhammad Reda
26.2k14 gold badges92 silver badges104 bronze badges
answered May 1, 2017 at 8:02
try with connecting to VPN (at least try with 2 different locations) this worked for me. I was having the same problem
answered Sep 5, 2021 at 3:37
2
Hi,
I am trying to access repositories hosted on GitHub from GitHub Desktop.
Still facing the same issue.
Regards,
Spoorthi
…
________________________________
From: Steve Ward <notifications@github.com>
Sent: Wednesday, August 26, 2020 7:25:23 PM
To: desktop/desktop
Cc: Spoorthi Vasantharaju; Mention
Subject: Re: [desktop/desktop] Github giving fatal error 500 when performing any operation (#10450)
@SpoorthiVasanth<https://github.com/SpoorthiVasanth> thanks for the report. Are you attempting to access repositories hosted on GitHub from GitHub Desktop, or is this a GitHub Enterprise instance? A 500 error indicates an external server issue — not a specific issue with GitHub Desktop.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#10450 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKGKC4KXLTCEC75Z7G7R6ODSCUH4XANCNFSM4QLPCZHA>.
The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.
I am trying to push my changes in my GitHub with VS code But I am facing the following error: Git: Bad status code: 500 in Vs Code. In this Exerror article, We are going to learn about How to reproduce this error and we will discuss All Possible Solutions Lets Get Start with This Article.
Contents
- How Git: Bad status code: 500 Error Occurs?
- How To Solve Git: Bad status code: 500 Error?
- Solution 1: Add this setting
- Solution 2: Checkmark this box
- Conclusion
How Git: Bad status code: 500 Error Occurs?
I am trying to push my changes in my GitHub with VS code But I am facing the following error.
Git: Bad status code: 500So here I am writing all the possible solutions that I have tried to resolve this error.
How To Solve Git: Bad status code: 500 Error?
- How To Solve Git: Bad status code: 500 Error?
To Solve Git: Bad status code: 500 Error First of All Open Your VS Studio Setting By Clicking On File -> Preferences -> Settings Or If You are Using Windows Then Simply Press Ctrl + Comma ( , ). Now In Search Bar Type : git: use editor as commit input Then, You can See the First Option Named Git : Use Editor As Commit Input there And Tick Mark Control Whether a full text editor will be used to author commit messages, Whenever no message is Provided in the commit input box. And Now Retry to commit and Push And Your error must be solved. Thank you.
- Git: Bad status code: 500
To Solve Git: Bad status code: 500 Error First of All Open Your VS Studio Setting By Clicking On File -> Preferences -> Settings Or If You are Using Windows Then Simply Press Ctrl + Comma ( , ). Now In Search Bar Type : git: use editor as commit input Then, You can See the First Option Named Git : Use Editor As Commit Input there And Tick Mark Control Whether a full text editor will be used to author commit messages, Whenever no message is Provided in the commit input box. And Now Retry to commit and Push And Your error must be solved. Thank you.
Solution 1: Add this setting
- First of All Open Your VS Studio Setting By Clicking On File -> Preferences -> Settings
- Or If You are Using Windows Then Simply Press Ctrl + Comma ( , ).
- Now In Search Bar Type : git: use editor as commit input
- Then, You can See the First Option Named Git : Use Editor As Commit Input there
- And Tick Mark Control Whether a full text editor will be used to author commit messages, Whenever no message is Provided in the commit input box.
- And Now Retry to commit and Push And Your error must be solved.
- Thank you.
Solution 2: Checkmark this box
Check Mark This Box And your error must be solved.
Conclusion
It’s all About this error. I hope We Have solved Your error. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?
Also, Read
- refers to a value, but is being used as a type here TS2749 in Reactjs
- Module not found: Can’t resolve ‘fs’
- Error: Cannot find module ‘express’
- TypeError: missing 2 required positional arguments
- ReferenceError: __dirname is not defined in ES module scope
Problem:
Today I open Vscode and trying to commit changes in my github repository and suddenly I am facing the following error.
Git: Bad status code: 500Solution:
To solve the problem go to VSCode settings and search for git: use editor as commit input.
An option with tick box will appear infront of you then if that option is on just turn it off as same as the picture below-
Thank you for reading the article. For any other query feel free to contact with us.
Still now problem not solved?
We want to help you to solve your problems. It’s totally free. We have experienced developers team. We’ll assign our team member to help you. Contact us now!
EDIT: It also happens with pulls.
Summary
Just upgraded to 12.2 and getting random 500 errors when using git and pulling/pushing to a project using HTTPS.
Steps to reproduce
Try to pull any repository using HTTPS on http://lab.shelter.moe (self-hosted gitlab) or push to one you created there.
What is the current bug behavior?
Git commands fail with a 500 error. These errors are random as, when you try pushing again, and again, it sometimes fails during the push, and sometimes the push succeeds.
See this terminal log for an example :
$ git push -u origin master
fatal: unable to access 'https://lab.shelter.moe/axelterizaki/ultrastar2ass.git/': The requested URL returned error: 500
$ git push -u origin master
fatal: unable to access 'https://lab.shelter.moe/axelterizaki/ultrastar2ass.git/': The requested URL returned error: 500
$ git push -u origin master
Counting objects: 24, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (19/19), done.
Writing objects: 100% (24/24), 25.73 KiB | 0 bytes/s, done.
Total 24 (delta 1), reused 0 (delta 0)
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500 Internal Server Error
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
$ git push -u origin master
fatal: unable to access 'https://lab.shelter.moe/axelterizaki/ultrastar2ass.git/': The requested URL returned error: 500
$ git push -u origin master
fatal: unable to access 'https://lab.shelter.moe/axelterizaki/ultrastar2ass.git/': The requested URL returned error: 500
$ git push -u origin master
Counting objects: 24, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (19/19), done.
Writing objects: 100% (24/24), 25.73 KiB | 0 bytes/s, done.
Total 24 (delta 1), reused 0 (delta 0)
To https://lab.shelter.moe/axelterizaki/ultrastar2ass.git
* [new branch] master -> master
Branch master set up to track remote branch master from origin.What is the expected correct behavior?
It should be working all right as in 12.1.x
This happened ever since I upgraded Omnibus gitlab to 12.2 this morning.
Relevant logs and/or screenshots
I examined the production.log and here’s what I found when trying a git push :
Started GET "/axelterizaki/ultrastar2ass.git/info/refs?service=git-receive-pack" for 192.168.122.1 at 2019-08-23 12:55:18 +0200
Processing by Gitlab::RequestForgeryProtection::Controller#index as */*
Parameters: {"service"=>"git-receive-pack"}
Completed 200 OK in 0ms (ActiveRecord: 0.0ms)
Redis::CommandError (ERR value is not an integer or out of range):
lib/peek/views/redis_detailed.rb:10:in `call'
lib/gitlab/middleware/read_only/controller.rb:40:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:26:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:29:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'Here it says it returned a 200, but my Apache frontend server returns a 500 instead :
xx.xxx.xx.xxx - - [23/Aug/2019:13:03:05 +0200] "GET /axelterizaki/ultrastar2ass.git/info/refs?service=git-receive-pack HTTP/1.1" 500 3228 "-" "git/2.19.0.windows.1"I’m not sure what’s wrong but I guess the Redis error in production.log has something to do with it.
Output of checks
See below
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 16.04 Current User: git Using RVM: no Ruby Version: 2.6.3p62 Gem Version: 2.7.9 Bundler Version:1.17.3 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.22.0 Sidekiq Version:5.2.7 Go Version: unknown
GitLab information Version: 12.2.0 Revision: 1c1d47c5974 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 10.9 URL: https://lab.shelter.moe HTTP Clone URL: https://lab.shelter.moe/some-group/some-project.git SSH Clone URL: git@shelter.mahoro-net.org:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: gitlab, google_oauth2, twitter, github
GitLab Shell Version: 9.3.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Checking Reply by email ...
IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 5/2 ... yes 2/4 ... yes 1/6 ... yes 1/7 ... yes 1/8 ... yes 7/9 ... yes 19/10 ... yes 4/11 ... yes 22/12 ... yes 156/13 ... yes 15/14 ... yes 8/15 ... yes 5/18 ... yes 45/22 ... yes 156/23 ... yes 52/24 ... yes 52/25 ... yes 59/26 ... yes 155/28 ... yes 62/32 ... yes 62/33 ... yes 52/34 ... yes 155/35 ... yes 5/36 ... yes 54/40 ... yes 67/41 ... yes 67/43 ... yes 67/44 ... yes 156/45 ... yes 65/46 ... yes 66/47 ... yes 82/52 ... yes 96/55 ... yes 82/59 ... yes 8/65 ... yes 7/66 ... yes 5/67 ... yes 5/68 ... yes 82/69 ... yes 20/70 ... yes 45/71 ... yes 110/72 ... yes 82/73 ... yes 8/74 ... yes 8/75 ... yes 8/76 ... yes 156/77 ... yes 9/80 ... yes 66/81 ... yes 78/83 ... yes 1/87 ... yes 135/89 ... yes 126/90 ... yes 135/91 ... yes 135/92 ... yes 135/93 ... yes 1/98 ... yes 153/99 ... yes 155/100 ... yes 155/101 ... yes 5/102 ... yes 20/104 ... yes 8/106 ... yes 45/107 ... yes 102/109 ... yes 129/110 ... yes 5/111 ... yes 9/112 ... yes 198/113 ... yes 102/114 ... yes 198/115 ... yes 193/116 ... yes 202/117 ... yes 45/118 ... yes 135/119 ... yes 107/120 ... yes 107/121 ... yes 20/123 ... yes 5/129 ... yes 135/130 ... yes 5/131 ... yes 52/132 ... yes 1/133 ... yes 1/134 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.3) Git version >= 2.22.0 ? ... yes (2.22.0) Git user has default SSH configuration? ... yes Active users: ... 196
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
For now my only possible workaround is to migrate back to an older version (12.1) where this didn’t happen.