Hi Ajay,
This error may be related to network connectivity, proxy configuration, or firewall restrictions on the machine where you are trying to download the project.
Since the same project can be downloaded successfully from the customer VDI, I would suggest checking the following:
Verify whether the new machine is connected to the required VPN or corporate network.
Check whether any firewall, proxy, or antivirus settings are blocking Git or Mendix Version Control communication.
Try cloning the repository using the HTTPS URL from Git Bash or the command prompt.
Compare the proxy and Git configuration between the working VDI and the affected machine using git config --list.
Check whether the required server URLs are accessible from the affected machine.
Since reinstalling Git and manually cloning the repository did not resolve the issue, it would be worth involving your IT/network team to check whether any network-level restrictions are affecting the Git connection.
Hope this helps!
Hi Ajay,
The exception:
LibGit2Sharp.LibGit2SharpException:
failed to read data:
The server returned an invalid or unrecognized responseindicates a failure while communicating with the remote Git repository.
Since the same project downloads successfully on another machine, and cloning through Git also fails on the affected machine, I would focus on the local Git/network configuration before investigating the Mendix project itself.
Recommended troubleshooting steps:
1. Check Git and Windows proxy settings
Open Command Prompt and execute:
git --version
git config --global --get http.proxy
git config --global --get https.proxy
netsh winhttp show proxyCheck whether an outdated proxy configuration is present or whether your organization requires a proxy that Git has not been configured to use.
If a proxy is required, configure Git using the correct proxy address provided by your IT team.
2. Verify connectivity to Mendix Team Server
For Mendix-hosted Git repositories, check connectivity to git.api.mendix.com over HTTPS (port 443).
You can test basic connectivity using:
Test-NetConnection git.api.mendix.com -Port 443Also check whether a corporate VPN, firewall, Zscaler, or SSL inspection policy is interfering with Git traffic.
3. Test the clone using Git CLI
Use the actual Git clone URL from your repository settings:
git clone <repository-clone-url>Do not use the project's Mendix Portal browser URL as the Git clone URL.
If the Git CLI clone also fails, investigate the Git authentication, proxy, TLS certificate trust, and network configuration.
4. Compare with the working machine
Since the same project works elsewhere, compare:
Git version and configuration.
VPN and proxy settings.
Corporate security software.
Network connectivity.
Git authentication configuration.
If permitted, testing the affected machine on another trusted network can help isolate network restrictions.
5. Retry Studio Pro after resolving Git connectivity
Once Git CLI cloning succeeds, retry downloading the project through Studio Pro.
If Git CLI succeeds but Studio Pro still fails, open Help → Open Log File Directory, collect log.txt, and share the relevant details with Mendix Support.
Important: Do not permanently disable Git SSL verification as a workaround. If certificate validation fails, resolve the certificate trust or corporate proxy configuration instead.
Mendix provides an official troubleshooting guide specifically for Team Server connectivity and Git cloning problems:
https://docs.mendix.com/refguide/troubleshoot-team-server-issues/
Additional reference:
https://docs.mendix.com/refguide/troubleshoot-version-control-issues/
My recommendation: Start with the Git CLI clone test and proxy configuration. Since both Studio Pro and Git fail on the affected machine, resolving the underlying connectivity or authentication issue is the priority.
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.