# Whitelistable IP range for build containers

**URL:** <https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664>\
**Category:** Question & Answer\
**Created:** [September 8, 2017, 10:08pm UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664 "2017-09-08T22:08:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeffremer](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/jeffremer/32/520_2.png) [@jeffremer](https://discuss.bitrise.io/u/jeffremer)\
**Post date:** [September 8, 2017, 10:08pm UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/1 "2017-09-08T22:08:14Z")

</div>

As part of certain builds we’d like to feed data into a Graphite instance. For security this Graphite instance is normally only available over VPN, but we _can_ whitelist IPs or a range of IPs. So my question is, do the boxes/VMs that BitRise builds on have a static or predictable IP or range of IPs that we could whitelist on our side?

---

<div class="post-metadata">

**Author:** ![bootstraponline](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@bootstraponline](https://discuss.bitrise.io/u/bootstraponline)\
**Post date:** [September 9, 2017, 2:35am UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/2 "2017-09-09T02:35:02Z")

</div>

> Restrict by IP: configure your server to only allow connections from certain IP addresses. We don’t recommend this solution, as even if you restrict the IP range to [bitrise.io](http://bitrise.io) build machine IPs, that means that anyone who runs builds on [bitrise.io](http://bitrise.io) will be allowed to communicate with your servers. Additionally, we only have fix IPs for our Mac build machines, the Linux stacks are hosted on Google Compute Engine and we use emphemeral IPs there, so the range is GCE’s ephemeral IP range.
> 
> [How to configure bitrise to access an internally hosted git repository](http://discuss.bitrise.io/t/how-to-configure-bitrise-to-access-an-internally-hosted-git-repository/85)

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [September 12, 2017, 10:36am UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/3 "2017-09-12T10:36:05Z")

</div>

Hi @jeffremer,

@bootstraponline is right (see above: [Whitelistable IP range for build containers](http://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/2?u=viktorbenei))

If you’d need more info please check [How to configure bitrise to access an internally hosted git repository](http://discuss.bitrise.io/t/how-to-configure-bitrise-to-access-an-internally-hosted-git-repository/85) and feel free to ask there!

I’ll close this issue, to have a centralized discussion at [How to configure bitrise to access an internally hosted git repository](http://discuss.bitrise.io/t/how-to-configure-bitrise-to-access-an-internally-hosted-git-repository/85)

---

<div class="post-metadata">

**Author:** ![viktorbenei](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/viktorbenei/32/18_2.png) [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Post date:** [September 16, 2017, 4:00pm UTC](https://discuss.bitrise.io/t/whitelistable-ip-range-for-build-containers/2664/6 "2017-09-16T16:00:27Z")

</div>

Closed on September 16, 2017, 4:00pm UTC

This topic was automatically closed after 4 days. New replies are no longer allowed.