Common Git Issues and How to Fix Them

Common Git Issues and How to Fix Them

Troubleshooting guide for common Git problems when working with CodeSubmit assignments

Git is essential for submitting your work on CodeSubmit. If you're experiencing issues cloning or pushing to your repository, this guide covers the most common problems and their solutions.

TLS/GnuTLS RPC Errors

If you see errors like gnutls_handshake() failed or TLS connection was non-properly terminated:

• Try cloning over HTTPS: Make sure you're using the HTTPS URL provided in your assignment (starting with http://)
• Update Git: Older versions of Git may have SSL/TLS compatibility issues. Update to the latest version
• Check your network: Corporate firewalls or VPNs can interfere with Git operations. Try from a different network
• On Linux: If your Git was compiled with GnuTLS and you're having persistent issues, you may need to rebuild Git with OpenSSL instead

HTTP/2 Stream Errors

If you encounter HTTP/2 stream 0 was not closed cleanly or similar HTTP/2 errors:

Force Git to use HTTP/1.1 instead:

git config --global http.version HTTP/1.1

This is often caused by proxies or firewalls that don't properly support HTTP/2.

Slow or Hanging Connections

If Git clone seems to hang or is extremely slow:

• Disable firewall/antivirus temporarily: Security software can sometimes interfere with Git operations
• Try a different network: Switch from WiFi to mobile hotspot, or vice versa
• Run with verbose output: Use GIT_CURL_VERBOSE=1 git clone ... to see where it's getting stuck
• Check proxy settings: If you're behind a corporate proxy, ensure Git is configured correctly

Authentication / Unauthorized Errors

If you see 401 Unauthorized or Authentication failed:

• Verify your credentials: Copy the clone command exactly as shown in your assignment - it includes your temporary username
• Check the password: Use the temporary password displayed in your assignment. It's case-sensitive
• Time limit expired: If your assignment has a time limit that has passed, you may no longer be able to push changes. Contact the hiring team if you need more time
• Repository closed: If you've already submitted your work, the repository may be locked for further changes

Push Failures

If git push fails after a successful clone:

• Check your .gitignore: Large files or node_modules directories can cause push failures. Make sure node_modules/ is in your .gitignore file
• Verify remote URL: Run git remote -v to confirm you're pushing to the correct repository
• Network issues: Unstable connections can interrupt pushes. Try again on a stable connection
• Authentication: If prompted for credentials, use the same username and password from your clone command

Still Having Issues?

If none of these solutions work:

1. Note down the exact error message you're seeing
2. Try the operation from a different computer or network if possible
3. Contact the hiring team or reach out to hello@codesubmit.io with details about your issue

We're here to help ensure you can complete your assignment successfully!