Fatal error when git push or pull to web app Local Git from App Service

Question

Fatal error when git push or pull to web app Local Git from App Service

AmirulAbdullah-6396 0

Fatal error when clone Local Git from App Service

I'm having fatal error whenever i'm trying to clone or push to app service. It was working fine before. Suddenly i couldn't even clone the git locally.

Below is debug trace when i git clone, i'm sure i use the correct username and password.

git clone --verbose https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git 
07:31:58.552836 exec-cmd.c:139          trace: resolved executable path from Darwin stack: /Applications/Xcode.app/Contents/Developer/usr/bin/git
07:31:58.553658 exec-cmd.c:238          trace: resolved executable dir: /Applications/Xcode.app/Contents/Developer/usr/bin
07:31:58.554423 git.c:460               trace: built-in: git clone --verbose https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git
Cloning into 'impact4c-prod'...
07:31:58.562522 run-command.c:654       trace: run_command: git remote-https origin https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git
07:31:58.565180 exec-cmd.c:139          trace: resolved executable path from Darwin stack: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git
07:31:58.565502 exec-cmd.c:238          trace: resolved executable dir: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core
07:31:58.565727 git.c:749               trace: exec: git-remote-https origin https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git
07:31:58.565735 run-command.c:654       trace: run_command: git-remote-https origin https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git
07:31:58.569652 exec-cmd.c:139          trace: resolved executable path from Darwin stack: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git-remote-https
07:31:58.570055 exec-cmd.c:238          trace: resolved executable dir: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core
07:31:58.571356 http.c:678              == Info: Couldn't find host impact4c-prod.scm.azurewebsites.net in the (nil) file; using defaults
07:31:58.656869 http.c:678              == Info:   Trying 20.43.132.130:443...
07:31:58.671798 http.c:678              == Info: Connected to impact4c-prod.scm.azurewebsites.net (20.43.132.130) port 443 (#0)
07:31:58.671915 http.c:678              == Info: ALPN: offers h2
07:31:58.671922 http.c:678              == Info: ALPN: offers http/1.1
07:31:58.678489 http.c:678              == Info:  CAfile: /etc/ssl/cert.pem
07:31:58.678506 http.c:678              == Info:  CApath: none
07:31:58.678860 http.c:678              == Info: (304) (OUT), TLS handshake, Client hello (1):
07:31:58.698858 http.c:678              == Info: (304) (IN), TLS handshake, Server hello (2):
07:31:58.698930 http.c:678              == Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
07:31:58.700088 http.c:678              == Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
07:31:58.700277 http.c:678              == Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
07:31:58.706805 http.c:678              == Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
07:31:58.706830 http.c:678              == Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
07:31:58.706861 http.c:678              == Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
07:31:58.723225 http.c:678              == Info: TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
07:31:58.723293 http.c:678              == Info: TLSv1.2 (IN), TLS handshake, Finished (20):
07:31:58.723305 http.c:678              == Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
07:31:58.723307 http.c:678              == Info: ALPN: server accepted h2
07:31:58.723313 http.c:678              == Info: Server certificate:
07:31:58.723324 http.c:678              == Info:  subject: C=US; ST=WA; L=Redmond; O=Microsoft Corporation; CN=*.azurewebsites.net
07:31:58.723328 http.c:678              == Info:  start date: Dec 27 21:12:39 2022 GMT
07:31:58.723330 http.c:678              == Info:  expire date: Dec 22 21:12:39 2023 GMT
07:31:58.723342 http.c:678              == Info:  subjectAltName: host "impact4c-prod.scm.azurewebsites.net" matched cert's "*.scm.azurewebsites.net"
07:31:58.723348 http.c:678              == Info:  issuer: C=US; O=Microsoft Corporation; CN=Microsoft Azure TLS Issuing CA 05
07:31:58.723350 http.c:678              == Info:  SSL certificate verify ok.
07:31:58.723364 http.c:678              == Info: Using HTTP2, server supports multiplexing
07:31:58.723368 http.c:678              == Info: Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
07:31:58.723458 http.c:678              == Info: h2h3 [:method: GET]
07:31:58.723464 http.c:678              == Info: h2h3 [:path: /impact4c-prod.git/info/refs?service=git-upload-pack]
07:31:58.723465 http.c:678              == Info: h2h3 [:scheme: https]
07:31:58.723467 http.c:678              == Info: h2h3 [:authority: impact4c-prod.scm.azurewebsites.net]
07:31:58.723468 http.c:678              == Info: h2h3 [user-agent: git/2.37.1 (Apple Git-137.1)]
07:31:58.723470 http.c:678              == Info: h2h3 [accept: */*]
07:31:58.723471 http.c:678              == Info: h2h3 [accept-encoding: deflate, gzip]
07:31:58.723472 http.c:678              == Info: h2h3 [pragma: no-cache]
07:31:58.723475 http.c:678              == Info: h2h3 [git-protocol: version=2]
07:31:58.723478 http.c:678              == Info: Using Stream ID: 1 (easy handle 0x15181bc00)
07:31:58.723497 http.c:625              => Send header, 0000000240 bytes (0x000000f0)
07:31:58.723500 http.c:637              => Send header: GET /impact4c-prod.git/info/refs?service=git-upload-pack HTTP/2
07:31:58.723502 http.c:637              => Send header: Host: impact4c-prod.scm.azurewebsites.net
07:31:58.723503 http.c:637              => Send header: user-agent: git/2.37.1 (Apple Git-137.1)
07:31:58.723506 http.c:637              => Send header: accept: */*
07:31:58.723507 http.c:637              => Send header: accept-encoding: deflate, gzip
07:31:58.723508 http.c:637              => Send header: pragma: no-cache
07:31:58.723510 http.c:637              => Send header: git-protocol: version=2
07:31:58.723511 http.c:637              => Send header:
07:31:58.748003 http.c:625              <= Recv header, 0000000013 bytes (0x0000000d)
07:31:58.748024 http.c:637              <= Recv header: HTTP/2 401
07:31:58.748027 http.c:625              <= Recv header, 0000000037 bytes (0x00000025)
07:31:58.748028 http.c:637              <= Recv header: date: Thu, 30 Mar 2023 23:31:58 GMT
07:31:58.748030 http.c:625              <= Recv header, 0000000038 bytes (0x00000026)
07:31:58.748032 http.c:637              <= Recv header: www-authenticate: Basic realm="site"
07:31:58.748034 http.c:625              <= Recv header, 0000000019 bytes (0x00000013)
07:31:58.748035 http.c:637              <= Recv header: content-length: 0
07:31:58.748037 http.c:625              <= Recv header, 0000000002 bytes (0x00000002)
07:31:58.748038 http.c:637              <= Recv header:
07:31:58.748048 http.c:678              == Info: Connection #0 to host impact4c-prod.scm.azurewebsites.net left intact
07:31:58.748070 run-command.c:654       trace: run_command: 'git credential-osxkeychain get'
07:31:58.756665 exec-cmd.c:139          trace: resolved executable path from Darwin stack: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git
07:31:58.757016 exec-cmd.c:238          trace: resolved executable dir: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core
07:31:58.757216 git.c:749               trace: exec: git-credential-osxkeychain get
07:31:58.757222 run-command.c:654       trace: run_command: git-credential-osxkeychain get
Username for 'https://impact4c-prod.scm.azurewebsites.net:443': markom
Password for 'https://******@impact4c-prod.scm.azurewebsites.net:443': 
07:32:18.098349 http.c:678              == Info: Found bundle for host: 0x600003f0cf00 [can multiplex]
07:32:18.100467 http.c:678              == Info: Re-using existing connection #0 with host impact4c-prod.scm.azurewebsites.net
07:32:18.100479 http.c:678              == Info: Connected to impact4c-prod.scm.azurewebsites.net (20.43.132.130) port 443 (#0)
07:32:18.100527 http.c:678              == Info: Server auth using Basic with user 'markom'
07:32:18.100558 http.c:678              == Info: h2h3 [:method: GET]
07:32:18.100562 http.c:678              == Info: h2h3 [:path: /impact4c-prod.git/info/refs?service=git-upload-pack]
07:32:18.100565 http.c:678              == Info: h2h3 [:scheme: https]
07:32:18.100569 http.c:678              == Info: h2h3 [:authority: impact4c-prod.scm.azurewebsites.net]
07:32:18.100572 http.c:678              == Info: h2h3 [authorization: Basic bWFya29tOkxbY35APH1IZSY4Tg==]
07:32:18.100576 http.c:678              == Info: h2h3 [user-agent: git/2.37.1 (Apple Git-137.1)]
07:32:18.100579 http.c:678              == Info: h2h3 [accept: */*]
07:32:18.101525 http.c:678              == Info: h2h3 [accept-encoding: deflate, gzip]
07:32:18.101544 http.c:678              == Info: h2h3 [pragma: no-cache]
07:32:18.101546 http.c:678              == Info: h2h3 [git-protocol: version=2]
07:32:18.101566 http.c:678              == Info: Using Stream ID: 3 (easy handle 0x15181bc00)
07:32:18.101680 http.c:625              => Send header, 0000000291 bytes (0x00000123)
07:32:18.101690 http.c:637              => Send header: GET /impact4c-prod.git/info/refs?service=git-upload-pack HTTP/2
07:32:18.101693 http.c:637              => Send header: Host: impact4c-prod.scm.azurewebsites.net
07:32:18.101695 http.c:637              => Send header: authorization: Basic <redacted>
07:32:18.101696 http.c:637              => Send header: user-agent: git/2.37.1 (Apple Git-137.1)
07:32:18.101697 http.c:637              => Send header: accept: */*
07:32:18.101698 http.c:637              => Send header: accept-encoding: deflate, gzip
07:32:18.101699 http.c:637              => Send header: pragma: no-cache
07:32:18.101701 http.c:637              => Send header: git-protocol: version=2
07:32:18.101702 http.c:637              => Send header:
07:32:18.474172 http.c:625              <= Recv header, 0000000013 bytes (0x0000000d)
07:32:18.474204 http.c:637              <= Recv header: HTTP/2 401
07:32:18.474209 http.c:625              <= Recv header, 0000000037 bytes (0x00000025)
07:32:18.474219 http.c:637              <= Recv header: date: Thu, 30 Mar 2023 23:32:17 GMT
07:32:18.474224 http.c:678              == Info: Authentication problem. Ignoring this.
07:32:18.474228 http.c:625              <= Recv header, 0000000038 bytes (0x00000026)
07:32:18.474231 http.c:637              <= Recv header: www-authenticate: Basic realm="site"
07:32:18.474235 http.c:625              <= Recv header, 0000000019 bytes (0x00000013)
07:32:18.474238 http.c:637              <= Recv header: content-length: 0
07:32:18.474242 http.c:625              <= Recv header, 0000000002 bytes (0x00000002)
07:32:18.474245 http.c:637              <= Recv header:
07:32:18.474266 http.c:678              == Info: Connection #0 to host impact4c-prod.scm.azurewebsites.net left intact
07:32:18.474291 run-command.c:654       trace: run_command: 'git credential-osxkeychain erase'
07:32:18.487872 exec-cmd.c:139          trace: resolved executable path from Darwin stack: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core/git
07:32:18.488650 exec-cmd.c:238          trace: resolved executable dir: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core
07:32:18.489602 git.c:749               trace: exec: git-credential-osxkeychain erase
07:32:18.489616 run-command.c:654       trace: run_command: git-credential-osxkeychain erase
fatal: Authentication failed for 'https://impact4c-prod.scm.azurewebsites.net:443/impact4c-prod.git/'

AmirulAbdullah-6396 0 Reputation points

2023-03-31T02:56:12.78+00:00

My apologies, it use due to wrong password. and i can't seem to find a way to delete this post
My KineMaster 0 Reputation points

2023-03-31T03:33:09.8533333+00:00

Based on the provided debug trace, it seems that there is a successful connection between your local Git client and the remote Git repository. The trace shows that Git has successfully resolved the executable path, built the clone command, and initiated a connection to the remote repository. The TLS handshake was completed successfully, and the server has accepted the connection.

Since the error message is not provided, it is difficult to determine the cause of the issue. However, some possible causes of Git push or clone failures are:

Authentication issues: Git may not have the correct credentials to access the repository. Check if your username and password are correct.

Network issues: There may be network issues or restrictions that are preventing your Git client from accessing the repository. Check if you can access the repository from another network or machine.

Permission issues: You may not have the necessary permissions to access or modify the repository. Check if you have the appropriate permissions.

Repository issues: The repository may be corrupted or have a configuration issue. Check if other users can access the repository, or try creating a new repository.

To resolve the issue, you can try the following:

Check if your Git credentials are correct. Try resetting your password, and then try cloning or pushing to the repository again.

Try accessing the repository from another network or machine to rule out network issues.

Check if you have the appropriate permissions to access or modify the repository. If not, contact the repository owner or administrator to grant you the necessary permissions.

Try creating a new repository and pushing to it to rule out repository issues. If successful, the issue may be with the original repository, and you may need to contact the repository owner or administrator to resolve it.

1 answer

Your answer

AmirulAbdullah-6396 0 Reputation points

2023-03-31T02:56:12.78+00:00

My apologies, it use due to wrong password. and i can't seem to find a way to delete this post
My KineMaster 0 Reputation points

2023-03-31T03:33:09.8533333+00:00

Based on the provided debug trace, it seems that there is a successful connection between your local Git client and the remote Git repository. The trace shows that Git has successfully resolved the executable path, built the clone command, and initiated a connection to the remote repository. The TLS handshake was completed successfully, and the server has accepted the connection.

Since the error message is not provided, it is difficult to determine the cause of the issue. However, some possible causes of Git push or clone failures are:

Authentication issues: Git may not have the correct credentials to access the repository. Check if your username and password are correct.

Network issues: There may be network issues or restrictions that are preventing your Git client from accessing the repository. Check if you can access the repository from another network or machine.

Permission issues: You may not have the necessary permissions to access or modify the repository. Check if you have the appropriate permissions.

Repository issues: The repository may be corrupted or have a configuration issue. Check if other users can access the repository, or try creating a new repository.

To resolve the issue, you can try the following:

Check if your Git credentials are correct. Try resetting your password, and then try cloning or pushing to the repository again.

Try accessing the repository from another network or machine to rule out network issues.

Check if you have the appropriate permissions to access or modify the repository. If not, contact the repository owner or administrator to grant you the necessary permissions.

Try creating a new repository and pushing to it to rule out repository issues. If successful, the issue may be with the original repository, and you may need to contact the repository owner or administrator to resolve it.

Answer 1

Hi @AmirulAbdullah-6396

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:

You were getting a fatal error whenever you tried cloning or pushing to app service and couldn't clone the git locally.

Solution: You resolved the issue by using the correct password.

Thanks again for sharing what worked for you.

Best,

Grace

Share via

Fatal error when git push or pull to web app Local Git from App Service

Fatal error when clone Local Git from App Service

1 answer

Your answer