# How to configure GitSCM to use a proxy different from what is configured in the plugin?

**URL:** <https://community.jenkins.io/t/how-to-configure-gitscm-to-use-a-proxy-different-from-what-is-configured-in-the-plugin/15311>\
**Category:** Using Jenkins\
**Created:** [May 20, 2024, 11:03pm UTC](https://community.jenkins.io/t/how-to-configure-gitscm-to-use-a-proxy-different-from-what-is-configured-in-the-plugin/15311 "2024-05-20T23:03:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidmichaelkarr](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/davidmichaelkarr/32/8316_2.png) [@davidmichaelkarr](https://community.jenkins.io/u/davidmichaelkarr)\
**Post date:** [May 20, 2024, 11:03pm UTC](https://community.jenkins.io/t/how-to-configure-gitscm-to-use-a-proxy-different-from-what-is-configured-in-the-plugin/15311/1 "2024-05-20T23:03:19Z")

</div>

We’re using Jenkins 2.303.1 .

We normally use an in-house git server behind a firewall. We’re doing a POC to use an external git server. We’re unable to get checkout with “GitSCM” work, because it appears that we’re unable to control the proxy used by GitSCM. I’ve tried various ways to do it, but GitSCM seems to ignore environment variables. I’ve gone through the GitSCM documentation, and I don’t see an obvious way to do this.

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [May 21, 2024, 3:57am UTC](https://community.jenkins.io/t/how-to-configure-gitscm-to-use-a-proxy-different-from-what-is-configured-in-the-plugin/15311/2 "2024-05-21T03:57:59Z")

</div>

You might try configuring the HTTP proxy for Jenkins in “Manage Jenkins” → “System”.

There is also a [stack overflow article](https://stackoverflow.com/questions/783811/getting-git-to-work-with-a-proxy-server-fails-with-request-timed-out) that describes proxy configuration using git commands. The Jenkins [config file provider plugin](https://plugins.jenkins.io/config-file-provider/) can deliver a `.gitconfig` file to the home directory of the user running each agent.