git clone. This guide compares Git mirror sites, proxy, and self-hosted mirrors, with a decision table and executable config steps. You get a clear comparison (use case, speed, stability, cost, maintenance), at least three config steps per option, and common failure fixes. Use it to choose and configure the right option for your team or CI runners.
Three Options Comparison Table
Use the table below to pick by use case, speed, stability, cost, and maintenance. Mirror sites are fastest to adopt; proxy fits mixed traffic; self-hosted gives full control at higher ops cost.
| Option | Use case | Speed | Stability | Cost | Maintenance |
|---|---|---|---|---|---|
| Git mirror site | Public repos (GitHub/GitLab mirrors) | High (CDN) | High | Free or low | None (third-party) |
| Proxy | All Git + HTTP(S) traffic | Medium–High | Medium (proxy uptime) | Low–medium | Low (config only) |
| Self-hosted mirror | Private or critical repos | High (local) | Depends on you | Higher (server + storage) | High (sync, disk, updates) |
Mirror Site Config Steps
Mirror sites (e.g. ghproxy, gitclone, or regional GitHub mirrors) expose the same repo under a different URL. No proxy or server to run.
Pick a mirror URL. Choose a public Git mirror for your region (e.g. https://gitclone.com/github.com/ or a known GitHub mirror). Verify it supports the Git protocol you use (HTTPS/SSH if applicable).
Rewrite clone URL. Replace the origin host with the mirror host. Example: git clone https://gitclone.com/github.com/owner/repo.git. In CI, set GIT_CLONE_URL or the repo URL to the mirror form.
Optional: Git url insteadOf. Add in ~/.gitconfig or repo .gitconfig: url.https://mirror.example.com/.insteadOf=https://github.com/ so all git clone to GitHub go via the mirror without changing scripts.
Proxy Config Steps
A proxy (HTTP/HTTPS or SOCKS) forwards Git and other traffic through a faster or permitted path. Good for unified acceleration and CI runners.
Set proxy env vars. Export http_proxy, https_proxy (and if needed all_proxy for Git). Example: export https_proxy=http://proxy.example.com:8080. Use the same in CI job env.
Git proxy config. For HTTPS: git config --global http.proxy http://proxy.example.com:8080 and https.proxy same. For SSH-over-proxy you may need ProxyCommand in ~/.ssh/config (e.g. nc -X 5 -x proxy:1080 %h %p).
CI: inject proxy in runner. In your CI config (GitHub Actions, GitLab CI, Jenkins), set the same proxy env for the job or runner so git clone and dependency fetches use the proxy. Restart or recreate the runner after changing env.
Self-Hosted Mirror Brief and Selection Advice
Self-hosted mirrors (e.g. Gitea, GitLab, or a bare repo synced by cron) give you full control and often the best latency inside your network. They are suited to private repos, compliance needs, or when you cannot rely on third-party mirrors or proxy availability.
- When to choose: Compliance, private repos, or need for guaranteed sync and retention.
- Cost: Server (or VM), storage, and ongoing sync (cron or mirroring tool) and monitoring.
- Selection: Prefer self-hosted if mirror sites and proxy are blocked or insufficient; otherwise start with mirror or proxy for lower maintenance.
Common Failure Troubleshooting
When mirror or proxy is misconfigured, clones can time out or fail with unclear errors. Typical failures and quick checks:
- Clone timeout or connection refused. Check mirror/proxy URL and port; ensure firewall and CI runner can reach the proxy or mirror. Test with
curl -I <mirror-url>orgit ls-remote. - SSL/certificate errors. If using a corporate proxy, you may need to set
GIT_SSL_NO_VERIFYonly in trusted environments or add the proxy CA to the system trust store. - Slow after config. Verify traffic actually goes through the mirror or proxy (e.g. proxy logs, or clone from a known mirror URL). For CI, ensure the runner region is close to the mirror or proxy.
Summary and Next Steps
For cross-border git clone acceleration, choose mirror sites for quick setup and zero maintenance, proxy for unified Git and dependency traffic, or self-hosted mirror when you need full control. Use the comparison table and steps above to configure. For a remote Mac (e.g. Mac Mini M4) close to your mirrors or in a better region for CI, see our pricing, homepage, and purchase (no login to view). More guides: blog.
Run CI and Fast Pulls on a Remote Mac
Rent a Mac Mini M4 in a region close to your mirrors or with better connectivity. SSH/VNC included. View pricing and try our remote Mac service—no login required. Or read more on our blog.