others-how to solve 'SSL_ERROR_SYSCALL in connection to github.com:443 ' when pushing code to github.com?

1. Purpose

In this post, I would demo how to solve the below error when we trying to push code using git to github.com.

➜  bswen-springboot24 git:(main) git push         
fatal: unable to access 'https://github.com/bswen/bswen-springboot24.git/': LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 

This error usually means that a system call error occurred while trying to establish an SSL connection. This can be caused by a variety of reasons, including network problems, proxy settings, SSL certificate problems, etc.

2. Environment

  • Mac OS or Linux System

3. The basics

The SSL_ERROR_SYSCALL error is an issue that can occur when using Git commands on a Linux system, particularly when interacting with remote repositories over HTTPS. This error is related to the SSL/TLS handshake process during a connection attempt and indicates that a system-level call has failed unexpectedly. Here’s an introduction to the error and some common approaches to resolving it:


SSL_ERROR_SYSCALL typically happens when the TCP connection between the client (your Git client) and the server (e.g., GitHub) has been established, but then a TCP reset packet (often written as “RST”) is received by the client during the SSL handshake phase, causing the connection to be terminated prematurely.

Common Causes:

  1. Network Issues: Unstable or interrupted network connections can lead to this error.
  2. Firewalls or Proxies: Network configurations, including firewalls or proxy settings, might interfere with the SSL handshake.
  3. SSL Library Issues: There might be problems with the SSL library being used by Git (e.g., OpenSSL or LibreSSL).
  4. Git Configuration: Incorrect Git configuration settings related to SSL can also cause this error.

4. The solution

4.1 What does this error mean?

SSL_ERROR_SYSCALL indicates that some problem happened with the underlying I/O (Should be TCP in this case).

4.2 Troubleshooting Steps

  1. Check Network Connection: Ensure you have a stable internet connection and can access other HTTPS sites without issues.

  2. Disable Proxy: If you are behind a proxy, try disabling it temporarily to see if that resolves the issue. You can unset Git’s proxy settings using:
    git config --global --unset http.proxy
    git config --global --unset https.proxy
  3. Change SSL Backend: If you’re using a different SSL library like LibreSSL, try switching to OpenSSL:
    git config --global http.sslBackend "openssl"
  4. Use SSH Instead of HTTPS: If the problem persists, consider switching from HTTPS to SSH for Git operations, which might be less prone to these issues. This requires setting up SSH keys and adding them to your GitHub account.

  5. Configure Git to Skip SSL Verification: As a workaround (not recommended for production environments due to security concerns), you can tell Git to skip SSL verification:
    git config --global http.sslVerify false
    git config --global https.sslVerify false
  6. Check for System Updates: Ensure your system and Git are up to date, as updates can resolve known issues.

  7. Use a Different Git Client: Sometimes, the issue might be specific to the Git client you are using. Trying a different client or a portable version of Git might help.

  8. Check for RST Packets: Use network diagnostic tools like tcpdump or wireshark to check for TCP RST packets that could indicate why the connection is being reset.

  9. Consult Documentation and Community: Look for solutions in the Git community forums or documentation, as the issue might be specific to the environment or network setup.

4.3 The solution

You should try to disable your local proxies that used to connect to github.com.

Try this command:

➜  bswen-springboot24 git:(main) git config --global --unset http.proxy

Or this command:

git config --global --unset http.proxy
git config --global --unset https.proxy

Now try again to push your code to github:

➜  bswen-springboot24 git:(main) git push                             
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 8 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (14/14), 2.95 KiB | 1.48 MiB/s, done.
Total 14 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), done.
To https://github.com/bswen/bswen-springboot24.git
   bdffeeb..69a008e  main -> main
➜  bswen-springboot24 git:(main) 

Now it works!

4.4 Optional solutions

4.4.1 disable the SSL verification(not recommend)

As a last resort, you can try disabling SSL certificate verification. However, please note that doing so will make your connection vulnerable to man-in-the-middle attacks and is therefore not recommended for production environments.

git config --global http.sslVerify false

5. Summary

Security Considerations:

When troubleshooting SSL_ERROR_SYSCALL, it’s important to be aware of the security implications of the solutions you apply. Disabling SSL verification, for example, can expose your connection to man-in-the-middle attacks. Always prefer solutions that maintain the security of your connection.


The SSL_ERROR_SYSCALL error can be caused by various factors, and the solution may depend on the specific environment and network setup. It’s essential to diagnose the problem carefully and apply the most appropriate fix, keeping security as a top priority. If the issue persists, consider seeking help from the community or the service provider’s support channels.

When you encounter the OpenSSL SSL_connect: SSL_ERROR_SYSCALL error, the first thing to do is to determine the cause of the problem. This could be due to network issues, proxy settings, or SSL certificate verification issues. You should be able to find a solution to the problem by checking your network connection, updating Git and OpenSSL, checking your proxy settings, disabling SSL certificate verification (not recommended), checking your firewall settings, or trying a different Git client.

Please note that disabling SSL certificate verification is an insecure practice and should be avoided. In a production environment, you should ensure that the network connection is secure and the SSL certificate is valid.

Hopefully, these tips will help you resolve the OpenSSL SSL_connect: SSL_ERROR_SYSCALL error you encounter when git cloning. If you have any other questions or need further assistance, feel free to ask!

In this post, I demonstrated how to solve the SSL_ERROR_SYSCALL in connection to github.com:443 when pushing code to github, the key point is try to disable your local http proxy or https proxy.