clonning tunnel failure #151420
Replies: 3 comments
-
|
Hey there! 👋 Thanks for posting in the GitHub Community, @manojGothankar! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. In the meantime, I do recommend taking a look at Troubleshooting cloning errors. Although I don't see your specific error listed in the article, you may find guidance there nonetheless. Let us know if this doesn't get you back up and running. I've gone ahead and moved this to the correct category for you. Good luck! |
Beta Was this translation helpful? Give feedback.
-
|
Hi! The most common cause for this specific error (400 with CONNECT tunnel failure) is often proxy-related. Try these solutions: Since this is a private repository and it was working before, verify your GitHub credentials: Then, try cloning again, it should prompt for credentials. As an alternative you can also try using SSH instead of HTTPS: If none of these work, please try running the clone command again and share the complete error output: Thank you!! 😄 |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
General
GitHub Feature Area
Issues
Body
I got below error while cloning
Cloning into 'incampus'...
fatal: unable to access 'https://github.com/manojGothankar/incampus.git/': ### CONNECT tunnel failed, response 400
if anyone have idea to solve it please tell,
incampus is a private repo , i have worked with it, i mean cloning and other all operations of git was working fine , but after somedays it started raising this error
Beta Was this translation helpful? Give feedback.
All reactions